Cannot get clients or second DC to synch time with PDC Emulator.

[Guest Matthew Adkins]

One of my customers has 2 Windows 2003 DCs and about 50 desktops running

Windows XP Pro SP2. Both DCS had the time settings screwed up in the registry

and in group policy and the desktops were not updating time except on bootup

through a login script.

I changed the group policy settings back to where an internet poist said

they should be and then deregistered w32tm and re-registered the .dll in

order to reset the registry settings in both DCs.

I then added the external time synch info for the PDC and it instantly began

pulling time on the PDC emulator. No matter what I try, though, I cannot get

the other DC to synch time. AD and DNS are passing all tests and replication

is working fine.

Both DCs run DNS and pass netdiag and dcdiag.

I am seeing (from the second DC):

 

C:\Program Files\Support Tools>w32tm /monitor

xxxxx-ml350.xxxxx.local [192.168.200.251]:

ICMP: 0ms delay.

NTP: error ERROR_TIMEOUT - no response from server in 1000ms

mail.xxxxx.local *** PDC *** [192.168.200.252]:

ICMP: 0ms delay.

NTP: error ERROR_TIMEOUT - no response from server in 1000ms

 

 

C:\Program Files\Support Tools>net time /querysntp

The current SNTP value is: mail.xxxxx.local,0x1

(note: this was manually put in by me)

 

 

 

The DC container has blocked policy inheritence and the Default domain

control GPO is the only GPO linked to the DC container and non of the time

settings are configured except enable NTP client.

 

This is driving me nuts. I appreciate any help. Thank you.

[Guest Ryan Hanisco]

RE: Cannot get clients or second DC to synch time with PDC Emulator.

 

Have you tried:

 

net time /domain:<domainName> /set

 

 

--

Ryan Hanisco

MCSE, MCTS: SQL 2005, Project+

http://www.techsterity.com

Chicago, IL

 

Remember: Marking helpful answers helps everyone find the info they need

quickly.

 

 

"Matthew Adkins" wrote:

> One of my customers has 2 Windows 2003 DCs and about 50 desktops running

> Windows XP Pro SP2. Both DCS had the time settings screwed up in the registry

> and in group policy and the desktops were not updating time except on bootup

> through a login script.

> I changed the group policy settings back to where an internet poist said

> they should be and then deregistered w32tm and re-registered the .dll in

> order to reset the registry settings in both DCs.

> I then added the external time synch info for the PDC and it instantly began

> pulling time on the PDC emulator. No matter what I try, though, I cannot get

> the other DC to synch time. AD and DNS are passing all tests and replication

> is working fine.

> Both DCs run DNS and pass netdiag and dcdiag.

> I am seeing (from the second DC):

>

> C:\Program Files\Support Tools>w32tm /monitor

> xxxxx-ml350.xxxxx.local [192.168.200.251]:

> ICMP: 0ms delay.

> NTP: error ERROR_TIMEOUT - no response from server in 1000ms

> mail.xxxxx.local *** PDC *** [192.168.200.252]:

> ICMP: 0ms delay.

> NTP: error ERROR_TIMEOUT - no response from server in 1000ms

>

>

> C:\Program Files\Support Tools>net time /querysntp

> The current SNTP value is: mail.xxxxx.local,0x1

> (note: this was manually put in by me)

>

>

>

> The DC container has blocked policy inheritence and the Default domain

> control GPO is the only GPO linked to the DC container and non of the time

> settings are configured except enable NTP client.

>

> This is driving me nuts. I appreciate any help. Thank you.

>