Cannot Access HomeServer Share by name on one computer, but can on another
I have a Desktop and Laptop computers, both run Vista Home Premium 32 and Norton Internet Security 2010. All with latest patches and updates. I also run a Windows Home Server. This configuration has remained pretty much the same for years. Recently there have been times when I cannot access shared files on the HomeServer from the Desktop by name (\\HOMESERVER), but can using IP address (192.168.1.105). At the same time everything works fine from the Laptop. I've checked network config to deep levels. Both are Hybrid nodes using the Default NetBIOS settings and at the time of the problem, but report using NetBIOS over TCP/IP (ipconfig /all). The one difference bewteen the laptop and desktop is that I run StarCraft2 on the desktop. I also seem to run into this problem afterplaying SC2 (but not all the time). Sometimes I can fix this problem by shuting down everthing Desktop, Laptop, HomeServer, Router and switch. Sometimes this doesn't work (like today). The laptop works OK using its wireless connection or the wired connection thru the same network switch as the desktop.
November 6th, 2010 5:42pm

Hi, Thank you for posting! What is the exact error message when failed to access the HomeServer? Is it "The network path was not found"? Please try the following command from Start: netsh winsock reset netsh int ip reset c:\resetlog.txt If this does not work, try the steps below: 1. Open up Network Connections, under Control Panel. 2. Right click on your network adapter and click on Properties.Click on Internet Protocol (TCP/IP), 3. then click on Properties. 4. Click on Advanced, and click on the WINS tab. 5. Even if it is set to Default, set the button to Enable NetBIOS over TCP/IP. 6. Press OK on each screen until everything’s closed. 7. Go back to the client machine and try again. Regards,Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
November 9th, 2010 12:10pm

Thanks for the helpful response. Yes, "The nework path was not found" was the error message. I have already fixed the problem by shutting everything down then bringing them up one-by-one... not the best solution. I will keep your reply handy for the next time, then post the results. Again, thanks.
November 9th, 2010 10:44pm

Sorry to say neither fixed worked yesterday when the problem once again surfaced. The exact message displayed was Windows cannot access \\homeserver when I enter \\homeserver in the Start Search box. Clicking the Diagnose button yielded a message to check spelling, etc. This seems to be some sort on name resolution problem as I can always get to the shares by using the actual IP address. Repeated reboots did not fix things. Shutting down everything, then bringing up the router, switch, Desktop, then Homesever (in that order) resolves the problem. I will try other combinations and orders when the proble resurfaces.
Free Windows Admin Tool Kit Click here and download it now
November 12th, 2010 7:10pm

I suspect that there are differences in the local DNS mapping files on your two computers, so that one of them has an entry for mapping \\homeserver to the proper IP address and one does not. Such a problem is very likely to cause name resolution issues. Unfortunately, I do not know how to inspect those files, and correct them if appropriate.
April 15th, 2012 9:42pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics