The computer did not resync because no time date was available

When you use the command w32tm /resync, you receive this error. Why? A number of reasons. You do need to open port 123 UDP on your firewall for the domain controller so it can reach the external time source. If you want to sync your clients to your DC, you probably edited a domain policy to allow this to happen. The catch what I noticed is that it’s most likely that your DC is part of this domain policy. By having a NTP client configured there, the DC will not sync to the external time source. Mistake, yes. Fix, well, create another policy JUST for your clients and specify your NTP client information there conneting to your DC. As for the domain policy, put all time related configurations as NOT CONFIGURED. By doing this, I was able to issue the w32tm /resync command succesfully.




Related posts:

  1. How to list user’s domain group memberships
  2. A domain controller for the domain could not be contacted
  3. Slow RDP into Windows Server 2003 SP2 x64 using Vista 64
  4. How to force client to connect to WSUS server
  5. How to force group policy

You can follow any responses to this entry through the RSS 2.0 feed.