The specified network name is no longer available

Just loaded up a brand new PE1950 with Server Enterprise 2003 R2 SP2 x64, trying to install anti-virus and other applications from source files located on another server.  I go to Run -> \\<server-name>\share and the system does nothing.  After approx 30 seconds it returns the following error:

The specified network name is no longer available

Both the system in question as well as the target server are pingable and I am able to connect to the same share from my workstation as well as any other server.  I've tried going to other shares and I always get the above error.  Event log does not show any errors whatsoever.  

Any ideas where I might look to fix this?  Thanks.
Who is Participating?
complex83Connect With a Mentor Author Commented:

Turns out this wasn't a VM issue at all.  The machine has two nic cards and as soon as I tried using the other nic, problem gone.  Weird, but there's no difference to using either card so I'm happy to just use the one that works.  Thanks for all the suggestions, I appreciate the effort.
Andres PeralesCommented:
have you checked to make sure that the firewall is off or you allowing what you are doing through it!
complex83Author Commented:
The service for the Windows Firewall has not even been enabled.
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

Well... on the server where you get the error you can try to reset the network stack it worked with me.

Open a dos command line then:

netsh int ip reset reset.log
netsh int ip delete arpcache
netsh winsock reset
ipconfig /flushdns

Reboot the server

Reconfigure the IP Address gateway and DNS because the commands above have reseted the network stack including tcp/ip.

Try again see if you still have the error.
The IP is pingable, what about the FQDN (to test DNS)?

Example: Ping

If it is pingable, you have a problem with netbios. Let us know if this is netbios or DNS and we can fix from there.
complex83Author Commented:
Tried to reset the network stack and it seems to be working better but still having issues.

I can access some network shares but not others.  Those that work take what seems like an inordinate amount of time (almost 45 seconds) to open, those that don't work are returning a different error:

"No network provider accepted the given network path"
Consider this:

You may have a multihomed domain controller. A multihomed domain controller is simply defined as a domain controller with multiple IPs. This could mean two or more IPs on the same NIC, Two or more NICs, or A NIC and VPN connection to the outside world.

So, some services may bind or be redirected to the wrong network binding. If fact, they could be bound or redirected to the outside network binding. So, that binding may give you the errors you see before you because that outside binding may not know how to get back to the client.

I am in the process of bringing together advice from others on how to configure a multihomed domain controller so there is NO error in the path of communications: (So far, this is what I have come up with)

There are a couple of "transports" or "protocols" or whatever you want to call them, that the DC uses to communicate with other machines on the domain and to the outside world:

1) DNS
3) Netbios

To prevent from DNS binding to the outside NIC or IP address, there are a couple things you will need to do. One is you need to prevent it from registering the SRV records in DNS. The second is you need to clean out DNS of any SRV records to the outside NIC. The third is, you need that outside NIC to not register with DNS.

Step 1) To resolve these issues, Follow this link: (NOTE: By default, 2003 server registers both NICs SRV records in DNS)
Step 2) Once you prevent bot SRV records from registering in DNS when the netlogon service restarts, then you need to prevent it from registering its DNS records in DNS. To do this go to the NIC configuration>> TCP/IP properties>>Advanced Button>>DNS tab and disable the ability of the NIC to register its DNS settings in DNS
Step3)) Once you have disabled the ability to register that outside NICs DNS address, then you must remove all HOST A, SRV, and cached records of that outside NIC. I assume you already know how to remove HOST A records. To remove DNS cache, go to the command prompt and type IPconfig /flushDNS. To remove the SRV records, pleas follow the advice on this link:

DHCP may try to provide DHCP to all network bindings. This could be a VPN or second NIC to the outside world. You can prevent it from providing DHCP to any binding by following these simple steps:

DHCP snapin>>right click the server in question>>Select properties>>select the Advanced tab>>select binding

You can disable any binding from providing DHCP

Preventing Netbios is a little more difficult to do on various types of Multihomed domain controllers. Not always does a DC use WINS when dealing with netbios. So, this is a bit more involved.

To prevent Netbios from binding to the outside binding or VPN connection binding, you must go to that binding and remove the ability of it to do ""Netbios over TCP/IP"" or ""Netbios over DHCP"".
For a VPN connection and Dual NICs:
Right click "My network Places">>select "properties">>right click "VPN connection" or the Second NIC>>Select "Properties" >>Select "TCP/IP">> Go to Properties>>Go to the "WINS" Tab>> and prevent it from providing "Netbios over TCP/IP" and also prevent it from performing "Netbios over DHCP"

Disabling File and Print sharing:
You may also wish to disable your outside NIC from broadcasting out your files and printers to the outside world. To do this, disable File and print sharing.

Other things to look out for:
You should have one single gateway for your multihomed NICs. If you are routing over your server, it should be the outside NIC that has a gateway configured. If you have the second NIC to communicate with a few nodes on the network, your Domain, side NIC should have the gateway configured. So, this is domain specific.
I have just started this all-inclusive fix for of a multihomed DC and would enjoy input on points I might have missed.

I hope this works for you.

complex83Author Commented:
Chief, thanks for the input however I can say for certain that we do not have any multihomed DC's here.

asrdias, I checked into the KB article you referenced and made the specified changes but having mixed results.  I can still only access certain shares (seems like more work than don't work at this point), but some are still not functional.  Since making the registry changes, I have noticed that the error now appears instantaneously whereas prior to the changes it would take nearly a minute to timeout.  

Thanks everyone for all your thoughts and responses, I really appreciate it, hopefully we can figure out what is going on here.
complex83Author Commented:

I even went so far as to re-install the OS and STILL the same problem.  I was able however to determine that the only servers it has issues connecting to do in fact have a common thread.  They are all virtual machines.  It seems that I am unable to connect to any share on a VM using the hostname however real physical boxes work without a problem.  

I'm guessing this must be an issue with VMWare then.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.