Problem with NTP Server on domain

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: David Tilman (DavidTilman_at_discussions.microsoft.com)
Date: 01/26/05 

Date: Tue, 25 Jan 2005 16:57:02 -0800

I'm sorry this question is long winded, but I figure the more info the better
(I've changed the server names for this message).

I have setup a Windows 2003 server on a domain to be an authoritive time
server, but clients are getting w32time errors in event viewer (event id 14 &
29). The server is the PDC emulator role. I've set it up to look at the
internal clock as a source. The
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\AnnounceFlags"
key value is set to 0x0000000a. The
"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters\Type" key value is set to "NoSync".
I've run the "net stop w32time && net start w32time" command and restarted
the computer.

When running dcdiag, I'm getting this:

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

and this:

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.

When I run "w32tm /monitor" from a client on the domain I get this:

Server1.domain.local *** PDC *** [192.168.90.10]:
    ICMP: 0ms delay.
    NTP: +0.0000000s offset from Server1.domain.local
        RefID: unspecified / unsynchronized [0.0.0.0]
Server2.domain.local [192.103.209.23]:
    ICMP: 0ms delay.
    NTP: +42.7812500s offset from Server1.domain.local
        RefID: unspecified / unsynchronized [0.0.0.0]

Should the RefID have something besides 0.0.0.0? Does this indicate a DNS
problem? There is a _ldap entry in DNS in _msdcs under the domain. Any help
would be appreciated.

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)