I'm trying to sync the time on our routers and swithces with a Windows 2008R2 server, but it doesn't work. Has anyone managed to do this:
ntp server 192.168.2.164
sh ntp associations
address ref clock st when poll reach delay offset disp
*~127.127.1.1 .LOCL. 7 11 16 377 0.000 0.000 0.225
~192.168.2.164 .INIT. 16 - 1024 0 0.000 0.000 15937.
Windows 2008R2 server
w32tm /config /manualpeerlist:uk.pool.ntp.org,0x8 /syncfromflags:MANUAL
net stop w32time
net start w32time
Woudl Linux like Ubuntu be better?
Think that win 2008 supports ntp version 3 and cisco sends version 4
I tried the same, and with wireshark saw the version mismatch
If that's the case, you can change your version on the end of the server line:
ntp server 192.168.2.164 version 3
In IOS, I tried it with callmanager, but this can't be done (it seems)
Windows NTP is very limited (when non MS machine's are involved)
According to this link
You CANNOT use a Windows server because they use W32Time
Please rate useful posts.
According to MS, you can setup a Windows 2008 server R2 as a NTP server and NTP client.
On the MS site there is a procedure on how to do this.
I have tried it and I couldn't make it work (long time ago)
I gave up, and I am using an IOS or a Linux device to get the time around to non-MS devices.
Soory, here is the link:
Here is some light bedtime reading too.
Looks to me as if W2008 server can be a W32Time server for the AD or Domain etc
But it can only use NTP NET TIME as a client
Please rate useful posts.
Just to let you know I got it all working int he end. I have around 100 switches getting their NTP from 2 Windows 2008 R2 Enterprise servers which also act as Radius servers. I have the servers get their data and time from a pool of IP's on the internet.
They have been in 4-5 months now and I have had no issues and the logs to the syslog server all come in show the correct timestamp.
It is good that you got it to work. Thank you for posting to the forum to tell us that it now does work. Can you also tell us what you needed to do to get it to work (was it something on the Cisco side or was it something on the Windows side)?
I have put it all in a document at work, let me copy the info and paste here when I'm back inthe office on Tuesday. It was a pain, as I expected the switches to update their time and date straight away and thought it wasn't working, so I configured about 10 switches and left them over night across various sites and to my surprise when I checked in the morning they were all working. I thought it word work almost straight away but NTP doesn't seem to work liked that it seems. Now I have over 100 switches talking to these 2 servers for NTP and Radius.
Sorry but this is not true, I have done it with Windows 7 (and believe it can be done with Server 2003 and above). Please see my post.
I got this working from a cisco 2911 router to Windows 7 computer.
As per many articles, you are missing:-
But the one that allows Cisco kit to Sync is:-
This article http://www.cisco.com/c/en/us/support/docs/ip/network-time-protocol-ntp/108076-ntp-troubleshoot.html talks about having a root-dispersion higher than 1000ms (1 second) causing Cisco IOS-NTP to unsynchronizes itself.
This article http://htluo.blogspot.co.uk/2009/02/ntp-network-time-protocol.html#comment-form was the only one I found that added to the normal enable ntp server registry keys information, stating to change ‘HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\LocalClockDispersion’ from 10 to 0
There was also articles that said that the Windows NTP implementation was version 3, and therefore you had to append ‘version 3’ to the routers ‘ntp server x.x.x.x’ command. This may be perhaps true for earlier windows versions?, but was NOT required for Windows 7.
Microsoft's "interpretation" and understanding of the NTP standard is incorrect. You're better off configuring your core switch to go out and get NTP synchronization and let your Windows boxes to synch to your core switch for better result and accuracy.