Networking Forums

Networking Forums > Computer Networking > Windows Networking > Windows 2003 NTP server

Reply
Thread Tools Display Modes

Windows 2003 NTP server

 
 
George
Guest
Posts: n/a

 
      01-06-2007, 09:06 PM
Hi

I am trying to synchronize a Linux Redhat AS (NTP Client, IP 172.16.0.200 )
with a Windows 2003 Server (NTP Server, IP 172.16.0.201). My client is not
synchronizing at all when I add only windows 2003 as server. If i add an
other Linux machine (IP 16.74.33.203) as NTP Server then my Linux client get
synchronize with it.

Linux client and Windows server are connected directly using cross over
cables.

My ntp.conf file in Linux client.

server 172.16.0.201 // Windows Server 2003
server 16.74.33.203 // Linux Server

driftfile /var/lib/ntp/drift
restrict 172.16.0.201
restrict 16.74.33.203

The tcpdump shows:

19:08:59.963205 IP (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto 17,
length: 76) 172.16.0.200.ntp > 172.16.0.201.ntp: [bad udp cksum 14fd!] NTPv4,
length 48
Client, Leap indicator: (0), Stratum 11, poll 10s, precision -20
Root Delay: 0.000000, Root dispersion: 0.026153, Reference-ID:
127.127.1.0
Reference Timestamp: 3377119989.155361995 (2007/01/06 18:53:09)
Originator Timestamp: 3377119909.875000000 (2007/01/06 18:51:49)
Receive Timestamp: 3377119915.094943001 (2007/01/06 18:51:55)
Transmit Timestamp: 3377120939.962101995 (2007/01/06 19:08:59)
Originator - Receive Timestamp: +5.219943001
Originator - Transmit Timestamp: +1030.087102003
19:08:59.963364 IP (tos 0x0, ttl 128, id 19173, offset 0, flags [none],
proto 17, length: 76) 172.16.0.201.ntp > 172.16.0.200.ntp: [udp sum ok]
NTPv3, length 48
Server, Leap indicator: (0), Stratum 1, poll 10s, precision -6
Root Delay: 0.000000, Root dispersion: 10.906082, Reference-ID: LOCL
Reference Timestamp: 3377043999.015999998 (2007/01/05 21:46:39)
Originator Timestamp: 3377120939.962101995 (2007/01/06 19:08:59)
Receive Timestamp: 3377120934.750000000 (2007/01/06 19:08:54)
Transmit Timestamp: 3377120934.750000000 (2007/01/06 19:08:54)
Originator - Receive Timestamp: -5.212101995
Originator - Transmit Timestamp: -5.212101995

I have read somewhere "w32time on Windows is a SNTP server and not a real NTP"

Is it possible to synchronize an NTP client with a server running w32time?

Please help.
 
Reply With Quote
 
 
 
 
Andrei Ungureanu [MVP]
Guest
Posts: n/a

 
      01-10-2007, 05:19 PM
<<I have read somewhere "w32time on Windows is a SNTP server and not a real
NTP">>
True! - that's the reason it's not working.

--
Regards,
Andrei Ungureanu
www.eventid.net
Test our new EventReader!
http://www.altairtech.ca/eventreader...lt2.asp?ref=au


"George" <(E-Mail Removed)> wrote in message
news:BA169776-6EF4-4CD5-8A49-(E-Mail Removed)...
> Hi
>
> I am trying to synchronize a Linux Redhat AS (NTP Client, IP
> 172.16.0.200 )
> with a Windows 2003 Server (NTP Server, IP 172.16.0.201). My client is not
> synchronizing at all when I add only windows 2003 as server. If i add an
> other Linux machine (IP 16.74.33.203) as NTP Server then my Linux client
> get
> synchronize with it.
>
> Linux client and Windows server are connected directly using cross over
> cables.
>
> My ntp.conf file in Linux client.
>
> server 172.16.0.201 // Windows Server 2003
> server 16.74.33.203 // Linux Server
>
> driftfile /var/lib/ntp/drift
> restrict 172.16.0.201
> restrict 16.74.33.203
>
> The tcpdump shows:
>
> 19:08:59.963205 IP (tos 0x10, ttl 64, id 0, offset 0, flags [DF], proto
> 17,
> length: 76) 172.16.0.200.ntp > 172.16.0.201.ntp: [bad udp cksum 14fd!]
> NTPv4,
> length 48
> Client, Leap indicator: (0), Stratum 11, poll 10s, precision -20
> Root Delay: 0.000000, Root dispersion: 0.026153, Reference-ID:
> 127.127.1.0
> Reference Timestamp: 3377119989.155361995 (2007/01/06 18:53:09)
> Originator Timestamp: 3377119909.875000000 (2007/01/06 18:51:49)
> Receive Timestamp: 3377119915.094943001 (2007/01/06 18:51:55)
> Transmit Timestamp: 3377120939.962101995 (2007/01/06 19:08:59)
> Originator - Receive Timestamp: +5.219943001
> Originator - Transmit Timestamp: +1030.087102003
> 19:08:59.963364 IP (tos 0x0, ttl 128, id 19173, offset 0, flags [none],
> proto 17, length: 76) 172.16.0.201.ntp > 172.16.0.200.ntp: [udp sum ok]
> NTPv3, length 48
> Server, Leap indicator: (0), Stratum 1, poll 10s, precision -6
> Root Delay: 0.000000, Root dispersion: 10.906082, Reference-ID:
> LOCL
> Reference Timestamp: 3377043999.015999998 (2007/01/05 21:46:39)
> Originator Timestamp: 3377120939.962101995 (2007/01/06 19:08:59)
> Receive Timestamp: 3377120934.750000000 (2007/01/06 19:08:54)
> Transmit Timestamp: 3377120934.750000000 (2007/01/06 19:08:54)
> Originator - Receive Timestamp: -5.212101995
> Originator - Transmit Timestamp: -5.212101995
>
> I have read somewhere "w32time on Windows is a SNTP server and not a real
> NTP"
>
> Is it possible to synchronize an NTP client with a server running
> w32time?
>
> Please help.



 
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
DHCP Migration from windows server 2000 to windows server 2003 Amr Salah Windows Networking 3 02-04-2007 12:01 PM
Migrating to Windows Server 2003 from Windows Server 2000 and using Remote Desktop Client Navodit Windows Networking 1 09-13-2006 07:38 PM
TCP/IP Stack Improvements in Windows Server 2003 and Windows Server 2003 Service Pack 1 Deepak Bansal [MS] Windows Networking 0 06-14-2005 01:14 AM
Webcast on TCP/IP Stack Improvements in Windows Server 2003 and Windows Server 2003 Service Pack 1 Deepak Bansal [MS] Windows Networking 0 06-13-2005 11:55 PM
Unable to access Windows 2003 file server in a Windows 2003/XP Active Directory Domain Edward Ray Windows Networking 0 11-21-2003 03:03 AM



1 2 3 4 5 6 7 8 9 10 11