[ntp:questions] Linux as clients not synching with Win/Tardis Time server
suj
sujnanshetty at gmail.com
Wed Dec 5 17:05:53 UTC 2007
3 Windows NTP server = Win 2003 Std Ed, Win 2000, Win 2003 Std Ed SP2
64 bit Linux= Suse SLES 2.6.16.21-0.8
NTP version =4.2.0a at 1.1196-r
The 3 windows NTP time servers are pointing to the external public
time server pool.
I looked up your archives and I see references to modifying W32time /
Windows registry and ofcourse advice to make Linux the time servers.
Our setup has 3 windows servers with Tardis2000 running as the time
server to our windows clients. We are deploying linux servers and want
to maintain status quo on the time servers till we reach a critical
mass where eventually we will have linux as NTP servers. So for the
time being we have to sync up Linux clients with Win Time Servers.
I have setup the ntp.conf as per the standard
my ntp.conf:
------------------
server 127.127.1.0
fudge 127.127.1.0 stratum 10
server <Win NTp Server-1 IP> burst iburst
server <Win NTp Server-2 IP> burst iburst
server <Win NTp Server-3 IP> burst iburst
peer <linux-server2-ip>
peer <linux-server2-ip>
driftfile /var/lib/ntp/drift/ntp.drift
logfile /var/log/ntp
------------------
austinpower:/home/austin # ntpdc -c peers
remote local st poll reach delay
offset disp
===================================================
*LOCAL(0) 127.0.0.1 10 64 377 0.00000 0.000000
0.03033
=10.248.0.22 10.248.3.231 14 1024 377 0.00017 -69.55465
0.06303
=gargoyle1.abc 10.248.3.231 14 1024 377 0.00015 -70.18628
0.06310
=gargoyle2.abc 10.248.3.231 14 1024 377 0.00017 -69.14703 0.06311
The 3 Win time servers have a stratum of 14 and the Linux time is
synched to its LCL clock. Also the ntpd does not like the time servers
as seen from the "x" against their entries
austinpower:/home/austin # ntpq -p
remote refid st t when poll reach
delay offset jitter
==============================================================
*LOCAL(0) LOCAL(0) 10 l 23 64 377 0.000
0.000 0.001
xgargoyle1.abc 216.bb.68.yyy 14 u 232 1024 377 0.153 -70186.
1.645
xgargoyle2.abc 216.bb.68.xxx 14 u 348 1024 377 0.179 -69147.
5.233
x10.222.0.55 71.bb.xx.xx 14 u 726 1024 377 0.170 -69554.
2.765
giving the time server IP in the ntpq command;
# ntpq -p 10.248.0.xxx
10.248.0.xxx: timed out, nothing received
***Request timed out
I have Linux bonding/network teaming, should that make a difference to
the ntp syncing?
I don't think so, but just explaining the setup.
austinpower:/home/austin # route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use Iface
10.248.3.0 0.0.0.0 255.255.255.0 U 0
0 0 bond0
127.0.0.0 0.0.0.0 255.0.0.0 U 0
0 0 lo
0.0.0.0 10.222.3.254 0.0.0.0 UG 0
0 0 bond0
ntpdate command exits as if the time servers were not available. But I
can ping those Win servers from my linux servers, basically not a
network connectivity issue. I can also do a "nslookup <WinNTPserverIP>
" from the linux m/c's and it resolves the names correctly.
ntpdate cmd comes back with ;
# ntpdate -u
5 Dec 10:39:05 ntpdate[10238]: no servers can be used, exiting
# ntpdate -u gargoyle1.abcd.com
5 Dec 10:39:27 ntpdate[10239]: no server suitable for synchronization
found
#cat /var/lib/ntp/drift/ntp.drift
-143.940 result on one linux server
460.786 result on the other linux server
# netstat -anu
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address
State
udp 0 0 255.255.255.255:427
0.0.0.0:*
udp 0 0 10.abc.yy.32:123 0.0.0.0:* <<<
Secondary bond IP
udp 0 0 10.abc.yy.31:123 0.0.0.0:* <<< Secondary
bond IP
udp 0 0 10.abc.yy.30:123 0.0.0.0:* <<< Secondary
bond IP
udp 0 0 10.abc.yy.130:123 0.0.0.0:* <<< Primary
bond IP
udp 0 0 127.0.0.1:123
0.0.0.0:*
udp 0 0 0.0.0.0:123
0.0.0.0:*
udp 0 0 :::
123 :::*
How can I make these linux servers to sync up with the tardis time
servers on the windoze boxes?
Thanking in advance.
Suj
More information about the questions
mailing list