Tony Giangreco
asked on
Problem contacting NTP server from Win 2003 behind firewall
I've had ongoing problems trying to get a Windows 2003 DC to get time from any NTP server on the web. I've tried following docs on the microsoft site to sync with an NTP server, but cannot get it working.
I find this message in the event viewer
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 9/16/2011
Time: 8:59:58 AM
User: N/A
Computer: Hxxx
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 120 minutes. NtpClient has no source of accurate time.
I find this message in the event viewer
Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 9/16/2011
Time: 8:59:58 AM
User: N/A
Computer: Hxxx
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 120 minutes. NtpClient has no source of accurate time.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
and as well as in windows firewall also
ASKER
Hi Number-1
I performed this ok:
Stop the time service
Code: [ Select ]net stop w32time <enter>
When I get to the next line, do I edit the registry and update a key? I tryied typeing it into the cmd prompt and it said the service was not started (I'm assuming it's the time service because the previous command stopped it.
Then configure the time source
Code: [ Select ]w32tm /config /manualpeerlist:XXX.XXX.XX X.XXX,0x8 /syncfromflags:MANUAL /reliable:yes /update <enter>
I performed this ok:
Stop the time service
Code: [ Select ]net stop w32time <enter>
When I get to the next line, do I edit the registry and update a key? I tryied typeing it into the cmd prompt and it said the service was not started (I'm assuming it's the time service because the previous command stopped it.
Then configure the time source
Code: [ Select ]w32tm /config /manualpeerlist:XXX.XXX.XX
No it should work from command line. This might explain it a bit better
http://www.1stbyte.com/2009/04/07/configure-windows-server-2003-and-2008-w32tm-commands-on-domain-controller/
http://www.1stbyte.com/2009/04/07/configure-windows-server-2003-and-2008-w32tm-commands-on-domain-controller/
that first w32tm command is all one line.
w32tm /config /manualpeerlist:”0.pool.nt p.org 1.pool.ntp.org 2.pool.ntp.org pool.ntp.org”,0×8 /syncfromflags:MANUAL /reliable:yes
w32tm /config /update
net stop w32time
net start w32time
w32tm /resync /rediscover
That should do it. However, always make sure you firewall is open to port 123 outbound! I initially was receiving this error after running a “w32tm /resync” :
The computer did not resync because no time data was available.
In my case, that was caused by my firewall blocking port 123 for NTP traffic. Go figure, we’ve been running this particular network for probably 2 years with that firewall blocking port 123, and only now did someone come and ask “why is our computer time off by 6 or 7 minutes?” This is when you say, “Welcome to the world, can I help you?” (Good old Beavis) Well, at least we got our server configured better as a “reliable” time source with the right ntp.org pools.
w32tm /config /manualpeerlist:”0.pool.nt
w32tm /config /update
net stop w32time
net start w32time
w32tm /resync /rediscover
That should do it. However, always make sure you firewall is open to port 123 outbound! I initially was receiving this error after running a “w32tm /resync” :
The computer did not resync because no time data was available.
In my case, that was caused by my firewall blocking port 123 for NTP traffic. Go figure, we’ve been running this particular network for probably 2 years with that firewall blocking port 123, and only now did someone come and ask “why is our computer time off by 6 or 7 minutes?” This is when you say, “Welcome to the world, can I help you?” (Good old Beavis) Well, at least we got our server configured better as a “reliable” time source with the right ntp.org pools.
Looks like the article above just stops & restarts the service after the config. Maybe that will work better for you.
ASKER
Number-1,
I tried the commands and they appeared to work. the event logs shows time was received. I will monitor this server and let you know what happens. Tkx
I tried the commands and they appeared to work. the event logs shows time was received. I will monitor this server and let you know what happens. Tkx
ASKER
Worked great. Thanks!!
123/udp #Network Time Protocol