WinXP Home in workgroup not able to access shared folders

0 pts.
Tags:
Networking
Seems this is a common problem, but I've tried all the solutions. Win98 box upgraded to WinXP Home SP2 (actually 2 boxes) on mixed workgroup based network. Need to access folders on Win2K pro machine. Box A - no problems at all Box B - cannot effectively browse the network, can ping the Win2K box by IP but not name. Can eventually see the other machines on the network (but never all) but cannot access any. user names/passwords all the same Netbui over TCPIP enabled Guest enabled on both machines Firewall disabled Win 2K box can see and access the WinXP box causing the problems. Any ideas?
ASKED: December 1, 2005  12:36 PM
UPDATED: December 2, 2005  10:45 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

At the risk of being nit-picky, I’m a little concerned by your use of the term “NetBEUI over TCP”, the reason being that NetBEUI is its own protocol, and it should be “NetBIOS over TCP”, meaning that you should not have two networking protocols installed. If I’m just over-reacting, then please ignore this first paragraph.

Other things to check for are:
- TCP/IP Control applet, advanced button, check the WINS folder tab for consistency.
- Are all machines using fixed or DHCP addresses?
–If fixed, are all subnet masks the same?
- Are all machines members of the same workgroup?
- If you browse the “Computers Near Me” from each of the three machines, what discrepancies do you find between the 3?
- For any shared resources (folders in this case) have you checked both the share permissions and the security permissions – this is a common stumbling block.
- See if you can add specific machineuser names to the permissions, such as \BoxAUserA.

Write back and let us know what you find.

Bob

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Boardinhank
    If everything looks ok and the same between box a and b. then I would dump your protocol stack. meaning uninstall your tcp/ip - client for microsoft networking etc till your installed components is empty. you can be extra nice and reboot. even one more step and uninstall the network card before you reboot. when it restarts it will redetect the nic, reload your stack and then make sure you are part of the same workgroup etc and that you are part of the correct subnet, hopefully you are using a private class c address like 192.168.0.xxx mask 255.255.255.0 or something like that. essentials are file and printer sharing, same subnet and same workgroup.
    60 pointsBadges:
    report
  • Poppaman2
    The fact that this is XP and you can ping by IP address, leads me to suggest that before you dump the TCP/IP stack etc..., that you try flushing the DNS cache on the problematic system, and re-registering. Look at ipcongig /? for specific commands if/as required. If this does not help, I would then proceed with the networking stack dump.....
    0 pointsBadges:
    report
  • Guardian
    Make sure your nic's are all fine! And activity is low between the PC's , try testing whilst you have no other applications running on the PC's ( even you media player). If sometimes you can see some machines, might be cache is working there. Try the all might "reboot", make sure all PC's are in the same workgroup, might try reconfiguring to the same workgroup see if you get the " welcome to .... " workgroup. Permissions also might help as suggested above. Just one shot in the dark, check media (cabling and network devices- Huibs, switches) if all is normal. Keep us informed Regards Newton
    900 pointsBadges:
    report
  • Kiwifred
    Thanks for all the responses. To summarise. All was working well in win98 the night of the upgrade. Upgraded overnight and ensured upgraded boxes had same users/passwords as before. So, in effect nothing has changed. will try the dump IP stack suggestion (after the flush DNS). FYI all machines on fixed IPs in 192.168.0.xxx range with subnet 255.255.255.0. No WINS in any machine (Oh, and yes I did mean netbios over TCP/IP - silly me). Seems to me this can be a problem with XP uipgrades - I've seen it before and any solution has been along the lines of - OK it works now - don't know why, but hey!
    0 pointsBadges:
    report
  • Boardinhank
    So you are still not working? what if you add the machine to your HOSTS file can you then ping it by name? There is an interesting thing going on for sure, technically DNS would not even be needed in a LAN situation where it can use a arp request to get the machine to respond by name. you can ue a ping -a 192.168.0.XXX to see if you can get arp to resolve the address to a hostname. In windows you have a master browser that makes the my network places work. you can read details here http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prcf_omn_mzox.asp and start to understand what it does. Maybe make sure that one machine only is set to be the master browser. I have seen NIC's that after the upgrade just have issues with the driver XP provides. You can try another one, update your driver, even down to I have had to set the duplexing and then it worked fine. I would look at the nic and its drivers before the master browser concern but it is good information to understand how computers use this browsing scheme to make life more simple and plug and play like.
    60 pointsBadges:
    report
  • Kiwifred
    Looks like the remove/reinstall tcp/ip stack has done the trick - well almost. Still have an issue (minor and easily got around for today) where the mapped drive I need has to be specifically logged onto even though users and passwords are the same on both machines. This could be because i had to change the user on the upgraded machine (WinXP won't allow mchine and user to be the same whereas Win98 is OK with that) - I also changed the user on tmachine A (Win2K) - I think i sould have added the new user even though the name only changed from shop to shoppc. Can't do that today though due to user pressure - will try Monday. Thanks all for the prompt and full suggestions. BTW Had added machine A to machine B's hosts file.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following