in

recevie an error when trying Universal Naming convention from some servers

Hello:

For some reason whenever I try to use the Universal Naming Convention (UNC), on some servers I receive an error.  The error is "The Network name Cannot be found" (please see pictures).  The same error comes up if I try to use the server's IP address , instead of the dns name.

I can ping the Servers (by name and by IP address).  The problem is not on every server only a couple.  I am able to get the mapped drives to work correctly on the same "Bad" servers.  The problem is exclusively with the UNC path to these servers.  If I try to put a \C$ at the end of the unc attempt, that works.  So if I type \\Venus\C$ that works just fine; but, if I type \\Venus that does not work.

This is only on Windows servers.  The errors come from Windows XP and 2000 workstations.  And from other 2003 Servers as well.

Before the problem was brought to my attention when users could not connect to the mapped network drives.  I noticed that the 'Server' service was not started on these3 different servers.  I started the service (Servers) and that problem was solved; but, teh UNC problem still remains.  

A restart did help 1 of the servers but not the rest.

Solution: recevie an error when trying Universal Naming convention from some servers

are these machines in a domain? If so, what happens if you use the fully qualified domain name (FQDN)? For example, \\server1.contoso.com

UNC is using WINS, so you may want to check your WINS server to make sure that it is working correctly. The FQDN uses DNS to do the same thing...which is to convert the machine name to an IP address.

Popular Tags

Browse All Tags