Problems with ntpdate

Problems with ntpdate

Post by Paul Fischer of BTG Inc. Office Automati » Thu, 18 Apr 1996 04:00:00



Hello All,

It seems that ntpdate is acting weird for me.  When I run it against
UUNET's NTP server (A Cisco Router that supports UDP/NTP) I get the
following message:

1039 # ntpdate  Fddi0/0.GW2.DCA1.Alter.Net
ntpdate: no server suitable for synchronization found

Which makes me think I can't communicate with the server at the other
end, or it doesn work.  However, ntptrace works fine, and ntpdate -d
shows lots of output while talking to the server.  Has anyone seen
this before?  Does anyone know if ntpdate -d and ntptrace use
different packet types than ntpdate?  If so, it could be a firewall
problem.  Any way config information and output of ntptrace and
ntpdate -d are below.

Pentium P133 w/32 MB
Adaptec PCI SCSI HA
One hard disk
Intel EtherExpress 16 ISA
CDROM drive
Sound Blaster 16 pro

1043 # ntptrace  Fddi0/0.GW2.DCA1.Alter.Net
Fddi0/0.GW2.DCA1.Alter.Net: stratum 3, offset -34.6116679, synch
distance 0.1431 43
Vienna1.VA.Alter.Net: stratum 2, offset -34.6206219, synch distance
0.072601
rackety.udel.edu: stratum 1, offset -34.6252995, synch distance
0.011078, refid 'PPS'

1044 # ntpdate -d Fddi0/0.GW2.DCA1.Alter.Net
ntpdate: ntpdate version=3.2; Tue Sep  7 16:54:10 CDT 1993 (1)
transmit(137.39.33.132)
receive(137.39.33.132)
transmit(137.39.33.132)
receive(137.39.33.132)
transmit(137.39.33.132)
receive(137.39.33.132)
transmit(137.39.33.132)
receive(137.39.33.132)
transmit(137.39.33.132)
server 137.39.33.132, port 123
stratum 3, precision -19, leap 00, trust 000
refid [137.39.2.31], delay 0.0355, dispersion 0.0018
transmitted 4, in filter 4
reference time:      b51fdae1.bb4d9c50  Wed, Apr 17 1996 17:02:25.731
originate timestamp: b51fe1ad.b941b7e5  Wed, Apr 17 1996 17:31:25.723
transmit timestamp:  b51fe1d0.570a4000  Wed, Apr 17 1996 17:32:00.340
filter delay:  0.0355   0.0355   0.0355   0.0455
               0.0000   0.0000   0.0000   0.0000
filter offset: -34.6253 -34.6225 -34.6243 -34.6263
               0.00000  0.00000  0.00000  0.00000
delay 0.0355, dispersion 0.0018
offset -34.6253831

ntpdate: step time server 137.39.33.132 offset -34.6307788

--

Paul Fischer     Internet Administrator          BTG, Inc.
(703) 761-6644   (703) 556-9290 (fax)            1945 Old Gallows Rd
"I have a notebook, therefore I will succeed!"   Vienna, VA 22182

 
 
 

1. ntpdate questions/problems

    On a 5.0.5 system I'm trying to run ntpdate.  From the man pages it
appears that I do not need to be running xntpd (which I'm not), in fact it
suggests running ntpdate before xntpd starts on boot.  Problem is, I don't
get a response from the ntp servers (192.43.244.18,
216.200.93.8,132.163.4.102) .  I can ping them (IP or name), traceroute
them, etc.  Yet when I run ntpdate I get "ntpdate: no server suitable for
synchronization found".  In debug mode I see I'm not getting any receive
from the servers.
    Does anyone have any ideas? TIA
Dennis

  dennis.vcf
< 1K Download

2. Why no 500GB SATA option for StorEdge 3511 ?

3. ntpdate problem

4. Help Linux with Windows 95

5. ntpd and ntpdate problem

6. Help in understanding Sun Ultra Sparc 1

7. ntpdate problems

8. kernel panics with Quantum SCSI disk

9. ntpdate problem

10. ntpdate

11. xntpd vs. ntpdate?

12. xntpd/ntpdate -m -w and ntp v4.099

13. ntpdate reports NTP socket in use...but it *shouldn't* be!