I have both the firewalls on the machines diabled for this test.  ntpd
is running on both machines: 

# ntpdate -d -u 192.168.0.1
31 Jul 13:59:20 ntpdate[1941]: ntpdate 4.0.99k Thu Apr  5 14:21:52 EDT
2001 (1)
transmit(192.168.0.1)
transmit(192.168.0.1)
transmit(192.168.0.1)
transmit(192.168.0.1)
transmit(192.168.0.1)
server 192.168.0.1, port 123
stratum 0, precision 0, leap 00, trust 000
refid [0.0.0.0], delay 0.00000, dispersion 64.00000
transmitted 4, in filter 4
reference time:    00000000.00000000  Thu, Feb  7 2036  0:28:16.000
originate timestamp: 00000000.00000000  Thu, Feb  7 2036  0:28:16.000
transmit timestamp:  bf117e8b.f6385404  Tue, Jul 31 2001 13:59:23.961
filter delay:  0.00000  0.00000  0.00000  0.00000 
         0.00000  0.00000  0.00000  0.00000 
filter offset: 0.000000 0.000000 0.000000 0.000000
         0.000000 0.000000 0.000000 0.000000
delay 0.00000, dispersion 64.00000
offset 0.000000

31 Jul 13:59:24 ntpdate[1941]: no server suitable for synchronization
found

me clueless here,
chuck

On 31 Jul 2001 21:40:45 +0300, Markku Kolkka wrote:
> On Tuesday 31. Julyta 2001 20:54, you wrote:
> > All seems to be working now on the server, but my clients have this
> > output from ntpq -p
> >      remote           refid      st t when poll reach   delay   offset
> > jitter
> > ===========================================================================
> >=== 192.168.0.1     0.0.0.0         16 u    -   64    0    0.000    0.000
> > 4000.00
> > *LOCAL(0)        LOCAL(0)        10 l   51   64  377    0.000    0.000
> > 0.000
> >
> > any ideas?
> 
> They can't communicate with the local server. More firewalling? Try
> "ntpdate -d -u 192.168.0.1" and see if you get any "receive" responses to the 
> "transmit" lines.
> 
> >  i don't understand really how the server can have 123 socket
> > connected to the internet to get time as well as serve time from that
> > same socket to the clients?
> 
> The socket isn't "connected", ntp uses UDP. The socket is 
> receiving packets that can be either responses from servers or requests from 
> clients, and the contents of the packet tells which it is.
> 
> -- 
>       Markku Kolkka
>       [EMAIL PROTECTED]
> 
> 
> 
> _______________________________________________
> Seawolf-list mailing list
> [EMAIL PROTECTED]
> https://listman.redhat.com/mailman/listinfo/seawolf-list




_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to