Re: DC Time Server Problem after DC hardware migration

Have you followed this KB to configure your DC? If not follow through on
this and see if it doesn't resolve it for you.

http://support.microsoft.com/kb/216734/

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA
http://www.pbbergs.com/

This posting is provided "AS IS" with no warranties, and confers no rights.


"Terry" <TAbingham@xxxxxxxxx> wrote in message
news:1142467884.367044.123340@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
This problem exists on a Win2k SP4 server

I recently moved my (only) PDC to a new hardware platform. Most of this
process went smoothly. I got hung up for a bit on the new hardware
taking over from the old because of Replication problems (which I was
able to resolve).
Once the replication problem was resolved, I was then able to complete
the transition and demote the old PDC to a member server.

I have only one problem that I can see with the new hardware.

When I run DCDiag, I get errors in the output regarding the new
hardware advertising as a time server. The text below shows the ONLY
errors I receive from DCDiag (even running a full, verbose test)

Starting test: Advertising
Warning: BINGPDC is not advertising as a time server.
......................... BINGPDC failed test Advertising


...
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.
......................... bingdom.com failed test FsmoCheck

I've read KB articles about the W32Time service, configured the
registry, bounced the time service, rebooted the PDC, made sure the
service is running, etc., etc.

I've even seen in my event logs from the PDC that the time service IS
synchronizing to the external source:
Source: w32time
Event ID: 0
Description: The Time service synced time from time source
(POOL.NTP.ORG) .

If I do a 'net time' command on my client PC's (WinXP SP2), they
timeout with the error message:

Could not locate a time-server.

At this point, I can't think of anything else to check or to do.

This PDC hosts my DNS, DHCP, AD (everything for the domain--it's a very
small home domain)

Please help!
Thanks



.

Relevant Pages

  • Re: Time Sync Issue - Win2003 Domain
    ... be using the PDCe as their time service. ... that the clients that are improperly getting their time are in fact doing ... Emulator) SHOULD be the preferred time server for all domain clients. ... corporate PDC. ...
    (microsoft.public.windows.server.active_directory)
  • time service
    ... i can't make the pdc a time server using the software i have because it is a cluster node and it disables the time service which could cause a problem since it is important that the time service runs for the cluster. ... Configure to sync from External time source using the net command, 'net time /setsntp:'. ...
    (microsoft.public.win2000.advanced_server)
  • time service
    ... i can't make the pdc a time server using the software i have because it is a cluster node and it disables the time service which could cause a problem since it is important that the time service runs for the cluster. ... Configure to sync from External time source using the net command, 'net time /setsntp:'. ...
    (microsoft.public.win2000.networking)
  • time service
    ... i can't make the pdc a time server using the software i have because it is a cluster node and it disables the time service which could cause a problem since it is important that the time service runs for the cluster. ... Configure to sync from External time source using the net command, 'net time /setsntp:'. ...
    (microsoft.public.win2000.general)
  • Re: Change Domain Time Server
    ... If I do a simple net time command, this should return the domain time server time, right? ... You are missing the time source on your registry. ... Your pdc should now return the correct time and you can now sync all other DCs to get time from the PDC. ...
    (microsoft.public.windows.server.general)
Loading