Windows Forum

Ask something
Discussion Locked

Cannot find Network Path Error

0 helpful
10 replies

by dillinger00

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am woking on an NT4.o Server. When I browse Network Neighborhood I can see my Windows 2000 server listed but when I try to open it I get the error Cannot Find Network Path. I can ping the 2000 server and get a reply. On the windows 2000 server when I look at Network Neighborhood I can see the NT server and also log into it. Also when I try to use the printer on the NT server it says that it cannot find the network path. This printer is shared on the 2000 server. I'm very confused and need to find an answer
Thanks

10 replies

by baddragon

Hi
Check to see if the Wins entry are correct on your and the 2000 server, browsing (which is what you're doing) is an netbios function. Also check out the event logs System, to see how often a browser election is being help.

JO

by mruiz

On Windows 2000 when you print to a shared printer it renames the printer path. So if you try to print from another NT station it can't find the original path. Point is Windows 2000 Network paths have different naming paths when created in 2000/NT

by dillinger00

The two servers I am referring to are in a workgroup. The main problem is that I cannot browse to the 2000 server from the NT server. Yet I can see the NT server from the 2000 box and log into the NT server. I can also see and log into the NT serverfrom any of the workstations that we have and they are win98 and 2000 pro workstations. I'm trying to figure out why the NT box seems to have lost it's ability to see the 2000 server. I beleive that when I solve the first issue it will also resolve the printing problem on the NT server. I hope this added info will help.

by curlergirl

If you are on an NT domain, the Win2K server is a member server (i.e., it cannot be a PDC or BDC). In these circumstances, it may be that the local security on the Win2K server is not set up properly to allow you access to the server's shared resources. Go to the Computer Management Console on the Win2K server and add whatever domain users and/or groups are necessary to the Administrators and/or Powers Users and/or Users local groups. Also, or alternatively if appropriate, make sure that anyshared resources on the Win2K server that need to be accessed from other machines on the domain are set up to allow access from the domain user and/or group accounts, not just local groups or accounts. Also, you might try disabling the Guest account on the Win2K server - I'm not sure if this applies to Win2K servers, but I know NT member servers in an NT domain have to have the Guest account disabled. Hope this helps!

by dillinger00

I added NetBeui to the NT server and now I can browse to the W2K server and access all of the shared folders. I don't think that this is a fix it seems to me to be more of a workaround for this problem since it did work without Netbeui loaded before.

This discussion is closed to new replies.