Domain Controller Not Advertising As A Time Server? (dcdiag)
Posted on 2004-04-30
When I run dcdiag here is my result:
Doing primary tests
Testing server: Default-First-Site-Name\FILE
Starting test: Advertising
Warning: FILE is not advertising as a time server.
......................... FILE failed test Advertising
Starting test: Services
......................... FILE passed test Services
***** Everything Else Passes *****
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.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
A Good Time Server could not be located.
Why would my "only" DC not be advertising as a time server? As you can see
the time service is running as the services test passed. I went to a
different domain and stopped the time service and it to received the same
exact errors as above. However when turned back on the dcdiag came back
100% good. I cant figure out why my DC is doing this.
I also used a script I found on the iNet to check the fsmo roles that the
server holds and it holds all 5.
I'm also assuming all three errors are related. Any ideas? Thanks for any insight!
p.s. this error is keeping me from upgrading my exchange server from 2000 to 2003.