the easiest way we've found to get around this is to time synch all your
servers. You can do with this the the net time \\time0a.nist.gov /SET /YES
-----Original Message-----
From: Schaub, Chris [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, September 25, 2001 10:33 AM
To: NT System Admin Issues
Subject: W2K Time service issues
Starting about a month ago we started to receive the following errors on
DC's throughout our enterprise:
1st error
Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 56
Date: 9/25/2001
Time: 8:20:16 AM
User: N/A
Computer: ServerY
Description:
The Domain Controller Server X in tld.domain.com returned an incorrectly
signed time stamp. If this DC is from the machine's parent domain then the
trust link between the domains may be broken and must be fixed. If the DC is
from this machine's own domain, then the machine password for this machine
is incorrect and should be corrected.
Data:
0000: e5 03 00 00 �...
2nd error
Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 11
Date: 9/25/2001
Time: 8:20:21 AM
User: N/A
Computer: ServerY
Description:
The NTP server \\Serverx.tld.domain.com didn't respond
Data:
0000: 00 00 00 00 ....
We see this problem when a lower level server (Servery.2ld.tld.domain.com)
tries to sync off of the server (serverx.tld.domain.com). So basically the
child domain DC is trying to sync with a parent level DC and getting these
errors. NTP on the parent level domain controller seems to be working for
manual calls for other clients. Also the trust between the two domains
seems to be intact. And it is happening on multiple servers in both
domains. Also this did use to work before a month ago. If anyone has some
insight.
Thanks,
Chris
Want to unsub? Do that here:
http://lyris.sunbelt-software.com/scripts/lyris.pl?enter=ntsysadmin&text_mod
e=0&lang=english
Want to unsub? Do that here:
http://lyris.sunbelt-software.com/scripts/lyris.pl?enter=ntsysadmin&text_mode=0&lang=english
