search for: broadcastclient

This ntp.conf file works fine under RedHat 9: authenticate no #enable auth driftfile /etc/ntp/drift keys /etc/ntp/ntp.keys server 127.127.1.0 fudge 127.127.1.0 stratum 10 trustedkey 1 enable bclient broadcastclient However, it doesn't work on CentOS 4.1. ntpd complains with this error message: Unable to listen for broadcasts, no broadcast interfaces available Has anyone gotten ntp broadcastclient to work under CentOS? This is very similar to the problem explained by this email thread: http://...

...s fine with RedHat Enterprise 3.0 and below. However, it doesn't work with CentOS 4.1. #authenticate no #enable auth driftfile /etc/ntp/drift keys /etc/ntp/ntp.keys server 127.127.1.0 <http://127.127.1.0> fudge 127.127.1.0 <http://127.127.1.0> stratum 10 trustedkey 1 enable bclient broadcastclient This is the error reported in /var/log/messages: Sep 29 20:24:36 wsp-mich-74-1 ntpdate[9758]: step time server 10.0.107.1<http://10.0.107.1>offset 0.033880 sec Sep 29 20:24:36 wsp-mich-74-1 ntpd: succeeded Sep 29 20:24:36 wsp-mich-74-1 ntpd[9766]: ntpd 4.2.0a at 1.1190-r Mon Feb 21 17:54:52...

I'm running latest CentOS 4.3 (2.6.9-34.0.2.ELsmp) and found that the included 'ntpd' 4.2.0a at 1.1190-r will not accept NTP broadcast packets. There is a documented bug in ntpd 4.2.0 to this effect, resolved way back in 2004: https://ntp.isc.org/bugs/show_bug.cgi?id=267 Any chance someone can include a more recent version of 'ntpd' in the next CentOS RPM update

...to provide time to your local subnet, change the next line. # (Again, the address is an example only.) #broadcast 192.168.123.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! #disable auth #broadcastclient driftfile /var/lib/ntp/ntp.drift # Enable this if you want statistics to be logged. #statsdir /var/log/ntpstats/ statistics loopstats peerstats clockstats filegen loopstats file loopstats type day enable filegen peerstats file peerstats type day enable filegen clockstats file clockstats type day...

...18-164.9.1 and 2.6.18-164.6.1 kernels on this branch. Symptom: On 32-bit domU only (we have never seen 64-bit domU be affected), we observe that the clock gets set forward by a random amount of time, between 40-80 minutes. We originally thought this was due to rogue ntp broadcasts because the ntp broadcastclient was disabled, but we have now disabled ntpd on all domU and the problem persists. During the 40-80 minutes it is possible to log into the domU via the Xen console, it appears to be otherwise functional although the clock is stuck at the forward time. The daemons (which are Axis-based web services)...

...ant to provide time to your local subnet, change the next line. # (Again, the address is an example only.) broadcast 192.168.1*6.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! disable auth broadcastclient Went to ntp.org to see if I could troubleshoot. Did as they suggested and got same result. Their troubleshooting page indicated that most issues are connected to DNS issues between machines. Did some 'nslookup' from each DC to the member and vise versa. DNS returns correct results. Look...

...to provide time to your local subnet, change the next line. # (Again, the address is an example only.) #broadcast 192.168.123.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! #disable auth #broadcastclient interface listen lo interface listen enp2s0 #interface ignore wildcard interface ignore ipv6 ###### Needed for Samba 4 ###### # in the restrict -4 or -6 added mssntp at the end # Location of the samba ntp_signed directory ntpsigndsocket /var/lib/samba/ntp_signd ####### NTP end Greetz, Louis

...nt to provide time to your local subnet, change the next line. # (Again, the address is an example only.) br oadcast 192.168.1*6.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! disable auth broadcastclient Went to ntp.org to see if I could troubleshoot. Did as they suggested and got same result. Their troubleshooting page indicated that most issues are connected to DNS issues between machines. Did some 'nslookup' from each DC to the member and vise versa. DNS returns correct results. Looked t...

...o provide time to your local subnet, change the next line. # (Again, the address is an example only.) #broadcast 192.168.123.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines.  Please do this only if you trust everybody on the network! #disable auth #broadcastclient

...et, change the next line. > # (Again, the address is an example only.) > #broadcast 192.168.123.255 > > # If you want to listen to time broadcasts on your local subnet, de-comment the > # next lines. Please do this only if you trust everybody on the network! > #disable auth > #broadcastclient > > interface listen lo > interface listen enp2s0 > #interface ignore wildcard > interface ignore ipv6 > > ###### Needed for Samba 4 ###### > # in the restrict -4 or -6 added mssntp at the end > # Location of the samba ntp_signed directory > ntpsigndsocket /var/lib/s...

