Home | Site Map | Cisco How ToNet How To | Wireless |Search | Forums | Services | Donations | Careers | About Us | Contact Us|

Unable to synch time with external time-server

Active Directory, Domain, DNS, WINS, DHCP, SBS, New Releases.

Unable to synch time with external time-server

Postby guest » Wed Aug 22, 2012 8:43 pm

Actually, I'm working on a problem, which really makes me headaches...

I'm building a new domain with time-critical applications running on it. For guaranting a exact time allover the domain, I wanted to create the link to time.ethz.ch as desript on http://support.microsoft.com/kb/816042/en-us

Unfortunately, Nothing happend and if I check w32tm /monitor, I still see this:
RefID: 'LOCL' [0x4C434F4C]
Stratum: 1

I did following command:
w32tm /config /update /manualpeerlist:time.ethz.ch /syncfromflags:MANUAL /reliable:YES

I searched the net and tried many solutions - nothing helped. I opened the port on the firewall and I can see the service demands of my server passing!

If I make this:
w32tm /stripchart /computer:time.ethz.ch

I get:
Tracking time.ethz.ch [129.132.97.15:123].
The current time is 05.02.2010 11:24:33.
11:24:33 error: 0x800705B4

The errors won't stop 'till I make Ctrl+C

With the old system (Win 2k3 it works like a charm (same time-server). Now in Win 2008 R2 that works not. What's wrong? Any ideas?

Thank you very much for your help
Alex
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9027
Joined: Mon Nov 27, 2006 1:10 pm

Re: Unable to synch time with external time-server

Postby guest » Wed Aug 22, 2012 8:43 pm

They've already configured the NTP time sources successfully, as indicated by by their second last post (the one with the /query /peers results), so that's not going to be the issue in this case.

Combined with the results from the prior post with the /stripchart results being listed all with values of zero (which indicates their server actually didn't get a result), then what we're dealing with is an issue local to their site, where the new Windows server they wish to use as a NTP server is not able to contact the configured NTP servers. This is further validated by the event log entry. In othre words, the Windows server is configured just fine, but there's other network issues that need to be fixed.

The above information is stil definitelyl useful on a general level, just not in this specific case. Also keep in mind that w32tm is a little safer to use, rather than manually editing the registry.
Tablet and Smartphone Setup Guide
http://www.quicksetupguide.com

Troubleshooting Vista Wireless
http://chicagotech.net/
guest
 
Posts: 9027
Joined: Mon Nov 27, 2006 1:10 pm


Return to Windows

Your Ad Here

Who is online

Users browsing this forum: Google [Bot] and 2 guests