Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 798
  • Last Modified:

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.
0
Tony Giangreco
Asked:
Tony Giangreco
  • 4
  • 3
  • 2
1 Solution
 
Amitabh SinghAWS Certified Solution Architect | L3 IT Specialist for CloudCommented:
did you check if port is open in your firewall ?
 123/udp                           #Network Time Protocol
0
 
Randy DownsOWNERCommented:
Try this

http://www.ozzu.com/mswindows-forum/how-configure-ntp-server-windows-2003-server-t91197.html

First thing you need to do is configure the domain controller to sync with a reliable time source. If you have two or more domain controllers you need to find the one that is acting as the PDC. To sync it with a time source open up a command prompt and perform the following:

Stop the time service
Code: [ Select ]net stop w32time <enter>


Then configure the time source
Code: [ Select ]w32tm /config /manualpeerlist:XXX.XXX.XXX.XXX,0x8 /syncfromflags:MANUAL /reliable:yes /update <enter>


The X's can be the IP address of the time server or the domain name of a time server such as time-a.nist.gov.

Once the command above is done you need to start the W32Time service
Code: [ Select ] [ Line Numbers Off ]
net start w32time <enter>
w32tm /resync <enter>

01.net start w32time <enter>
02.w32tm /resync <enter>


The <enter> means to press the enter key.

Next you need to sync all of your client PC's to the domain controller. You can do the following from the command line.

Code: [ Select ] [ Line Numbers Off ]
net stop w32time <enter>
w32tm /config /manualpeerlist:peers /syncfromflags:DOMHIER /update <enter>
net start w32time <enter>
w32tm /resync </enter>

01.net stop w32time <enter>
02.w32tm /config /manualpeerlist:peers /syncfromflags:DOMHIER /update <enter>
03.net start w32time <enter>
04.w32tm /resync </enter>


You can remotely do these commands using psexec from SysInternals if you have a lot of client machines.
0
 
Amitabh SinghAWS Certified Solution Architect | L3 IT Specialist for CloudCommented:
and as well as in windows firewall also
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
Tony GiangrecoAuthor Commented:
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.XXX.XXX,0x8 /syncfromflags:MANUAL /reliable:yes /update <enter>
0
 
Randy DownsOWNERCommented:
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/

that first w32tm command is all one line.

w32tm /config /manualpeerlist:”0.pool.ntp.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.
0
 
Randy DownsOWNERCommented:
0
 
Randy DownsOWNERCommented:
Looks like the article above just stops & restarts the service after the config. Maybe that will work better for you.
0
 
Tony GiangrecoAuthor Commented:
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
0
 
Tony GiangrecoAuthor Commented:
Worked great. Thanks!!
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now