I'm havinf NTP configuration problems

david.bradley · ‎06-11-2003

Hi,

I'm not sure if anyone can help me with this issue. I'm trying to configure NTP on my router to sync it's clock with a public time server. It's not working, but it's talking to the server..

Here is the debug, the host 192.168.10.1 is the reply from my firewall.

----

12w3d: NTP: xmit packet to 131.188.3.220:

12w3d: leap 3, mode 3, version 3, stratum 0, ppoll 64

12w3d: rtdel 0000 (0.000), rtdsp 0002 (0.031), refid 7F7F0701 (127.127.7.1)

12w3d: ref C0884A47.A1BD7EAA (01:56:23.631 UTC Sun May 12 2002)

12w3d: org 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)

12w3d: rec 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)

12w3d: xmt C08EFC7B.99FFB81C (03:50:19.601 UTC Fri May 17 2002)

12w3d: NTP: rcv packet from 192.168.10.1 to 192.168.10.252 on Vlan10:

12w3d: leap 0, mode 4, version 3, stratum 4, ppoll 64

12w3d: rtdel 0000 (0.000), rtdsp 02B3 (10.544), refid 7F7F0100 (127.127.1.0)

12w3d: ref C2917CAB.5200E000 (10:02:19.320 UTC Wed Jun 11 2003)

12w3d: org C08EFC7B.99FFB81C (03:50:19.601 UTC Fri May 17 2002)

12w3d: rec C2917CD9.70F14000 (10:03:05.441 UTC Wed Jun 11 2003)

12w3d: xmt C2917CD9.70F5A000 (10:03:05.441 UTC Wed Jun 11 2003)

12w3d: inp C08EFC7B.9A31D42B (03:50:19.602 UTC Fri May 17 2002)

12w3d: NTP: xmit packet to 131.188.3.220:

12w3d: leap 3, mode 3, version 3, stratum 0, ppoll 64

12w3d: rtdel 0000 (0.000), rtdsp 0002 (0.031), refid 7F7F0701 (127.127.7.1)

12w3d: ref C0884A47.A1BD7EAA (01:56:23.631 UTC Sun May 12 2002)

12w3d: org 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)

12w3d: rec 00000000.00000000 (00:00:00.000 UTC Mon Jan 1 1900)

12w3d: xmt C08EFC7C.99FF8C90 (03:50:20.601 UTC Fri May 17 2002)

12w3d: NTP: rcv packet from 192.168.10.1 to 192.168.10.252 on Vlan10:

12w3d: leap 0, mode 4, version 3, stratum 4, ppoll 64

12w3d: rtdel 0000 (0.000), rtdsp 02B4 (10.559), refid 7F7F0100 (127.127.1.0)

........

etc, etc...

mark-obrien · ‎06-11-2003

David,

I've had routers that didn't change to reflect the data they receive trom an NTP source, and the problem was traced to the fact that the routers' configurations had the command "ntp master". See if your config has this command, and if so get rid of it.

Mark

david.bradley · ‎06-11-2003

Hi, thanks for you suggestion.

The only entry I have is :ntp server 131.188.3.220

Dave

mark-obrien · ‎06-11-2003

Dave,

I just noticed the bit about the address of your firewall in the NTP RCV packets in your debug trace. Your router is expecting to receive NTP packets from 131.188.3.220. Is your firewall is translating this address to its own IP address on VLAN 10?

Mark