[ntp:questions] broadcast ntpd server on Windows
mayer at ntp.isc.org
Sat Jan 27 04:57:57 UTC 2007
mshetty at mail.com wrote:
> Thank you for the response.
> The contents of the configuration file is as follows:
> # Use drift file
> driftfile "C:\NTP\etc\ntp.drift"
> # your local system clock, could be used as a backup
> # (this is only useful if you need to distribute time no matter how
> good or bad it is)
> server 127.127.1.0
> # but it should operate at a high stratum level to let the clients know
> and force them to
> # use any other timesource they may have.
> fudge 127.127.1.0 stratum 12
This means that you have nothing to discipline this clock. Is there a
specific reason why? Note: you cannot run ntpd AND w32time at the same
time, they use the same 123/UDP port and in any case w32time is not an
NTP protocol implementation.
> # End of generated ntp.conf --- Please edit this to suite your needs
Generated? By what? There's nothing in here that's worth generating.
> authenticate yes
> keys /etc/ntp/keys
> broadcast 192.168.38.17 key 1 ttl 6
This is wrong. 192.168.38.17 is *NOT* a broadcast address. You *MUST*
use either a valid broadcast or multicast address with this line. A
valid broadcast address here would be 192.168.38.255. A valid multicast
address would be 22.214.171.124. Also why is ttl set to 6. That is extremely
high and means that it will go 6 hops to deliver an NTP broadcast
packet. You really don't want that. You probably need at most 2 and most
likely 1. Hopefully your routers don't let them out.
> #broadcast 192.168.38.17
> trustedkey 1
Do the broadcast clients have the key?
> The contens of the drift file is:
> Would help if you could give us some suggestions.
> Thanks and Regards,
> M Shetty
More information about the questions