gregurl
asked on
Windows 2000 VMWare Virtual machine time and ping slow
I had P2V a physical Windows 2000 server to VMWare ESX 3.1 about 3 months ago.
I have notice recently that the clock has been running slow. Also when I ping out of the server, I always get a 10ms response. If I ping from a server to the converted Windows 2000 server, the ping goes to a normal 1ms on the local LAN.
I think the slow ping times and clock are related. What should I check for?
I have notice recently that the clock has been running slow. Also when I ping out of the server, I always get a 10ms response. If I ping from a server to the converted Windows 2000 server, the ping goes to a normal 1ms on the local LAN.
I think the slow ping times and clock are related. What should I check for?
ASKER
No other issues with networking.
I found that 10ms is the way Windows 2000 reports the ping times versus the 1ms of Windows 2003.
As for the time, it is not syncing with the host time but with active directory.
I can tell that the time is slowly losing time versus the actual time as minutes pass.
I was wondering because 4 vCPUs had been converted over in the p2v that the machine is having issues with the multiple CPUs assigned to the older Windows 2000 server.
I found that 10ms is the way Windows 2000 reports the ping times versus the 1ms of Windows 2003.
As for the time, it is not syncing with the host time but with active directory.
I can tell that the time is slowly losing time versus the actual time as minutes pass.
I was wondering because 4 vCPUs had been converted over in the p2v that the machine is having issues with the multiple CPUs assigned to the older Windows 2000 server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Yes. 10ms is Windows 2003 standard ping time.
Have you installed VMware Tools, to sync the Virtual Machine to the Host time, of if you have VMware Tools installed, have you ticked the Box to enable time sync?