[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
| Notice: | Welcome to the Digital UNIX Conference |
| Moderator: | SMURF::DENHAM |
|
| Created: | Thu Mar 16 1995 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 10068 |
| Total number of notes: | 35879 |
I am trying to set up a NTP server (DUNIX V3.2G) using a local reference
as the time source. I am trying to synchronize time on a client (DUNIX
V4.0B), but I haven't been succesfull so far. I have succesfully being
using the same setup in a homogenous environmet (V3.2). I was also
able to use the NTP server with systems running V2.0 (!) and V3.0B but
not with the V4.0B system.
This is the setup:
One and only NTP server: trubuster.suo.dec.com (16.185.32.29)
/etc/rc.config
--------------
XNTPD_CONF="YES"
export XNTPD_CONF
XNTP_SERV1=""
export XNTP_SERV1
XNTP_SERV2=""
export XNTP_SERV2
XNTP_SERV3=""
export XNTP_SERV3
XNTPD_OPTS="-g"
export XNTPD_OPTS
/etc/ntp.conf
-------------
driftfile /etc/ntp.drift
peer 127.127.1.1
V4.0B client suosf1.suo.dec.com (16.185.32.19):
/etc/rc.config
--------------
XNTPD_CONF="YES"
export XNTPD_CONF
XNTP_SERV1="trubuster.suo.dec.com"
export XNTP_SERV1
XNTP_SERV2=""
export XNTP_SERV2
XNTP_SERV3=""
export XNTP_SERV3
XNTPD_OPTS="-g"
export XNTPD_OPTS
/etc/ntp.conf
-------------
driftfile /etc/ntp.drift
server trubuster.suo.dec.com version 2 # xntpd V2
ntpq -p on the server:
ntpq -p
remote refid st when poll reach delay offset disp
==========================================================================
127.127.1.1 .LCL. 1 never 64 0 0.0 0.00 64000
ntpq -p on the client:
remote refid st t when poll reach delay offset disp
==============================================================================
trubuster.suo.d 0.0.0.0 16 u 8 64 0 0.00 0.000 16000.0
ntptrace on the client:
ntptrace -vd trubuster
DoTransmit(16.185.32.29)
DoTransmit to 16.185.32.29
ReceiveBuf(16.185.32.29, 16.185.32.29)
server 16.185.32.29, port 123
stratum 16, precision -6, leap 11
refid 0.0.0.0 delay 0.00977, dispersion 0.00000 offset 1.395755
rootdelay 0.00000, rootdispersion 0.00000, synch dist 0.00000
reference time: 00000000.00000000 Thu, Feb 7 2036 7:28:16.000
originate timestamp: b7073484.88ebd000 Tue, Apr 22 1997 14:58:44.534
transmit timestamp: b7073483.225b9000 Tue, Apr 22 1997 14:58:43.134
DoTransmit(0.0.0.0)
DoTransmit to 0.0.0.0
ReceiveBuf(0.0.0.0, 16.185.32.19)
receive: wrong server
DoTransmit(0.0.0.0)
DoTransmit to 0.0.0.0
ReceiveBuf(0.0.0.0, 16.185.32.19)
receive: wrong server
DoTransmit(0.0.0.0)
DoTransmit to 0.0.0.0
ReceiveBuf(0.0.0.0, 16.185.32.19)
receive: wrong server
DoTransmit(0.0.0.0)
DoTransmit to 0.0.0.0
ReceiveBuf(0.0.0.0, 16.185.32.19)
receive: wrong server
DoTransmit(0.0.0.0)
DoTransmit to 0.0.0.0
ReceiveBuf(0.0.0.0, 16.185.32.19)
receive: wrong server
0.0.0.0: *Timeout*
So the question is why the client wants to talk to 0.0.0.0 ?
Interesting is the
reference time: 00000000.00000000 Thu, Feb 7 2036 7:28:16.000
in the year 2036. What does this mean ?
Any idea ?
Thnx and cheers
Catsup
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|