The Active Network
ActiveWin Anonymous | Create a User | Reviews | News | Forums | Advertise | VBA in Excel | Users Online: 0  
 

neowin.net

Amazon.com

  *  

The network path was not found
Forum: Windows XP
Read Only Forum
Back to Windows XP
All Forums
  Displaying Posts 1 through 4 of 4
  This is an archived static copy of ActiveWin.com.
#1 By 71758 (205.144.218.66) at Tuesday, January 02, 2007 06:44:47 PM
I am having the same problem with my computers. I went to the compnetworking web site and I did what it said to do. This still did not fix the problem. The computer that I am having the problem with was working about a week and a half ago. I just can't figure out what is going on. I set the computer back so that it has the ten sections of the correct protocol. I don't know what else to do. Help!

#2 By 76894 (76.18.51.15) at Wednesday, April 11, 2007 11:40:43 AM
the network path was not found I found the problem (at least in my case) to be a corrupt File and Printer Sharing. Double click the Local Area Network Icon, click Properties, highlight File and Printer Sharing and Uninstall, reboot. When the Computer is ready again, repeat the paragraph above to before Uninstall and then Click Install, highlight Service and click Add, highlight File and Printer Sharing, and click OK.

#3 By 91707 (86.129.236.119) at Saturday, November 24, 2007 01:03:55 PM
I had the same problem nearly drove me nuts. None of the above fxes worked - but this one did: http://support.microsoft.com/kb/903267/en-us

#4 By 93278 (67.101.103.135) at Tuesday, December 11, 2007 07:53:10 PM
[QUOTE]Originally Posted by origamiuk: I had the same problem nearly drove me nuts. None of the above fxes worked - but this one did: http://support.microsoft.com/kb/903267/en-us [/QUOTE] It seems that networking issues at any level can cause this. I spent quite a bit of time on this problem, which happened apparently randomly on our network (7 computers). We use one computer as a server, and randomly, the server disappeared. Rebooting the server seemed to fix it. It turned out that one of the computers (not the server) had 802.1x authentication enabled, and the others didn't. When this computer became the Master Browser (who maintains the list of computers on the network), nobody could access it. The clue was access denied messages in the security log of one of the other computers. Not sure whether this is unique or will help others.



 

  *  
  *   *
 
replica watches