[ previous ] [ next ] [ threads ]
 From:  "P B" <pjb141 at hotmail dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  MSNTP Timeout Problem - monowall 1.1b1 - PC CDROM
 Date:  Sun, 04 Apr 2004 01:28:47 +0000

I recently noticed that the clock on my monowall machine was wrong by more 
than a couple of minutes, even though it is set to sync with a machine 
running ntpd on my DMZ.

Disabling time sync and running msntp manually in verbose mode gives the 

$ msntp -a -W
msntp options: a=3 p=0 v=3 e=0.100 E=5.000 P=30.000
    d=15 c=5 x=0 op=1 l=/var/run/msntp.pid f=
Started=3290030492.087422 2004 Apr 03 20:21:32.087
Looking for the socket addresses
msntp: using NTP server *removed* (
Using port 123 for NTP
Internet address: address=c0a81402 anywhere=00000000 everywhere=ffffffff
Initial sockets: here=00000000/0000 there=c0a81402/007b
Times: old=(1081041692,090095) new=(1081041692,090095) adjust=(0,000000)
Outgoing packet on socket 0:
sta=0 ver=3 mod=3 str=15 pol=8 dis=0.000000 ref=0.000000
ori=0.000000 rec=0.000000
tra=3290030492.090149 cur=3290030492.090149
1b0f0800 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 c419e19c 17140000
Flushing outstanding packets
Flushed 0 packets totalling 0 bytes
Receive timed out

This is repeated 5 times and the following error is then generated.

msntp: not enough valid responses received in time

I can ping from m0n0 - and have other machines on the LAN and 
in the DMZ which sync to it fine. I also tried syncing with an external 
(nist.gov) time server but get the same error message.


It's fast, it's easy and it's free. Get MSN Messenger today!