Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Syncing times across a single domain

Status
Not open for further replies.

BigFunkyChief

IS-IT--Management
Jan 22, 2004
115
US
I have done alot of reading on time syncing in a Windows 2003 network, and I think I'm confused on all the jargon and different options.

I have one single Windows 2003 SBS server, with about 20-30 clients. I'd like to maintain the time on the SBS server, and have the clients sync with the server.

Apparently that should work natively, but it's not. I've also seen the Group Policy settings for clients, but I haven't had any success. About the only thing I've gotten to work is the 'net time' statement from a command line, but I'd like Group Policy to do it, if possible, so I don't have to rely on a batch file.

The error I get in the Event Log on the client machines is :

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 14 minutes. NtpClient has no source of accurate time.

Then I get :

The time provider NtpClient was unable to find a domain controller to use as a time source. NtpClient will try again in 15 minutes.

Has anyone implemented a time sync solution like I'm trying to do, and if so, could you provide some basic help?

"Rule #1 - When stumped, check your Event Logs!
 
What NTP server does the command 'NET TIME /QUERYSNTP' give on your Domain controller and one of your clients?

Jeffrey
 
On the server, it shows time.windows.com.

On the workstation it shows the IP address of my server and time.windows.com.

I did add the following statement to my login script last night :

net time \\SERVERNAME /set /setsntp:

so it syncs the time during the login script, so the above results might be due to that.

"Rule #1 - When stumped, check your Event Logs!
 
If your clients are domain members (Windows 2000 or XP) they will by default attempt to sync thier clocks off a (any) Domain Controller. There is no need to configure anything manually on the clients. You should see W32Time system events logged on the clients like this:

The time service is now synchronizing the system time with the time source windows2003.server.com (ntp.d|192.168.1.50:123->192.168.1.10:123).

HTH

Andy
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top