[Samba] ntpq -p ***Request timed out

[Bob of Donelson Trophy]

Made the suggested adjustments (4 locations in the member server
ntp.conf file) and restarted ntp. 

Still (member server) timing out. 

Not sure what you mean about removing "server 0.debian.pool.ntp.org
iburst" lines. Those on the DC's. Aren't they necessary? 

Running 'ntpq -p' on DC's results in correct response. 

---

-------------------------

Bob Wooden of Donelson Trophy

615.885.2846 (main)
www.donelsontrophy.com [3]

"Everyone deserves an award!!"

On 2015-02-13 10:06, L.P.H. van Belle wrote: 

> bob.
> 
> server dc02.dts***m.lan. iburst prefer
> server dc01.dts***m.lan. iburst prefer 
> 
> remove the . after lan 
> and try like this 
> 
> server dc02.dts***m.lan
> server dc01.dts***m.lan
> 
> and optional, i advice, remove all lines : 
> server 0.debian.pool.ntp.org iburst
> 
> Louis
> '
> 
>> -----Oorspronkelijk bericht----- Van: bob at donelsontrophy.net [mailto:samba-bounces at lists.samba.org] Namens Bob of Donelson Trophy Verzonden: vrijdag 13 februari 2015 16:56 Aan: SAMBA MailList Onderwerp: [Samba] ntpq -p ***Request timed out I have two DC's running Version 4.1.16-SerNet-Debian-9.wheezy and a member server running Version 4.1.11-Debian. When I 'ntpq -p' from the member server I get: localhost: timed out, nothing received ***Request timed out Member server ntp.conf file: cat /etc/ntp.conf # Local clock (this is not the localhost address!) server 127.127.1.0 fudge 127.127.1.0 stratum 10 # The source, where we are receiving the time from (PDC) server dc02.dts***m.lan. iburst prefer server dc01.dts***m.lan. iburst prefer driftfile /var/lib/ntp/ntp.drift logfile /var/log/ntp # Access control # Default restriction restrict default ignore # Allow everything from localhost restrict 127.0.0.1 # Allow that our time source can only provide time and do nothing else restr
 ict
dc02.dts***m.lan. mask 255.255.255.255 nomodify notrap nopeer noquery restrict dc01.dts***m.lan. mask 255.255.255.255 nomodify notrap nopeer noquery The ntp.conf from one of the DC's: cat /etc/ntp.conf # /etc/ntp.conf, configuration for ntpd; see ntp.conf(5) for help 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 enable # You do need to talk to an NTP server or two (or three). #server ntp.your-provider.example # pool.ntp.org maps to about 1000 low-stratum NTP servers. Your server will # pick a different set every time it starts up. Please consider joining the # pool: <http://www.pool.ntp.org/join.html [1]> server 0.debian.pool.ntp.org iburst server 1.debian.pool.ntp.org iburst server 2.debian.pool.ntp.org iburst server
3.debian.pool.ntp.org iburst # Access control configuration; see /usr/share/doc/ntp-doc/html/accopt.html for # details. The web page <http://support.ntp.org/bin/view/Support/AccessRestrictions [2]> # might also be helpful. # # Note that "restrict" applies to both servers and clients, so a configuration # that might be intended to block requests from certain clients could also end # up blocking replies from your own upstream servers. # By default, exchange time with everybody, but don't allow configuration. restrict -4 default kod notrap nomodify nopeer noquery restrict -6 default kod notrap nomodify nopeer noquery # Local users may interrogate the ntp server more closely. restrict 127.0.0.1 restrict ::1 # Clients from this (example!) subnet have unlimited access, but only if # cryptographically authenticated. restrict 192.168.1*6.0 mask 255.255.255.0 notrust # If you want 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 to confirm I do NOT have a firewall running on any device. Not at this time. Member server time keeps drifting and I need to correct this. Any ideas? -- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [3] [1 [3]] "Everyone deserves an award!!" Links: ------ [1] http://www.donelsontrophy.com [3] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba [4]
 

Links:
------
[1] http://www.pool.ntp.org/join.html
[2] http://support.ntp.org/bin/view/Support/AccessRestrictions
[3] http://www.donelsontrophy.com
[4] https://lists.samba.org/mailman/options/samba