Running dcdiag on a windows 2003 native AD domain.. Simple, one domain, one forest, three domain controllers all of them GCs.
Every AD server returns this error: DC1 is not advertising as a time server.
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
ED) call failed, error 1355
A Good Time Server could not be located.
I have done all of this:
Netdom query pdc runs fine on all of the servers, returns the correct pdc emulator. Everything seems to be fine except that error in dcdiag and Event ID: 14 is in one AD server's log multiple times: The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 240 minutes.
This server is on a different subnet than the other two. I just ran w32tm on the other AD server (non pdc emulator) and it returned 'the computer did not resync because no time data was available' and logged an event id: 14 in the system log.
This one has me stumped.. any ideas how to fix this? I want to upgrade the domain to AD 2008, but am afraid to with this happening.