...t to provide time to your local subnet, change the next line. # (Again, the address is an example o nly.) br oadcast 192.168.1*6.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! disable auth broadcastclient Went to ntp.org to see if I could troubleshoot. Did as they suggested and got same result. Their troubleshooting page indicated that most issues are connected to DNS issues between machines. Did some 'nslookup' from each DC to the member and vise versa. DNS returns correct results. Looked t...

...change the next >line. ># (Again, the address is an example only.) >broadcast 192.168.1*6.255 > ># If you want to listen to time broadcasts on your local subnet, >de-comment the ># next lines. Please do this only if you trust everybody on >the network! >disable auth >broadcastclient > >Went to ntp.org to see if I could troubleshoot. Did as they suggested >and got same result. Their troubleshooting page indicated that most >issues are connected to DNS issues between machines. Did some >'nslookup' >from each DC to the member and vise versa. DNS return...

...ide time to your local subnet, change the next line. # (Again, the address is an example o > nly.) br oadcast 192.168.1*6.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! disable auth broadcastclient Went to ntp.org to see if I could troubleshoot. Did as they suggested and got same result. Their troubleshooting page indicated that most issues are connected to DNS issues between machines. Did some 'nslookup' from each DC to the member and vise versa. DNS returns correct results. Looked t...

On Tue, 12 Sep 2017 14:41:42 -0300 Flávio Silveira via samba <samba at lists.samba.org> wrote: > > Ok, I understand now, one question though: if realm is > AD.TECNOPON.COM.BR, does domain need to be AD? No, you can use anything you like, provided it is one word, 15 characters or less, without punctuation. > If I understand > correctly, realm is "full domain with

...(Again, the address is an example only.) #broadcast > 192.168.123.255 > > > > # If you want to listen to time broadcasts on your local subnet, > > de-comment the # next lines. Please do this only if you > trust everybody on the network! > > #disable auth > > #broadcastclient > > > > interface listen lo > > interface listen enp2s0 > > #interface ignore wildcard > > interface ignore ipv6 > > > > ###### Needed for Samba 4 ###### > > # in the restrict -4 or -6 added mssntp at the end # > Location of the > > samba...

...de time to your local subnet, change the next line. # (Again, the address is an example only.) br > oadcast > 192.168.1*6.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! disable auth broadcastclient Went to ntp.org to see if I could troubleshoot. Did as they suggested and got same result. Their troubleshooting page indicated that most issues are connected to DNS issues between machines. Did some 'nslookup' from each DC to the member and vise versa. DNS returns correct results. Looked t...

...time to your local subnet, change the next line. # (Again, the address is an example only.) broadcast 10.48.0.0 #mask 255.255.0.0 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! #disable auth #broadcastclient --------------------------------------------------- Are you have any idea why isn't works? Thanks, Robert

...e time to your local subnet, change the next line. # (Again, the address is an example o > nly.) br > oadcast 192.168.1*6.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! disable auth broadcastclient Went to ntp.org to see if I could troubleshoot. Did as they suggested and got same result. Their troubleshooting page indicated that most issues are connected to DNS issues between machines. Did some 'nslookup' from each DC to the member and vise versa. DNS returns correct results. Looked t...

...rom the pool.ntp.org project. # Please consider joining the pool (http://www.pool.ntp.org/join.html). server 0.europe.pool.ntp.org iburst server 1.europe.pool.ntp.org iburst server 2.europe.pool.ntp.org iburst server 3.europe.pool.ntp.org iburst #broadcast 192.168.1.255 autokey # broadcast server #broadcastclient # broadcast client #broadcast 224.0.1.1 autokey # multicast server #multicastclient 224.0.1.1 # multicast client #manycastserver 239.255.254.254 # manycast server #manycastclient 239.255.254.254 autokey # manycast client # Enable public key cryptography. #crypto includefile /etc/ntp/crypto/p...

..., change the next line. # (Again, the address is > an > example > > o > >> nly.) br oadcast 192.168.1*6.255 # If you want to listen to time broadcasts on your local subnet, de-comment the # next lines. Please do this only if you trust everybody on the network! disable auth broadcastclient Went to ntp.org to see if I could troubleshoot. Did as they suggested and got same result. Their troubleshooting page indicated that most issues are connected to DNS issues between machines. Did some 'nslookup' from each DC to the member and vise versa. DNS returns correct results. Looked t...