asked on

Hyper V - Specified Network name is no longer available.

I have a Dell PowerEdge 2950 server running Hyper V. I have 6 guests on this host.

The domain controller for this network (Server 2003) is a VM on this host. Another VM is used for the mail server (Exchange 2003/Server 2003), as well as a file server on Server 2008.

If large files (over 10mb or so) are copied over our site to site VPN, they always fail with the message "specified network name is no longer available" however the mapped drive is still visible.

I did some testing, and this occurs when the file shares are on one of the VM's. If the files are directly on the Hyper V host itself, the issue does not occur. I can only assume its a network setting within the Virtual Network Manager or the VM's themselves...

Tips appreciated.

Naga Bhanu Kiran Kota

hi,

Can you confirm the OS running on the problem VM and if possible turn off SNP on that machine. This feature introduced in Win2003 R2 and continued has caused problems many a time.

Try disabling TCPChimney as mentioned in this MS KB article

http://support.microsoft.com/kb/951037

regards
bhanu

colditzz

This maybe applicable to your situation.
http://go.microsoft.com/fwlink/?LinkId=201917

ASKER CERTIFIED SOLUTION

mikeshaver

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

mikeshaver

ASKER

installed new NIC

the_cyman

It might have been TOE... TOE tends to mess up VMware and HyperV clients. It should be disabled according to the manufacturers instructions.