NTP - Problem synchronizing a linux client against windows 2003

[Ruben-Fdez-Marcote de G]

Hi,

I have all my linux clients that try to synchronize against a windows 2003 (NTP server) but all fails. But the other hand all windows clients synchronize well.

The asterisk in left side of the server, indicates that it's synchronizing.
The problem is that doesn't appear the asterisk with the server.

[root@imdc1appsap1d ~]# ntpq -p
remote refid st t when poll reach delay offset jitter
=======================================================
imdc1dcoges1p .LOCL. 1 u 7 64 377 0.238 11464.6 42.725


Thanks

[Steven E. Protter]

Shalom,

Its well known that Windows fails to follow agreed upon standards with ntp. Your windows box may need to be patched.

Microsoft's bad quality control or something more sinister.

SEP

[Peter Godron]

Hi,
as this ithe HPUX forum, I can only recommend you read:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=119885

What is the reply to your ntpdate request ?

Perhaps that will help, otherwise raise this problem on the linux forums.


Please also read:
http://forums1.itrc.hp.com/service/forums/helptips.do?#33 on how to reward any useful answers given to your questions.

[melvyn burnard]

posted in wrong forum, moved to more appropriate forum

[Ruben-Fdez-Marcote de G]

Hi,

The exit of command ntpdate is:

[root@imdc1appsap1d ~]# ntpdate imdc1dcoges1p
16 Mar 11:30:05 ntpdate[16881]: step time server 10.215.137.42 offset 8.020151 sec

It's seems to connect. But with ntpq not sync

in ntpd.conf only have one line
server

[Ruben-Fdez-Marcote de G]

Steven,

How I could know if the windows ntp server need to be patched?
I'm not administrator of this windows machine.

And If this machine need to be patched, I need to justify it.

Thanks

[Ivan Ferreira]

Hi Ruben, please see also this thread.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1069976

[Florian Heigl (new acc)]

I think ntpdate is less picky about the quality of a time source. You could try running ntpdate -d -v servername for more verbose information.

Can anyone verify that 2003 still uses the flawed (s)ntp implementation of 2000? I dimly remember it to be fixed up a bit.

In any case, it is not very sane to rely on a windows server for a primary time source - the windows implementation is based on the assumption there's a unix ntp server available the windows can cling to overcome it's unability to keep time.
so, hooking up unix to windows won't do you much good.

[Ruben-Fdez-Marcote de G]

I have readed many threads about this cuestion.

I have been tried to chage de version server 1, 2 or 3.

I put the out of ntpd -ddd comand

[root@imdc1appsap1d ~]# ntpd -ddd
ntpd 4.2.0a@1.1190-r Thu Apr 20 11:28:36 EDT 2006 (1)
addto_syslog: ntpd 4.2.0a@1.1190-r Thu Apr 20 11:28:36 EDT 2006 (1)
addto_syslog: set_process_priority: Leave priority alone: priority_done is <2>
addto_syslog: precision = 3.000 usec
create_sockets(123)
address_okay: listen Virtual: 1, IF name: lo, Up Flag: 1
address_okay: listen Virtual: 1, IF name: eth0, Up Flag: 1
bind() fd 4, family 2, port 123, addr 0.0.0.0, flags=8
flags for fd 4: 04002
addto_syslog: Listening on interface wildcard, 0.0.0.0#123
bind() fd 5, family 10, port 123, addr ::, flags=0
flags for fd 5: 04002
addto_syslog: Listening on interface wildcard, ::#123
bind() fd 6, family 2, port 123, addr 127.0.0.1, flags=0
flags for fd 6: 04002
addto_syslog: Listening on interface lo, 127.0.0.1#123
bind() fd 7, family 2, port 123, addr 10.215.137.30, flags=8
flags for fd 7: 04002
addto_syslog: Listening on interface eth0, 10.215.137.30#123
create_sockets: ninterfaces=4
interface 0: fd=4, bfd=-1, name=wildcard, flags=0x8, scope=0
sin=0.0.0.0 bcast=0.0.0.0, mask=255.255.255.255
interface 1: fd=5, bfd=-1, name=wildcard, flags=0x0, scope=0
sin=:: mask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
interface 2: fd=6, bfd=-1, name=lo, flags=0x5, scope=0
sin=127.0.0.1 mask=255.0.0.0
interface 3: fd=7, bfd=-1, name=eth0, flags=0x9, scope=0
sin=10.215.137.30 bcast=10.215.137.127, mask=255.255.255.128
init_io: maxactivefd 7
local_clock: time 0 clock 0.000000 offset 0.000000 freq 0.000 state 0
getnetnum given 10.215.137.42, got 10.215.137.42
key_expire: at 0
peer_clear: at 0 assoc ID 28020 refid INIT
newpeer: 10.215.137.30->10.215.137.42 mode 3 vers 1 poll 6 10 flags 0x1 0x1 ttl 0 key 00000000
addto_syslog: configure: keyword "authenticate" unknown, line ignored
authtrust: keyid 0000ffff life 1
report_event: system event 'event_restart' (0x01) status 'sync_alarm, sync_unspec, 1 event, event_unspec' (0xc010)
addto_syslog: select(): nfound=-1, error: Interrupted system call
MCAST *****sendpkt(fd=7 dst=10.215.137.42, src=10.215.137.30, ttl=0, len=48)
transmit: at 1 10.215.137.30->10.215.137.42 mode 3
poll_update: at 1 10.215.137.42 flags 0001 poll 6 burst 0 last 1 next 65
auth_agekeys: at 1 keys 1 expired 0
timer: refresh ts 0
input_handler: if=3 fd=7 length 48 from 0ad7892a 10.215.137.42
receive: at 1 10.215.137.30<-10.215.137.42 restrict 000
receive: at 1 10.215.137.30<-10.215.137.42 mode 4 code 1
peer 10.215.137.42 event 'event_reach' (0x84) status 'unreach, conf, 1 event, event_reach' (0x8014)
poll_update: at 1 10.215.137.42 flags 0001 poll 6 burst 0 last 1 next 64
clock_filter: popcorn 0.740102 0.000015
addto_syslog: select(): nfound=-1, error: Interrupted system call
addto_syslog: select(): nfound=-1, error: Interrupted system call
addto_syslog: select(): nfound=-1, error: Interrupted system call
addto_syslog: select(): nfound=-1, error: Interrupted system call
addto_syslog: select(): nfound=-1, error: Interrupted system call
addto_syslog: select(): nfound=-1, error: Interrupted system call
addto_syslog: select(): nfound=-1, error: Interrupted system call
addto_syslog: select(): nfound=-1, error: Interrupted system call
addto_syslog: ntpd exiting on signal 2