Jump to content

charlow

Member
  • Posts

    1
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About charlow

charlow's Achievements

0

Reputation

  1. Seems like this topic is going for a while. I found it by looking for problem/solution that I am having. I have read the various articles, each helped a little, but not all the way. A great piece of info can come from the w32time logging facility. This can be turned on by setting a few registry entries then restarting the service. This document talks alot about the service and at the end shows how to turn it on. I am going to try the utility it has a link to in case it might help. My main problem is that I have a hardware clock on on our local network that has a GPS input, but the GPS hardware isn't connected yet, only the internal clock is set. Right now, the PDC seems to get the NTP response, but doesn't like it.. Here's the packet from the log file: 148251 03:17:37.5781250s - /-- NTP Packet: 148251 03:17:37.5781250s - | LeapIndicator: 3 - not synchronized; VersionNumber: 3; Mode: 4 - Server; LiVnMode: 0xDC 148251 03:17:37.5781250s - | Stratum: 1 - primary reference (syncd by radio clock) 148251 03:17:37.5781250s - | Poll Interval: 4 - 16s; Precision: -19 - 1.90735æs per tick 148251 03:17:37.5781250s - | RootDelay: 0x0000.0000s - unspecified; RootDispersion: 0x0246.365Fs - 582.212s 148251 03:17:37.5781250s - | ReferenceClockIdentifier: 0x49524947 - source name: "IRIG" 148251 03:17:37.5781250s - | ReferenceTimestamp: 0x83AA7E8000000000148251 03:17:37.5781250s - - 11644473600000000000ns - 134774 00:00:00.0000000s 148251 03:17:37.5781250s - | OriginateTimestamp: 0xC912345194000000148251 03:17:37.5781250s - - 12808898257578125000ns - 148251 03:17:37.5781250s 148251 03:17:37.5781250s - | ReceiveTimestamp: 0xC91234C472F86A09148251 03:17:37.5781250s - - 12808898372449103000ns - 148251 03:19:32.4491030s 148251 03:17:37.5781250s - | TransmitTimestamp: 0xC91234C4732BB73D148251 03:17:37.5781250s - - 12808898372449885800ns - 148251 03:19:32.4498858s 148251 03:17:37.5781250s - >-- Non-packet info: 148251 03:17:37.5781250s - | DestinationTimestamp: 148251 03:17:37.5781250s - 0xC912345194000000148251 03:17:37.5781250s - - 12808898257578125000ns148251 03:17:37.5781250s - - 148251 03:17:37.5781250s 148251 03:17:37.5781250s - | RoundtripDelay: -782800ns (0s) 148251 03:17:37.5781250s - | LocalClockOffset: 114871369400ns - 1:54.871369400s 148251 03:17:37.5781250s - \-- The next lines are: 148251 03:17:37.5781250s - Packet test 6 failed (not syncd or bad interval since last sync). 148251 03:17:37.5781250s - Packet test 8 failed (bad value for root delay or root dispersion). 148251 03:17:37.5781250s - Ignoring packet that failed tests from 10.13.3.30 (ntp.m|0x8|10.13.2.70:123->10.13.3.30:123). I noticed that the Leap Indicator is 3, which is "not syncronized", which could cause the problem.. Just putting this info out in case it helps others, and if others have seen my problem. Also does anybody know what the NTP response field "LiVnMode: 0xDC" means? Doesn't show up in docs that I 've seen for NTP packet definitions
×
×
  • Create New...