locked
PDC can not sync time via NTP RRS feed

  • Question

  • Hello everyone,

    I'm struggling with a big problem. This morning I realized that all my clients a running with wrong time. Time sync within my domain works fine - the PDC refuses to sync time with external time servers. My PDC is a Win 2012 VM running on a 2019 S2D Cluster. Time synchronization with the HV is disabled. All HVs a recieving the wrong time from my DCs.

    Time difference is approximately minus 8 hrs. My PDC tell me its time source would be "Local CMOS clock". NTP was configured before und worked without problems. So I tried to reconfigre my time service:

    w32tm.exe /config /manualpeerlist:"0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.org" /syncfromflags:manual /reliable:YES /update
    net stop win32time && net start win32time


    It seems that the NTP client recieves no (valid) data. Example output from the W32TimeDebug log:

    153149 03:20:06.4972712s - AddNewPendingPeer: manual
    153149 03:20:06.4972712s - Polling peer 2.de.pool.ntp.org (ntp.m|0x0|0.0.0.0:123->213.172.105.106:123)
    153149 03:20:06.4972712s - PeerPollingThread: PeerListUpdated
    153149 03:20:06.4972712s - Sending packet to 2.de.pool.ntp.org (ntp.m|0x0|0.0.0.0:123->213.172.105.106:123) in Win2K detect mode, stage 1.
    153149 03:20:06.4972712s - PeerPollingThread: waiting 0.109s
    153149 03:20:06.4972712s - No response from peer 2.de.pool.ntp.org (ntp.m|0x0|0.0.0.0:123->213.172.105.106:123).
    153149 03:20:06.4972712s - 5 Age:0 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0096468s Dst:16.0096468s FDsp:08.0000000s
    153149 03:20:06.4972712s - 4 Age:3 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0096460s Dst:16.0096460s FDsp:12.0000000s
    153149 03:20:06.4972712s - 3 Age:2 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0096460s Dst:16.0096460s FDsp:14.0000000s
    153149 03:20:06.4972712s - 2 Age:1 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0096460s Dst:16.0096460s FDsp:15.0000000s
    153149 03:20:06.4972712s - 1 Age:4 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0089056s Dst:16.0089056s FDsp:15.5000000s
    153149 03:20:06.4972712s - 0 Age:5 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0044456s Dst:16.0044456s FDsp:15.7500000s
    153149 03:20:06.4972712s - Logging information: NtpClient has not received response from server 2.de.pool.ntp.org (ntp.m|0x0|0.0.0.0:123->213.172.105.106:123).
    153149 03:20:06.4972712s - Logging information: NtpClient: No response has been received from manual peer 2.de.pool.ntp.org (ntp.m|0x0|0.0.0.0:123->213.172.105.106:123) after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer from which to synchronize.


    If I run the stripchart command I can see a big offset:

    C:\Windows\system32>w32tm /stripchart /computer:de.pool.ntp.org /dataonly
    Tracking de.pool.ntp.org [144.76.0.164:123].
    The current time is 23.04.2020 05:45:36.
    05:45:36, +32723.4797195s
    05:45:38, +32723.4729284s

    My time zone is correctly set:

    C:\Windows\system32>w32tm /tz
    Time zone: Current:TIME_ZONE_ID_DAYLIGHT Bias: -60min (UTC=LocalTime+Bias)
      [Standard Name:"W. Europe Standard Time" Bias:0min Date:(M:10 D:5 DoW:0)]
      [Daylight Name:"W. Europe Daylight Time" Bias:-60min Date:(M:3 D:5 DoW:0)]

    My current config looks like this:

    C:\Windows\system32>w32tm /query /configuration /verbose
    [Configuration]
    
    EventLogFlags: 2 (Local)
    AnnounceFlags: 5 (Local)
    TimeJumpAuditOffset: 28800 (Local)
    MinPollInterval: 6 (Local)
    MaxPollInterval: 10 (Local)
    MaxNegPhaseCorrection: 172800 (Local)
    MaxPosPhaseCorrection: 172800 (Local)
    MaxAllowedPhaseOffset: 300 (Local)
    
    FrequencyCorrectRate: 4 (Local)
    PollAdjustFactor: 5 (Local)
    LargePhaseOffset: 50000000 (Local)
    SpikeWatchPeriod: 900 (Local)
    LocalClockDispersion: 10 (Local)
    HoldPeriod: 5 (Local)
    PhaseCorrectRate: 7 (Local)
    UpdateInterval: 100 (Local)
    
    FileLogName: c:\EventLogs\W32Time\w32time.log (Local)
    FileLogEntries: 0-116 (Local)
    FileLogSize: 10000000 (Local)
    FileLogFlags: 0 (Undefined or NotUsed)
    
    [TimeProviders]
    
    NtpClient (Local)
    DllName: C:\Windows\system32\w32time.DLL (Local)
    Enabled: 1 (Local)
    InputProvider: 1 (Local)
    CrossSiteSyncFlags: 0 (Undefined or NotUsed)
    AllowNonstandardModeCombinations: 1 (Local)
    ResolvePeerBackoffMinutes: 15 (Local)
    ResolvePeerBackoffMaxTimes: 7 (Local)
    CompatibilityFlags: 2147483648 (Local)
    EventLogFlags: 1 (Local)
    LargeSampleSkew: 3 (Local)
    SpecialPollInterval: 3600 (Local)
    Type: NTP (Local)
    NtpServer: 0.de.pool.ntp.org 1.de.pool.ntp.org 2.de.pool.ntp.org 3.de.pool.ntp.o
    rg (Local)
    
    NtpServer (Local)
    DllName: C:\Windows\system32\w32time.DLL (Local)
    Enabled: 1 (Local)
    InputProvider: 0 (Local)
    AllowNonstandardModeCombinations: 1 (Local)
    EventLogFlags: 0 (Undefined or NotUsed)
    
    VMICTimeProvider (Local)
    DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
    Enabled: 1 (Local)
    InputProvider: 1 (Local)

    I tried many different time servers. I tried it with DNS and IP. It always rejects the responses and falls back to local cmos clock.

    I really hope one of you can help me out here...

    Thursday, April 23, 2020 5:25 PM

