[suse-security] getting mad connecting to (x)ntpd
Dear colleagues, i wonder if suse took some sophisticated measures to prevent the xntpd from being contacted by clients :-| I configured the server connecting to two "outside" servers as time sources. These connections work fine (shown with "ntpq -p"). The local source was left untouched. Now, if i try to "netdate" to this timeserver from a (linux) client, i immediately get the message "connection refused". Here's the ntpd.conf, maybe i've missed sth? Thanx a lot for your patience Uli server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized server 192.53.103.104 prefer server 212.19.48.35 driftfile /etc/ntp.drift # path for drift file logfile /var/log/ntp # alternate log file logconfig =all
Am Dienstag, 11. Dezember 2001 22:40 schrieb UKlaus-Mailinglistenaccount:
Dear colleagues, i wonder if suse took some sophisticated measures to prevent the xntpd from being contacted by clients :-| I configured the server connecting to two "outside" servers as time sources. These connections work fine (shown with "ntpq -p"). The local source was left untouched. Now, if i try to "netdate" to this timeserver from a (linux) client, i immediately get the message "connection refused". Here's the ntpd.conf, maybe i've missed sth?
Thanx a lot for your patience Uli
server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized
server 192.53.103.104 prefer server 212.19.48.35
driftfile /etc/ntp.drift # path for drift file
logfile /var/log/ntp # alternate log file logconfig =all Hello, Netdate uses a udp-connection (port 37, time, see /etc/services) by default. Your server has to listen to udp-port 37, it has to be configured/enabled in /etc/(x)inetd.conf. BTW, as far as I know, netdate doesn't use the network time protokoll, it just ask the server what time it has and sets it on the local box.
HTH -- ------------------ Guido Tschakert Sys-Ad, SRC ------------------
Hallo, please use the command ntpdate for connecting ntp-server(s) and have a look at: http://www.eecis.udel.edu/~ntp/ntp_spool/html/build.htm sincerly Michael Huppert ---------------------------------- ORBIS communications GmbH Goethestraße 3-5 66121 Saarbruecken E-Mail: m.huppert@orbiscom.de Fon: 0681 / 9 67 27 60 Fax: 0681 / 9 67 27 69 Date: 12-Dec-01 Time: 11:27:10 ---------------------------------- On 11-Dec-01 UKlaus-Mailinglistenaccount wrote:
Dear colleagues, i wonder if suse took some sophisticated measures to prevent the xntpd from being contacted by clients :-| I configured the server connecting to two "outside" servers as time sources. These connections work fine (shown with "ntpq -p"). The local source was left untouched. Now, if i try to "netdate" to this timeserver from a (linux) client, i immediately get the message "connection refused". Here's the ntpd.conf, maybe i've missed sth?
Thanx a lot for your patience Uli
server 127.127.1.0 # local clock (LCL) fudge 127.127.1.0 stratum 10 # LCL is unsynchronized
server 192.53.103.104 prefer server 212.19.48.35
driftfile /etc/ntp.drift # path for drift file
logfile /var/log/ntp # alternate log file logconfig =all
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
participants (3)
-
Guido Tschakert -
Michael Huppert -
UKlaus-Mailinglistenaccount