I am getting problems trying to sync time using SNTPCLN4.NLM. I have loaded
it on my server and it is coming up with console messages similar to this
one when it loads and when it sync's (or tries to anyway)
CBR-1:load sntpcln4
Loading module SNTPCLN4.NLM
sntpcln4.nlm
Version 1.05 July 20, 1998
bind socket: Can't assign requested address
bind socket: Can't assign requested address
1. The addresses it can't seem to find are CISCO Routers which are
getting their time from an atomic clock.
2. I can ping the Routers at the addresses specified in the CFG file
(see below) from the file server. They are replying 100% of the time when I
load ping.
Any ideas? The log file and cfg file are below.
Thanks
Michael Carroll
Contents of SYS:SNTPCLN4.LOG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
time zone names: EST ESUT
timezone : -36000
daylight : 1
daylightOffset : 3600
daylightON/OFF : 1
Request started client for server at: 1998/12/07 05:33:11 3121997591.673265
48 bytes sent to NTP server 203.2.240.1 Request started client for server
at: 1998/12/07 05:33:21 3121997601.669705
48 bytes sent to NTP server 203.2.240.1 Request started client for server
at: 1998/12/07 05:33:31 3121997611.666145
48 bytes sent to NTP server 203.2.240.1 Request started client for server
at: 1998/12/07 05:33:41 3121997621.662584
48 bytes sent to NTP server 203.2.240.1 Request started client for server
at: 1998/12/07 05:33:51 3121997631.659024
48 bytes sent to NTP server 203.2.240.1 server 203.2.240.1 did not respond
Request started client for server at: 1998/12/07 05:34:01 3121997641.655464
48 bytes sent to NTP server 203.2.240.1 Request started client for server
at: 1998/12/07 05:34:11 3121997651.651904
48 bytes sent to NTP server 203.2.240.1 Request started client for server
at: 1998/12/07 05:34:21 3121997661.648344
48 bytes sent to NTP server 203.2.240.1 Request started client for server
at: 1998/12/07 05:34:31 3121997671.644783
48 bytes sent to NTP server 203.2.240.1 Request started client for server
at: 1998/12/07 05:34:41 3121997681.641223
48 bytes sent to NTP server 203.2.240.1 server 203.2.240.1 did not respond
Server 203.2.240.1 Delay 0.0000 Offset 0.0000
Request started client for server at: 1998/12/07 05:34:51 3121997691.637663
48 bytes sent to NTP server 203.2.243.1 Request started client for server
at: 1998/12/07 05:35:01 3121997701.634102
48 bytes sent to NTP server 203.2.243.1 Request started client for server
at: 1998/12/07 05:35:11 3121997711.630542
48 bytes sent to NTP server 203.2.243.1 Request started client for server
at: 1998/12/07 05:35:21 3121997721.626982
48 bytes sent to NTP server 203.2.243.1 Request started client for server
at: 1998/12/07 05:35:31 3121997731.623422
48 bytes sent to NTP server 203.2.243.1 server 203.2.243.1 did not
respond Request started client for server at: 1998/12/07 05:35:41
3121997741.619862
48 bytes sent to NTP server 203.2.243.1 Request started client for server
at: 1998/12/07 05:35:51 3121997751.616301
48 bytes sent to NTP server 203.2.243.1 Request started client for server
at: 1998/12/07 05:36:01 3121997761.612741
48 bytes sent to NTP server 203.2.243.1 Request started client for server
at: 1998/12/07 05:36:11 3121997771.609181
48 bytes sent to NTP server 203.2.243.1 Request started client for server
at: 1998/12/07 05:36:21 3121997781.605620
48 bytes sent to NTP server 203.2.243.1 server 203.2.243.1 did not
respond Server 203.2.243.1 Delay 0.0000 Offset 0.0000
No timeserver could be reached Networkfailure ????
Contents of SYS:ETC\SNTPCLNT.CFG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
; Lines who start with ; or # are comments
;
[GLOBAL]
; When set to 1, the statistic screen is displayed.
StatisticScreen=1
;
;Logscreen
;
LogScreen=0
;
; Level for loginformations on the logscreen and the logfile
;
LogLevel=9
;
; Name of the logfile, when no logfile is needed, then just leave this
; setting empty
;
LogFile=SYS:sntpclnt.log
; This option has only an effect on NW4.x servers (When using the
sntpcln4.nlm)
; When the time correction is smaller than this number, then the time is
corrected via
; the length of the system ticks.
; This is the preffered method on 4.x servers, since the clock will always
run forward,
; and such corrections work fine with NDS and the tymesync nlm
;
MaxTickCorrection = 300
;
;Resync clock once a day at...
ResyncAT = 23:50:00
;
; Only apply corrections, if the timedifference between local time and NTP
time is greater
; than this number of seconds.
; It is not recomended to set this value under 0.5 seconds for 3.x servers
and not below
; 0.2 seconds for 4.x servers
;
MinimumCorrection=0.5
;
; The number of times we try to get the current time from a specific NTP
server.
;
ServerRetryCount=5
;
; The number of seconds we wait for an answer
;
ServerTimeout=10
;
; With this you can set the source-address to any of your IP addresses
; It's used when you have MPR 3.x version together with NW4.11 & ISWP3/4
;
SourceIP=203.2.241.200
;
;
; Here you can specify a list of NTP servers
; When you have a working DNS/NIS resolver or specified the hostnames in the
host file,
; then you can use the hostnames instead of the IP numbers
[NTPSERVERS]
203.2.240.1
203.2.243.1