Answers

  • Sounds like something is blocking the inbound UDP 123 Some ISPs do this, so I'd check with your ISP about this issue. I fought this issue for a while and like you got success replies via /stripchart but unfortunately message analyzer confirmed the reply comes back on another port and also found AT&T blocking inbound UDP 123

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    • Edited by Dave PatrickMVP Thursday, April 23, 2020 6:16 PM
    • Marked as answer by St_Marcel Friday, April 24, 2020 12:03 PM
    Thursday, April 23, 2020 5:46 PM
  • Hello,

    Thank you for posting in our TechNet forum.

    Have you checked the information provided? Hope they will be helpful. 

    Here we would like to share with you the information about Configuring the Windows Time service to use an external time source
    https://support.microsoft.com/en-gb/help/816042/how-to-configure-an-authoritative-time-server-in-windows-server 

    For any question, please feel free to contact us.


    Best regards,
    Hannah Xiong

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Friday, April 24, 2020 5:28 AM

All replies

  • Sounds like something is blocking the inbound UDP 123 Some ISPs do this, so I'd check with your ISP about this issue. I fought this issue for a while and like you got success replies via /stripchart but unfortunately message analyzer confirmed the reply comes back on another port and also found AT&T blocking inbound UDP 123

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    • Edited by Dave PatrickMVP Thursday, April 23, 2020 6:16 PM
    • Marked as answer by St_Marcel Friday, April 24, 2020 12:03 PM
    Thursday, April 23, 2020 5:46 PM
  • As Dave has said, please check the required port communication status for the time service(UDP port 123)

    1. Allow UDP port 123 from your cooperate Firewall/Proxy 
    2. check the turning off Windows firewall
    3. Check the status turning off AV
    4. Check the service status
    5. Try by registering and re registering the time service

    for further troubleshooting, please refer below

    https://gallery.technet.microsoft.com/Troubleshoot-Windows-time-60fa8dad?redir=0


    • Edited by Udara Kaushalya Thursday, April 23, 2020 9:57 PM added additionally
    Thursday, April 23, 2020 9:55 PM
  • Hello,

    Thank you for posting in our TechNet forum.

    Have you checked the information provided? Hope they will be helpful. 

    Here we would like to share with you the information about Configuring the Windows Time service to use an external time source
    https://support.microsoft.com/en-gb/help/816042/how-to-configure-an-authoritative-time-server-in-windows-server 

    For any question, please feel free to contact us.


    Best regards,
    Hannah Xiong

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Friday, April 24, 2020 5:28 AM
  • Hi everyone, thanks for your support. The time time difference is slowly increasing. Yesterdays delay was about 8 hours. Todays is about 10 hours.

    I disabled FW and AV before I followed the manual configuration steps mentioned in Hannahs link.

    I added an internal time server (name changed to INTERNAL...) which not part of our Windows infrastructure and two external time servers. Alle time servers seem to provides the correct time. I can watch the time offset form the servers increasing.

    The interesting thing is according to my logs, the internal time server seems to deliver correct data:

    Logging information: NtpClient is currently receiving valid time data from INTERNAL-TIMESRV,0x1 (ntp.m|0x1|0.0.0.0:123->INTERNAL-IP.57.8:123).

    But it's beeing rejected at some point. According to the logs it ssems that the external time servers are not reachable (but I can get my time stamps via the stripchart command?!, I will investigate what Dave mentioned above and talk to our central IT department).

    153150 00:01:56.2391945s - Association: (Local) 0.0.0.0:123 => 192.53.103.108:123 (Remote)
    153150 00:01:56.2391945s - Association: (Local) [::]:123 => [2001:638:610:be01::108]:123 (Remote)
    153150 00:01:56.2391945s - Created reachability group: (
    153150 00:01:56.2391945s - 192.53.103.108:123,
    153150 00:01:56.2391945s - [2001:638:610:be01::108]:123,
    153150 00:01:56.2391945s - )
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.000s
    153150 00:01:56.2391945s - PeerPollingThread: WaitTimeout
    153150 00:01:56.2391945s - Reachability: Attempting to contact peer ptbtime1.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.108:123).
    153150 00:01:56.2391945s - Polling peer ptbtime1.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.108:123)
    153150 00:01:56.2391945s - Sending packet to ptbtime1.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.108:123) in Win2K detect mode, stage 1.
    153150 00:01:56.2391945s - Peer poll: Max:3600.0000000s (special) Cur:00.0000000s
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.100s
    153150 00:01:56.2391945s - Association: (Local) 0.0.0.0:123 => 192.53.103.104:123 (Remote)
    153150 00:01:56.2391945s - Association: (Local) [::]:123 => [2001:638:610:be01::104]:123 (Remote)
    153150 00:01:56.2391945s - Created reachability group: (
    153150 00:01:56.2391945s - 192.53.103.104:123,
    153150 00:01:56.2391945s - [2001:638:610:be01::104]:123,
    153150 00:01:56.2391945s - )
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.000s
    153150 00:01:56.2391945s - StartListeningThread completed!
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.000s
    153150 00:01:56.2391945s - StartPeerPollingThread completed!
    153150 00:01:56.2391945s - PeerPollingThread: WaitTimeout
    153150 00:01:56.2391945s - NtpServer started.

    The time source is still stucked at "Local CMOS Clock".

    This is a bigger part of the logfile:

    153150 00:01:56.2235700s - Peer INTERNAL-TIMESRV,0x1 (ntp.m|0x1|0.0.0.0:123->INTERNAL-IP.57.8:123) is not Win2K. Setting compat flags.
    153150 00:01:56.2235700s - Peer poll: Max:3600.0000000s (special) Cur:3600.0000000s
    153150 00:01:56.2235700s - Response from peer INTERNAL-TIMESRV,0x1 (ntp.m|0x1|0.0.0.0:123->INTERNAL-IP.57.8:123), ofs: +36331.9217156s
    153150 00:01:56.2235700s - 5 Age:5 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0000000s Dst:16.0000000s FDsp:08.0000000s
    153150 00:01:56.2235700s - 4 Age:4 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0000000s Dst:16.0000000s FDsp:12.0000000s
    153150 00:01:56.2235700s - 3 Age:3 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0000000s Dst:16.0000000s FDsp:14.0000000s
    153150 00:01:56.2235700s - 2 Age:2 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0000000s Dst:16.0000000s FDsp:15.0000000s
    153150 00:01:56.2235700s - 1 Age:1 Ofs:+00.0000000s Dly:+00.0000000s RDly:+00.0000000s Dsp:16.0000000s RDsp:00.0000000s Pnt:00.0000000s Dst:16.0000000s FDsp:15.5000000s
    153150 00:01:56.2235700s - 0 Age:0 Ofs:+36331.9217156s Dly:+00.0312500s RDly:+00.0050812s Dsp:00.0156326s RDsp:00.0023193s Pnt:00.0000000s Dst:00.0312576s FDsp:07.7500000s
    153150 00:01:56.2235700s - Reachability:  peer INTERNAL-TIMESRV,0x1 (ntp.m|0x1|0.0.0.0:123->INTERNAL-IP.57.8:123) is reachable.
    153150 00:01:56.2235700s - Logging information: NtpClient is currently receiving valid time data from INTERNAL-TIMESRV,0x1 (ntp.m|0x1|0.0.0.0:123->INTERNAL-IP.57.8:123).
    153150 00:01:56.2391945s - Association: (Local) 0.0.0.0:123 => 192.53.103.108:123 (Remote)
    153150 00:01:56.2391945s - Association: (Local) [::]:123 => [2001:638:610:be01::108]:123 (Remote)
    153150 00:01:56.2391945s - Created reachability group: (
    153150 00:01:56.2391945s - 192.53.103.108:123,
    153150 00:01:56.2391945s - [2001:638:610:be01::108]:123,
    153150 00:01:56.2391945s - )
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.000s
    153150 00:01:56.2391945s - PeerPollingThread: WaitTimeout
    153150 00:01:56.2391945s - Reachability: Attempting to contact peer ptbtime1.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.108:123).
    153150 00:01:56.2391945s - Polling peer ptbtime1.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.108:123)
    153150 00:01:56.2391945s - Sending packet to ptbtime1.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.108:123) in Win2K detect mode, stage 1.
    153150 00:01:56.2391945s - Peer poll: Max:3600.0000000s (special) Cur:00.0000000s
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.100s
    153150 00:01:56.2391945s - Association: (Local) 0.0.0.0:123 => 192.53.103.104:123 (Remote)
    153150 00:01:56.2391945s - Association: (Local) [::]:123 => [2001:638:610:be01::104]:123 (Remote)
    153150 00:01:56.2391945s - Created reachability group: (
    153150 00:01:56.2391945s - 192.53.103.104:123,
    153150 00:01:56.2391945s - [2001:638:610:be01::104]:123,
    153150 00:01:56.2391945s - )
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.000s
    153150 00:01:56.2391945s - StartListeningThread completed!
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.000s
    153150 00:01:56.2391945s - StartPeerPollingThread completed!
    153150 00:01:56.2391945s - PeerPollingThread: WaitTimeout
    153150 00:01:56.2391945s - NtpServer started.
    153150 00:01:56.2391945s - PeerPollingThread: PeerListUpdated
    153150 00:01:56.2391945s - Reachability: Attempting to contact peer ptbtime2.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.104:123).
    153150 00:01:56.2391945s - Starting 'VMICTimeProvider', dll:'C:\Windows\System32\vmictimeprovider.dll'
    153150 00:01:56.2391945s - Polling peer ptbtime2.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.104:123)
    153150 00:01:56.2391945s - Sending packet to ptbtime2.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.104:123) in Win2K detect mode, stage 1.
    153150 00:01:56.2391945s - PeerPollingThread: PeerListUpdated
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.100s
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.100s
    153150 00:01:56.2391945s - Peer poll: Max:3600.0000000s (special) Cur:00.0000000s
    153150 00:01:56.2391945s - PeerPollingThread: waiting 0.100s
    153150 00:01:56.2391945s - LoadLibrary
    153150 00:01:56.2391945s - Successfully started 3 providers.
    153150 00:01:56.2391945s - W32TmServiceMain: waiting i16.000s (64.000s)
    153150 00:01:56.2235700s - W32TmServiceMain: resync req, irreg already pending.
    153150 00:01:56.2391945s - W32TmServiceMain: waiting i16.000s (64.000s)
    153150 00:01:56.2391945s - W32TmServiceMain: Network Topology Change
    153150 00:01:56.2391945s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
    153150 00:01:56.2391945s - W32TmServiceMain: Network Topology Change
    153150 00:01:56.2391945s - TimeProvCommand([NtpClient], TPC_NetTopoChange) called.
    153150 00:01:56.2391945s - NtpProvider: Network Topology Change
    153150 00:01:56.2391945s - Reachability:  removing peer INTERNAL-TIMESRV,0x1 (ntp.m|0x1|0.0.0.0:123->INTERNAL-IP.57.8:123).  LAST PEER IN GROUP!
    153150 00:01:56.2391945s - Reachability:  removing peer ptbtime1.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.108:123).  
    153150 00:01:56.2391945s - Reachability:  removing peer ptbtime1.ptb.de,0x1 (ntp.m|0x1|[::]:123->[2001:638:610:be01::108]:123).  LAST PEER IN GROUP!
    153150 00:01:56.2391945s - Reachability:  removing peer ptbtime2.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.104:123).  
    153150 00:01:56.2391945s - Reachability:  removing peer ptbtime2.ptb.de,0x1 (ntp.m|0x1|[::]:123->[2001:638:610:be01::104]:123).  LAST PEER IN GROUP!
    153150 00:01:56.2391945s -   Peer (special) now pending: <Name:INTERNAL-TIMESRV,0x1 (ntp.m|0x1|0.0.0.0:123->INTERNAL-IP.57.8:123) poll:3600 diff:2133401055 last:132321964481453200 resync?:FALSE>
    153150 00:01:56.2391945s -   Peer ptbtime1.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.108:123) never sync'd, resync now!
    153150 00:01:56.2391945s -   Peer ptbtime2.ptb.de,0x1 (ntp.m|0x1|0.0.0.0:123->192.53.103.104:123) never sync'd, resync now!
    153150 00:01:56.2391945s -   Peers reset: p-p:0 a-p:3 a-x:0
    153150 00:01:56.2391945s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
    153150 00:01:56.2391945s - StartListeningThread completed!
    153150 00:01:56.2391945s - PeerPollingThread: waiting 1.500s
    153150 00:01:56.2391945s - StartPeerPollingThread completed!
    153150 00:01:56.2391945s - PeerPollingThread: PeerListUpdated
    153150 00:01:56.2391945s - TimeProvCommand([NtpServer], TPC_NetTopoChange) called.
    153150 00:01:56.2391945s - Logging error: NtpClient has been configured to acquire time from one or more time sources, however none of the sources are currently accessible and no attempt to contact a source will be made for 1 minutes. NTPCLIENT HAS NO SOURCE OF ACCURATE TIME.
    153150 00:01:56.2391945s - PeerPollingThread: waiting 1.500s
    153150 00:01:56.2391945s - W32TmServiceMain: waiting i16.000s (64.000s)
    153150 00:01:56.2391945s - W32TmServiceMain: RequestNetTopoChangeNotification Succeed
    153150 00:01:56.2391945s - NtpProvider: Network Topology Change
    153150 00:01:56.2391945s -   Peer (special) now pending: <Name: poll:3600 diff:2133401055 last:132321964481453200 resync?:FALSE>
    153150 00:01:56.2391945s -   Peer  never sync'd, resync now!
    153150 00:01:56.2391945s -   Peer  never sync'd, resync now!
    153150 00:01:56.2391945s -   Peers reset: p-p:3 a-p:3 a-x:0
    153150 00:01:56.2391945s - NtpProvider: Created 2 sockets (0 listen-only): [::]:123<0x0>, 0.0.0.0:123<0x0>
    153150 00:01:56.2391945s - StartListeningThread completed!
    153150 00:01:56.2391945s - PeerPollingThread: waiting 1.500s
    153150 00:01:56.2391945s - StartPeerPollingThread completed!
    153150 00:01:56.2391945s - TimeProvCommand([NtpServer], TPC_NetTopoChange) called.
    153150 00:01:56.2391945s - PeerPollingThread: PeerListUpdated
    153150 00:01:56.2391945s - Logging error: NtpClient has been configured to acquire time from one or more time sources, however none of the sources are currently accessible and no attempt to contact a source will be made for 1 minutes. NTPCLIENT HAS NO SOURCE OF ACCURATE TIME.

    Friday, April 24, 2020 11:04 AM
  • But it's beeing rejected at some point. According to the logs it ssems that the external time servers are not reachable (but I can get my time stamps via the stripchart command?!, I will investigate what Dave mentioned above and talk to our central IT department).

    Yes, I don't remember the specifics since it was some months ago but if you wire shark / message analyzer it you'll see stripchart coming back on another port.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.


    Friday, April 24, 2020 11:12 AM
  • FML - Its working again! 

    Yep I found out, that external time servers are blocked. Thanks to my lack of knowledge of how NTP works it was hard for me that this could be the source of my problems. I have now have a running and working configuration with an unofficial internalt time server and an official one. Another difference was specifying the 0x1-Flag at the servers. 

    Thanks you all so much for your support - you really saved my week(end)!

    I wish you all a nice weekend!

    Friday, April 24, 2020 12:02 PM
  • Glad to hear it helps, you're welcome. It was certainly a hair puller for me as well back a few months ago.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Friday, April 24, 2020 12:05 PM