dalva
asked on
Why are non windows ntp clients not updating from a windows ntp server?
Our non windows ntp clients are not receiving time updates. Why?
Scenario:
MAINT2 is our NTP server. It is a Windows 2003 which reaches out to time.windows.com for the time.
Our PDC gets the time from MAINT2. All other domain desktops and servers get their time from our PDC. This portion works as expected.
All NON Windows equipment is pointed to MAINT2 for the time. Non Windows equipment includes printers, VOIP phones, network equipment etc.
The non Windows equipment is not receiving updates. It did work at one time until we realized MAINT2 was not actually reaching the Internet for the time due to a firewall issue. Since we corrected MAINT2 being able to reach the time server on the Internet the non Windows clients are not getting time updates.
Using WireShark we can see the one way conversation between a phone and MAINT2. The phone makes a time request but MAINT2 does not reply back.
We've tried every idea we have come across but still no luck. Any ideas? Is there some kind of authentication getting in the way?
Scenario:
MAINT2 is our NTP server. It is a Windows 2003 which reaches out to time.windows.com for the time.
Our PDC gets the time from MAINT2. All other domain desktops and servers get their time from our PDC. This portion works as expected.
All NON Windows equipment is pointed to MAINT2 for the time. Non Windows equipment includes printers, VOIP phones, network equipment etc.
The non Windows equipment is not receiving updates. It did work at one time until we realized MAINT2 was not actually reaching the Internet for the time due to a firewall issue. Since we corrected MAINT2 being able to reach the time server on the Internet the non Windows clients are not getting time updates.
Using WireShark we can see the one way conversation between a phone and MAINT2. The phone makes a time request but MAINT2 does not reply back.
We've tried every idea we have come across but still no luck. Any ideas? Is there some kind of authentication getting in the way?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
giltjr,
This morning everything is now working as expected. We tweaked a few reg settings such as "PhaseCorrectRate"=dword:0
What is the difference between a Windows time server and an NTP server on a Windows server? We used w32tm to set things up.
This morning everything is now working as expected. We tweaked a few reg settings such as "PhaseCorrectRate"=dword:0
What is the difference between a Windows time server and an NTP server on a Windows server? We used w32tm to set things up.
ASKER
frankhelk,
I read your article. It answered the difference between Windows time server and Windows NTP server.
If we start having issues again, we'll yank Windows time server and find a Windows NTP application to use.
I read your article. It answered the difference between Windows time server and Windows NTP server.
If we start having issues again, we'll yank Windows time server and find a Windows NTP application to use.
Not sure if this will work in a Active Directory environment, but here is how to make a standalone Windows server a NTP server:
http://www.techrepublic.com/blog/the-enterprise-cloud/configure-a-standalone-ntp-server-in-windows-server/
http://www.techrepublic.com/blog/the-enterprise-cloud/configure-a-standalone-ntp-server-in-windows-server/
If you kick W32time, I would recommend the NTP port for Windows by Meinberg (don't forget to grab their "NTP cheat sheet" - very helpful).
I' havn't tried the other flavours around (besides of the Hopf version some years ago), but I have good experience with it and it comes with a pretty installer.
I havn't done an installation for some time now, but I faintly remember that there's a trick when installing the x86 version (the only one ...) on x64 Windows - maybe the installed configuration file ntp.conf ends up in %WINDIR%\SysWOW64\Drivers\
I' havn't tried the other flavours around (besides of the Hopf version some years ago), but I have good experience with it and it comes with a pretty installer.
I havn't done an installation for some time now, but I faintly remember that there's a trick when installing the x86 version (the only one ...) on x64 Windows - maybe the installed configuration file ntp.conf ends up in %WINDIR%\SysWOW64\Drivers\
ASKER
giltjr,
After reading the article about how to make a stand alone NTP Windows server we think we know what happened. While tweaking various reg settings, my co-worker recalls changing the Enabled from 0 to 1 without really understanding why. This is the only explanation which makes sense as to why it started working again. With that in mind, we're closing the ticket and awarding the points to you.
[HKEY_LOCAL_MACHINE\SYSTEM
"InputProvider"=dword:0000
"AllowNonstandardModeCombi
"DllName"="C:\\WINDOWS\\sy
"Enabled"=dword:00000001
After reading the article about how to make a stand alone NTP Windows server we think we know what happened. While tweaking various reg settings, my co-worker recalls changing the Enabled from 0 to 1 without really understanding why. This is the only explanation which makes sense as to why it started working again. With that in mind, we're closing the ticket and awarding the points to you.
[HKEY_LOCAL_MACHINE\SYSTEM
"InputProvider"=dword:0000
"AllowNonstandardModeCombi
"DllName"="C:\\WINDOWS\\sy
"Enabled"=dword:00000001
But if you like to use NTP (a excellent choice, btw), why not consider to use the "real thing" - a Windows port of the *ux NTP daemon ? Easy to install, simple to config, precise, stable as a rock and with the footprint of an ant.
See my article on NTP for more details and don't hesitate to ask me for assistance if needed.