Time synce problems in windows xp

Edited Dec 19, at UTC. Wireshark View this "Best Answer" in the replies below ». Popular Topics in General Windows. Spiceworks Help Desk.

The help desk software for IT. Track users' IT needs, easily, and with only the features you need. Learn More ». Thai Pepper. This will cause problems with network access and Windows updates if the time difference is large. If you are not in an AD environment, you will want time sync enabled on the VM host server, and make sure that server has a properly-synced external time source. The question is why the restore from suspend doesn't automatically update the clock.

That's a standard part of the process and why all machines that come out of suspension don't have this problem. It appears that if we "shutdown" the VM instead of suspending it, when we bring the VM back up, the time is syncing correctly with the host machine. At least at this point that appears to be whats happening.

To continue this discussion, please ask a new question. Anunta Followers - Follow. Kelly for Anunta. Get answers from your peers along with millions of IT pros who visit Spiceworks. Hi, Im running VMware Player v4. Popular Topics in Virtualization. I tried every time service — user In the middle of that KB article are some steps that involve changing registry settings. Take a look at the section titled: Configuring the Windows Time service to use an external time source — Sean Earp.

I just remembered the solution that worked for me back in the day when I was building new computers Try setting the time to something close to the real time and try again. If that didn't work, just waiting a day or so usually resolved whatever random intermittent problem I was hitting.

If it's only seconds off, though, I think that's permissible ntp drift, and it would resync properly after not long. I guest you sit behind a firewall. No, no firewall. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Recently I had setup a small domain One domain controller with 8 numbers of XP professional 32bit clients using Windows R2. This particular place has a regular power failure problem which runs into hours of outage and UPS shuts down the server successfully.

However whenever the Server is turned on back, the date and time settings are shown incorrect and the clients fail to authenticate. This domain controller is synched with an external time server and once the time is manually changed everything works fine. Now my question is, whether I can configure the domain controller to rely upon it's hardware clock instead of the external time servers. If yes, what are the areas I need to modify and what kind of changes I should apply.