NTPClient on DC fails to contact time source (W2K3 R2 64-bit)

Our W2K3 R2 64-bit DC has been up and running for some time, and getting
time updates regularly.

Last week, it started a spate of failed attempts which have become rather
chronic.

First, I followed advice to set the time source:

w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL
net stop w32time
net start w32time
w32tm /resync

Had no luck. I verified that TCP & UDP ports 123 were available to the
server and tested successfully with:

w32tm /monitor /computers:time.nist.gov

I also re-registered the service with:

net stop w32time
w32tm /unregister
w32tm /register
net start w32time

Also to no avail.

I did find a hotfix related (830092), but it appears it is only for the
32-bit version.

Anything else I can try?

Meinolf
Wed Apr 30 01:34:15 PDT 2008

Hello Dvord,

What happend, if you choose another time server? Is that the only DC in your
domain?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Our W2K3 R2 64-bit DC has been up and running for some time, and
> getting time updates regularly.
>
> Last week, it started a spate of failed attempts which have become
> rather chronic.
>
> First, I followed advice to set the time source:
>
> w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL
> net stop w32time
> net start w32time
> w32tm /resync
> Had no luck. I verified that TCP & UDP ports 123 were available to
> the server and tested successfully with:
>
> w32tm /monitor /computers:time.nist.gov
>
> I also re-registered the service with:
>
> net stop w32time
> w32tm /unregister
> w32tm /register
> net start w32time
> Also to no avail.
>
> I did find a hotfix related (830092), but it appears it is only for
> the 32-bit version.
>
> Anything else I can try?
>

Dvord
Wed Apr 30 09:08:38 PDT 2008

Thanks Meinolf,

Different time server, same results.

The resync command generates this response:

Sending resync command to local computer...
The computer did not resync because no time data was available.




"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb6697fea8ca78c4df225bb0@msnews.microsoft.com...
> Hello Dvord,
>
> What happend, if you choose another time server? Is that the only DC in
> your domain?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Our W2K3 R2 64-bit DC has been up and running for some time, and
>> getting time updates regularly.
>>
>> Last week, it started a spate of failed attempts which have become
>> rather chronic.
>>
>> First, I followed advice to set the time source:
>>
>> w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL
>> net stop w32time
>> net start w32time
>> w32tm /resync
>> Had no luck. I verified that TCP & UDP ports 123 were available to
>> the server and tested successfully with:
>>
>> w32tm /monitor /computers:time.nist.gov
>>
>> I also re-registered the service with:
>>
>> net stop w32time
>> w32tm /unregister
>> w32tm /register
>> net start w32time
>> Also to no avail.
>>
>> I did find a hotfix related (830092), but it appears it is only for
>> the 32-bit version.
>>
>> Anything else I can try?
>>
>
>

Dvord
Wed Apr 30 09:51:01 PDT 2008

I apologize I didn't answer the second question.

No it is not. I have two DC's.


"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb6697fea8ca78c4df225bb0@msnews.microsoft.com...
> Hello Dvord,
>
> What happend, if you choose another time server? Is that the only DC in
> your domain?
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Our W2K3 R2 64-bit DC has been up and running for some time, and
>> getting time updates regularly.
>>
>> Last week, it started a spate of failed attempts which have become
>> rather chronic.
>>
>> First, I followed advice to set the time source:
>>
>> w32tm /config /manualpeerlist:time.nist.gov,0x8 /syncfromflags:MANUAL
>> net stop w32time
>> net start w32time
>> w32tm /resync
>> Had no luck. I verified that TCP & UDP ports 123 were available to
>> the server and tested successfully with:
>>
>> w32tm /monitor /computers:time.nist.gov
>>
>> I also re-registered the service with:
>>
>> net stop w32time
>> w32tm /unregister
>> w32tm /register
>> net start w32time
>> Also to no avail.
>>
>> I did find a hotfix related (830092), but it appears it is only for
>> the 32-bit version.
>>
>> Anything else I can try?
>>
>
>