You are unable to connect to any network resource (network shares, printer, etc) on a Windows XP machine, from a Win XP client.
A solution (there could be several causes)
- On the target machine (the one you're trying to connect to) open up Services, under Administrative Tools in the Start Menu.
- Scroll down to the Computer Browser service.
- If it is Disabled or set to Manual, set it to Automatic.
- Then start it. It may stop immediately again, but this is OK.
- At this point try to connect to the target machine.
- open up Network Connections, under Control Panel.
- Right click on your network adapter and click on Properties.
- Click on Internet Protocol (TCP/IP), then click on Properties.
- Click on Advanced, and click on the WINS tab.
- Even if it is set to Default, set the radio button to Enable NetBIOS over TCP/IP.
- Press OK on each screen until everything's closed.
- Go back to the client machine and try again.
- You should be able to connect!
- Go back to the Services window and find the service named Routing and Remote Access.
- Double-click on it, set it to Manual, and stop it.
- Close Services and try to connect from your client machine again.
, Microsoft Windows XP Networking Inside Out
, or Windows XP Home Networking
.If this helped you, or if you found another solution to this common and frustrating problem, please leave a comment to help others!
p.s. See here for a possible Windows 2000 solution.
35 comments:
To share resources such as file and print sharing. You must first rename the drive you're trying to share to local disk E: or whatever the drive letter will already be named. example local disk, don't change or add a drive letter.After that simply map to the computer name and dive letter using the unc path. example \\computer name\E and wahlah, coool hey. Don't use netbios over tcp/ip or go into the services or registry. Be sue that all the computers are in the same workgroup.I've tried this with 2000pro and xp pro service pack 2 mechines and it works everytime.Microsoft does not recommend using netbios if at all possible. Use client for microsoft networks, file and print sharing and tcp/ip...Hope this helps.
Thanks for posting. Interesting tip.
Thank for this valuable information.
No probs - thanks for reading. I just Windows networking was more stable, but hey it makes for lots of interesting blog posts.
It appears that the box "client for microsoft networks" must be checked
as well as the NETBIOS default or enable box being checked. I did Netbios, still no luck until I checked "client for microsoft networks", then it all came back. How this changed? dont know.
When all in windows goes all right, it is not necesary to check in services or the registry, but, when this badly created system is wrong, services and registry could save your live.
For "humans" or "mortals" it seems like 'too complicated', but for us, it is the day to day.
Thanks for all tips, neither works for me. Grrr!
After many attempts, I have already achieved.
I had to restart the Computer Browser service and enable net Bios.
Thank you very much!
Applause!
Great fix. I was trying for weeks and this is the only fix that works.
Here's the thing: seeing the PCs in my workgroup and file sharing only stays on for 15 minutes or so after your fix. It doesn't matter if I start or stop the "routing and remote access" as long as I change it.
Any ideas on what could be blocking the workgroup after those 15 minutes?
I could acess folders on my pc from the laptop but couldnt access laptop files from the Pc these tips fixed my problem
@joneric - glad it helped you a bit.
I think starting/stopping Routing and Remote Access resets something. From your description it sounds like some other competing service is starting up again.
Do you have other computers on your network that could be competing for position of Master Browser? In the past I have had this problem. One thing I would say is to look in your Event Log, like it describes here: http://support.microsoft.com/kb/135404
@anonymous: glad you sorted out your issue! Now let's all hope Microsoft totally rewrites their networking in the next OS!
Also @Gvann - I am glad you sorted out your issue! I should update this post with some of the other suggestions. One for the list.
THe firewall must be informed of the other computers to allow them to pass through.
Thanks for the reminder to check this. Found remote access off on one of my machines. Have no idea why it was disabeled, but problem solved. Thanks again. Mike.
millions of thanks dear. You work really great. Problem solved perfectly by method no. 2.
CHEERS!!!!!!!!!!!!!!!!!!!!!!
Hello. I had this problem intermittently for a long while. My main PC would fail to connect to my secondary PC even though both were connected on the same switch. On the other hand, my laptop and media center had no problem connecting to the secondary computer. All PCs were running Windows Vista.
Ignore most of what you've read online -- stuff like disable your firewall etc... I saw those same tips and they were just not going to help.
I found that this is what fixes it:
1. Go to control panel
2. Click on "Network and Internet/View network status and tasks"
3. Select the "Manage network connections" link on the left "Tasks" section
4. Double-click on your LAN adapter that you're using to connect to the network. (For example, "Local Area Connection"
5. Select properties
6. Select "Client For Microsoft Networks"
7. Click on Properties
8. On the RPC Services tab, go to the "Name service provider" and select "Windows Locator" from the drop down menu
9. Click OK
10.Click close
11. Click close
After a second or two, you should be able to now connect to your other computer.
I have no idea which software changed that setting and I found that when I went back to it, it had been changed again to blank.
So if you see the problem again, follow the steps above.
It worked for me and I hope it works for you too!
If it does, drop me a note at o-e-c-h-e-r-u-o at gmail.com
(remove the dashes and extra spaces and replace the at with a @)
Hi all,
if it does not work all above solutions please repair the system with the Windows xp SP2.
It should work.
i tried with this method. no problems were not found in machine.
i am maintaining with 90 xp machines. there is no problems with each other. and i followed above 3 methods but still i got the problem. finally i did this method. it is working fine.
hope it will help to somebody.
Thanks
sridhar
Hey there,I just read this post,and just wanna make sure something.
I have 5 computers sharing 1 printer,and 5 of them can share and print well,but recently 1 of them cant print but it already shared,and i went to ping that target computer and i found that THE NETWORK PATH WAS NOT FOUND,and so i just found this blogs of solutions...
Ok here is what u wanna make sure about:-
What if i follow the above solution and all things done,and the client computer can print well,but will this settings will effect to the other 4 of my computers,and cause them cant print?
I am not sure if that will fix your problem if the rest of your PCs can connect. I would look for a solution for the problem PC before changing the print server.
Perhaps as @sidhu commented, you can try a Windows repair.
Good luck!
I have THE FUCKING SOLUTION to "The Network Path Was Not Found"..
IS THE FUCKING SERVICE: "TCP/IP NetBIOS HELPER".. PUT THAT FUCKING SERVICE STARTED!! AND AUTOMATIC!!..
IS THE FUCKING SOLUTIOOOOOOOOON!!!!!!!!
MEEEEEEEETOOOOOOOOOOOOOOOOOOOOOOLLLLLLLL!!!!!!!!! \m/!!!!!!!!
Uffffffff, sry my caps, but i have trying resolve this like a fucking monkey after FIVE HOURS!!
thanks m8
the netbios helper service did the trick
Great job...
Start service "TCP/IP NetBIOS Helper" is the resolution. Tks.
Sorry. I've tried all of these "solutions." None have worked. I used to be able to see my laptop's C: from my desktop PC. Now I can't. It says the network path cannot be found. It was able to see it half an hour ago, but now it can't.
Interestingly, this problem only happens when I am connected physically via Cat-5 cable to my switch. When I'm wireless, it works like a charm.
@Big Al
Do you mean the admin share \\pc\c$ ?
When you are wireless, you will have a different IP to when wired, so perhaps check the firewall settings on both PC's for any anomalies.
Also, you may even be on a different subnet depending on your router config. Can you ping the desktop machine?
Also, if you are using Windows 7 (not sure if you are), they have an additional layer of security which classifies wireless networks into Home/Work/Public. You would need to make your your wifi network is set to Home to be able to access this type of share.
Post back and let us know how you get on
One more thing to add to the already-long list of things to check: Try turning off Internet Connection Sharing. That turned out to be the problem in my case. Why? Who knows.
[quote] Anonymous said...
I have THE FUCKING SOLUTION to "The Network Path Was Not Found"..
IS THE FUCKING SERVICE: "TCP/IP NetBIOS HELPER".. PUT THAT FUCKING SERVICE STARTED!! AND AUTOMATIC!!..
IS THE FUCKING SOLUTIOOOOOOOOON!!!!!!!!
MEEEEEEEETOOOOOOOOOOOOOOOOOOOOOOLLLLLLLL!!!!!!!!! \m/!!!!!!!!
Uffffffff, sry my caps, but i have trying resolve this like a fucking monkey after FIVE HOURS!!
11:12 AM [/quote]
I LOVE YOU BRO THIS WORKED FOR ME
Yess, enable this service, and it will work:
TCP/IP NetBIOS HELPER
This will solve the "The network path was not found. (53)" error!
henrry.doan( email: doanvanvu@hotmail.com)
Idon't know much about how to solve this problem, but few days ago I have faced with this problem. I cannot connect to printer server from the client on the network. Then I use advanced systemcare 4.0
click on turbo boost and click on configure turbor boost.I un check :
-disable application compatibility cache
-Disable printer support
-disable tablet input support
-disable scaner and pc support
-disable sharing media to other media devices
-disable auto proxy detecting
after finished configure turbo boost on the printer server then any client can connect to the printer, sharing folder,...
sorry about my English
I am trying to improve my English
Works for me.
Just Right click on Computer Browser service(in services) and click restart. Enable net Bios in WINS lan setting. That's it.
Thank you very much!
tcp/ip netbios helper service was disabled for me. set to automatic and started, fixed.
I ran into this problem and tried every solution here and many others. My problem was every Windows 7 computer worked (could see other computers) but every XP computer could not. I found out that it was the NAME of the workgroup. For some bizarre reason, the XP computers did not like the 4 character name I gave the workgroup. I have no idea why, but when I renamed the workgroup to MSHOME, everything started working.
"TCP/IP NetBIOS HELPER" Service started.
worked. <3
"TCP/IP NetBIOS HELPER" Service started.
Worked
4It works or me! Tks a Lot!
Post a Comment