DC Not Advertising As A Time Server?

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
1355
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 does hold all 5.

Any ideas? Thanks for any insight!

Justin

By default, the root parent domain controller will not synchronize to a time
source. The root parent domain controller can be set to either synchronize
to a known and trusted Internet-based time source, or a hardware time device
that provides an NTP (Network Time Protocol) or SNTP interface. Its time
accuracy can also be maintained manually.

See:

http://www.microsoft.com/technet/pro.../26_s3wts.mspx

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Justin Emlay" <(E-Mail Removed)> wrote in message
news:O%(E-Mail Removed)...
> 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
> 1355
> 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 does hold all 5.
>
> Any ideas? Thanks for any insight!
>
> Justin
>
>

Thanks for the help Doug!

I read through some of that page however I still dont see what the problem
is.

What exactly needs to be setup?

Example:
Install Windows 2003
Setup DNS
Run DCPROMO
Install Support Tools
Run DCDIAG

DCDIAG finishes with no problems. Nothing else should have to be setup.

Another thing I've noticed is the following:

When I right right click the DC server in replication monitor and go to
Properties then Server Flags there is an X next to the time service line.
The time service is running and I can stop and start it with no problems.

I unregistered w32tm and re-registered it and I have the same problem.