Results 1 to 6 of 6

Thread: Clients sync to wrong NTP DC

  1. #1
    johnisccp Guest

    Clients sync to wrong NTP DC

    I have three W2K DCs. One is in the remote site and the other two DCs are in
    the Corp office. I setup the FSMO DC at corp office to get its time from the
    router. For some reason all the clients are getting its time from the remote
    DC. I compare the two DCs registry entry for W32Time. Everything looks the
    same except the registry entry "type". The remote DC has a the "type REG_SZ
    Nt5DS" and the FSMO DC has a "type REG_SZ NTP". Does it matter what the type
    is in the registry? I am trying to make sure the clients are sync their time
    to the FSMO DC and not the remote DC. I ran net time on my machine and it is
    show:
    C:\>net time
    Current time at \\AUSTINFS1 is 2/12/2008 11:07 AM

    Local time (GMT-06:00) at \\AUSTINFS1 is 2/12/2008 10:07 AM

    The command completed successfully.



  2. #2
    Newell White Guest
    Yes, the registry controls wat syncs with what.

    The types available are:
    NT5DS = sync with a DC higher up the order (PDC emulator in our LAN)
    NTP = sync with the NTP provider whose URL is specified in the registry
    entry about 3 lines up the page
    NoSync = free run

    So remote DC should be NT5DS, and FSMO should be NTP if synced to external
    provider or LAN time source, or free run if you don't care about the time in
    the rest of the universe.

    Is that is the case, then how can I make all the clients to sync with the
    FSMO DC and not the remote DC?

  3. #3
    thomville Guest
    As long as the clients are using type "NT5DS," which is the default
    setting, the will authenticate on login against (in this order), the
    DC holding the PDC Emulator role, the DC they logged in against,
    another server, another workstation.

    Do you have a domain environment? Make sure the DC with the PDCEmulator role
    sync to an external time source. On clients and member servers check that
    the time zone is the same and that port123 UDP is opened when a firewall
    is in use.

    Wich error messages are in the event viewer from the clients?

    Does XP SP3 do anything to block port 123??
    I am having the same problem with 1 machine in a small 2003 domain.

  4. #4
    Join Date
    Jun 2009
    Posts
    1

    Clients time dosn't sync to server: Envrmnt 2008 server and windows xp

    Hi

    I have newly installed windows 2008 server and client side xp but time sync is not done in my clients(xp).
    My clients are not showing correct time server showing correct time. They are not able to sync with server.
    Please help me.

  5. #5
    Meinolf Weber [MVP-DS] Guest

    Re: Clients sync to wrong NTP DC

    Hello Rich,

    Depends on the built in firewall. If activated, just disable and test again.
    If it works then you have to configure it to open the port.

    Best regards

  6. #6
    Syed Khairuddin Guest

    Re: Clients sync to wrong NTP DC

    can you please try this command and from cmd

    w32tm /monitor

    and paste the conteents here.

    Thanks

Similar Threads

  1. Facebook Photo Sync app error "Something went wrong"
    By jacob2013 in forum Windows Software
    Replies: 4
    Last Post: 05-09-2013, 12:01 AM
  2. wlan clients unable to ping lan clients with WAG320N
    By connoisseur in forum Networking & Security
    Replies: 3
    Last Post: 25-06-2012, 06:46 PM
  3. Unable to sync iphone 4 due to sync session failed to finish
    By Nabhanyu in forum Portable Devices
    Replies: 2
    Last Post: 03-09-2011, 03:56 AM
  4. Windows Live Sync beta blends the best of Sync and Mesh
    By Fox28 in forum Windows Software
    Replies: 3
    Last Post: 17-08-2010, 06:26 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,967,354.67565 seconds with 17 queries