broadcast ntpd server on Windows

  • Follow


Hi,

We have installed ntp-4.2.0a@mbg-fluxcap-v2-o-win32-setup.exe. We are
unable to use it as a broadcast server.

Would help if anyone who has has configured it as a broadcast server
can get back.

Every time we specify a broadcast address like 192.168.39.255 in
ntp.conf, re-starting ntpd service results in an error like not Class D
address.

We need a broadcast ntpd server on Windows. Incase there's any other
freeware available kindly let us know.

Thanks and Regards,
M Shetty

0
Reply mshetty (50) 1/17/2007 2:08:18 PM

mshetty@mail.com wrote:
> Hi,
>
> We have installed ntp-4.2.0a@mbg-fluxcap-v2-o-win32-setup.exe. We are
> unable to use it as a broadcast server.
>
> Would help if anyone who has has configured it as a broadcast server
> can get back.
>
> Every time we specify a broadcast address like 192.168.39.255 in
> ntp.conf, re-starting ntpd service results in an error like not Class D
> address.
>
> We need a broadcast ntpd server on Windows. Incase there's any other
> freeware available kindly let us know.
>
> Thanks and Regards,
> M Shetty

Wouldn't your clients respond correctly if you used the multicast
address that
is assigned to NTP?  The normal address is 224.0.1.1, which I use.

Not positive, but maybe if you just used the keyword 'broadcast',
without an address,
it might default to the standard broadcast address for the current
network.

Roger

0
Reply wa6zvp 1/19/2007 4:36:29 AM


Hi M Shetty,

could you please let us know how your configuration file looks like?

Best Regards,
Heiko


mshetty@mail.com schrieb:
> Hi,
> 
> We have installed ntp-4.2.0a@mbg-fluxcap-v2-o-win32-setup.exe. We are
> unable to use it as a broadcast server.
> 
> Would help if anyone who has has configured it as a broadcast server
> can get back.
> 
> Every time we specify a broadcast address like 192.168.39.255 in
> ntp.conf, re-starting ntpd service results in an error like not Class D
> address.
> 
> We need a broadcast ntpd server on Windows. Incase there's any other
> freeware available kindly let us know.
> 
> Thanks and Regards,
> M Shetty
> 

0
Reply Heiko 1/22/2007 10:23:44 AM

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

# End of generated ntp.conf --- Please edit this to suite your needs

authenticate yes
keys		/etc/ntp/keys
broadcast 192.168.38.17 key 1 ttl 6
#broadcast 192.168.38.17
trustedkey 1

The contens of the drift file is:
0.000

Would help if you could give us some suggestions.

Thanks and Regards,
M Shetty

On Jan 22, 3:23 pm, Heiko Gerstung
<heiko_removeme_.gerst...@meinberg.de> wrote:
> Hi M Shetty,
>
> could you please let us know how your configuration file looks like?
>
> Best Regards,
> Heiko
>
> mshe...@mail.com schrieb:
>
>
>
> > Hi,
>
> > We have installed ntp-4.2...@mbg-fluxcap-v2-o-win32-setup.exe. We are
> > unable to use it as a broadcast server.
>
> > Would help if anyone who has has configured it as a broadcast server
> > can get back.
>
> > Every time we specify a broadcast address like 192.168.39.255 in
> > ntp.conf, re-starting ntpd service results in an error like not Class D
> > address.
>
> > We need a broadcast ntpd server on Windows. Incase there's any other
> > freeware available kindly let us know.
>
> > Thanks and Regards,
> > M Shetty- Hide quoted text -- Show quoted text -

0
Reply mshetty 1/24/2007 12:11:11 PM

mshetty@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 239.1.1.2. 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?

Danny

> The contens of the drift file is:
> 0.000
> 
> Would help if you could give us some suggestions.
> 
> Thanks and Regards,
> M Shetty
> 
_______________________________________________
questions mailing list
questions@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions
0
Reply mayer 1/27/2007 4:57:57 AM

Danny Mayer wrote:
>> 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 239.1.1.2. 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.
> 

I forgot to ask, did you look in the application event log and see the
messages for NTP?

Danny
_______________________________________________
questions mailing list
questions@lists.ntp.isc.org
https://lists.ntp.isc.org/mailman/listinfo/questions
0
Reply mayer 1/27/2007 5:00:48 AM

5 Replies
176 Views

(page loaded in 0.134 seconds)

Similiar Articles:













7/10/2012 11:16:51 PM


Reply: