Windows 2003 Virtual Server on Hypervisor - Slow Ping Response

I have a Windows 2003 server running as a virtual server on Windows
2008 Hypervisor
SERVER-A consistently pings external destinations at 30-60ms response time
SERVER-B ping response is 2000ms to the same external sites.
How can this be when they are actuallu using the same physical NIC and connection?

NOTE - even though the SERVER-B ping times are 2 seconds the actual ping "Reply from" lines on the screen come up really quick - much quicker than normal ping output.

SERVER-A  is  192.168.1.1
SERVER-B  is  192.168.1.2 in the same subnet

Only a single physical NIC is enabled on the 2008 server and the Hypervisor Virtual Network Manager  has an External LAN linked to this NIC.
The virtual computer only has a single NIC enabled.

A second physical NIC is available on the 2008 server but not currently used.

SERVER-A ping trace
Pinging www.l.google.com [66.102.11.104] with 32 bytes of data:
Reply from 66.102.11.104: bytes=32 time=47ms TTL=245
Reply from 66.102.11.104: bytes=32 time=52ms TTL=245
Reply from 66.102.11.104: bytes=32 time=95ms TTL=245
Reply from 66.102.11.104: bytes=32 time=57ms TTL=245
Reply from 66.102.11.104: bytes=32 time=39ms TTL=245
Reply from 66.102.11.104: bytes=32 time=41ms TTL=245
Reply from 66.102.11.104: bytes=32 time=38ms TTL=245
Reply from 66.102.11.104: bytes=32 time=67ms TTL=245
Reply from 66.102.11.104: bytes=32 time=47ms TTL=245
Reply from 66.102.11.104: bytes=32 time=92ms TTL=245

SERVER-B Ping Trace
Pinging www.l.google.com [66.102.11.104] with 32 bytes of data:
Reply from 66.102.11.104: bytes=32 time=47ms TTL=245
Reply from 66.102.11.104: bytes=32 time=52ms TTL=245
Reply from 66.102.11.104: bytes=32 time=95ms TTL=245
Reply from 66.102.11.104: bytes=32 time=57ms TTL=245
Reply from 66.102.11.104: bytes=32 time=39ms TTL=245
Reply from 66.102.11.104: bytes=32 time=41ms TTL=245
Reply from 66.102.11.104: bytes=32 time=38ms TTL=245
Reply from 66.102.11.104: bytes=32 time=67ms TTL=245
Reply from 66.102.11.104: bytes=32 time=47ms TTL=245
Reply from 66.102.11.104: bytes=32 time=92ms TTL=245
DerekStonemanAsked:
Who is Participating?
 
Darius GhassemCommented:
Yes, sometimes the Network Adapter doesn't work with the Hyper-V service so the Legacy Adapter usually works. If you have installed the most updated integration components then you will have to use the Legacy because the integration services allow the use for the Network Adapter but even with those installed you will have to use the Legacy which will work not matter what.
0
 
Darius GhassemCommented:
Derek,

I don't see a difference in the pings.
0
 
DerekStonemanAuthor Commented:
Additional information.
I have noticed that this problem only occurs with a 2003 server running virtually.
I have reproduced the same fault on another site that also has a Windows 2003 server running under hypervisor.
On this site there is also a Windows 2008 server running virtually on the same physical server that does not have the slow ping response times.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Darius GhassemCommented:
What type of Network do you have installed on the Hyper-V VMs?
0
 
DerekStonemanAuthor Commented:
Revised ping times for Server B
Pasted the same settings in twice.
Pinging www.l.google.com [66.102.11.104] with 32 bytes of data:

Reply from 66.102.11.104: bytes=32 time=2593ms TTL=245
Reply from 66.102.11.104: bytes=32 time=2596ms TTL=245
Reply from 66.102.11.104: bytes=32 time=2595ms TTL=245
Reply from 66.102.11.104: bytes=32 time=2594ms TTL=245
Reply from 66.102.11.104: bytes=32 time=2595ms TTL=245
Reply from 66.102.11.104: bytes=32 time=2597ms TTL=245
Reply from 66.102.11.104: bytes=32 time=2414ms TTL=245
Reply from 66.102.11.104: bytes=32 time=2596ms TTL=245
Reply from 66.102.11.104: bytes=32 time=2593ms TTL=245
Reply from 66.102.11.104: bytes=32 time=2594ms TTL=245
0
 
DerekStonemanAuthor Commented:
Dariusq - not sure I understand the question.
The Windows 2003 Server VM has a single NIC (Microsoft Virtual Machine Bus Network Adapter)
using Client for Microsoft Networking & TCP/IP protocols
0
 
Darius GhassemCommented:
If you go to the settings of the VM what type of adapter is installed? Legacy?
0
 
DerekStonemanAuthor Commented:
The adapter was installed using "Network Adapter" as the device type.
I have since changed to "Legacy Network Adapter" and removed the original and the problem seems to have been resolved.
Does that make sense?
0
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.