SNTP Time server

[wklug]

We recently added two Windows Server 2003 servers to our network. On these, Event ID 29 is filling up the system log. It reads:


Source: W32Time
Category: None
Event ID: 29
Type: Error

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

So, I checked our Windows Server 2000 domain controller (which is our time server) by running the net time/querysntp and it states that "This computer is not currently configured to use a specific SNTP server."

Then, I set it to point to an SNTP server by running net time /setsntp:us.pool.ntp.org. Then, I verify that it stuck by running the querysntp and everything is OK.

However, if I log off and then back in and run the querysntp again, the first error is returned again stating that the computer is not configured to use a specific SNTP server.

Any ideas why it's not sticking???

Thanks in advance - Wayne

 

[Davetoo]

Set the SNTP server, then stop and restart the time service and see what it states afterwards.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[wklug]

I restarted the time service after setting the sntp and it stuck. But, I logged off of the server and logged back in, ran a query, and it still says that it's not configured to use a specific sntp server...

 

[adcfaq]

try a different sntp servre, like time.winodws.com

---------------------------------------
Sr. Directory Services/Exchange Consultant

http://adcfaq.8m.com/

 

[wklug]

I have tried this, but no luck.

 

[PScottC]

Check the permissions on the registry key that holds these settings. Make sure that it is inheriting the permission from its parent.

Do you have administrative permissions on the system you are trying to modify?

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[wklug]

Thank you, I do have Domain Admin (Local administrator) permissions to this server. I verified my registry permissions by opening up c:\winnt\system32\config and ensuring that I have full access to these files. This is the only way I know to check security on the registry files. Please advise if there is another way.

Anyway, I verified that I do have full access to these files, and tried setting the sntp server again - no luck.

 

[PScottC]

Using regedt32, check inheritance on the following keys:

HKLM\SYSTEM\CurrentControlSet\Services\w32time\

and

HKLM\SYSTEM\CurrentControlSet\Services\w32time\Parameters\

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[wklug]

Thank you. I have full access to these registry keys, but it still will not save the SNTP server.

 

[PScottC]

When you do the setsntp, do you see the selection appear under the "parameters" in the registry?

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[wklug]

Here's an interesting bit of information...when I first log on and check the W32time\parameters, ntpserver is not listed at all. Then, I run net time /setsntp:time.windows.com, and the value appears.

I log off, log back in, check W32time\parameters, and ntpserver is gone again until I set sntp again.

 

[PScottC]

Are there any logon/logoff scripts running with the logon that you are using? Could they affect what you are doing?

Do you have any type of registry protection software running? AV, Anti-Spyware, SMS, MOM, etc... that could do this?

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[wklug]

Yes! This is it! Each person logs on to their computer and a batch script is run. For me, the top line of the batch script is:

NET TIME \\scpserver2 /DOMAIN:SCP /SET /Y

Then, it goes on to map a few network drives. Apparently when I log on to scpserver2 and it refers to itself, it loses the ntpserver value. Is this line necessary in our script anyway? I'm not sure what exactly it is accomplishing. Can I eliminate this out of our batch logon scripts and not have any problems?

 

[PScottC]

You only need that line for systems that are NT4 or below. 2000 and above uses the domain hierarchy for time resolution.

You can modify your script like this...

 If /I not "%computername%" == "scpserver2" NET TIME \\scpserver2 /DOMAIN:SCP /SET /Y

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers

 

[wklug]

Great! Thanks so much for your help. So modifying the script to what you suggested basically will run net time //scpserver2 if the computer name is not scpserver2, correct? I think I will just eliminate the line completely since all of our computers are Win2000 or above.

Thanks once again for the solution.

Wayne

 

[PScottC]

Yes. I have heard some remarks from people on the forum about having a hard time with time distribution, so they use that command in the logon script as a "just in case of".

Good Luck!

PSC

Governments and corporations need people like you and me. We are samurai. The keyboard cowboys. And all those other people out there who have no idea what's going on are the cattle. Mooo! --Mr. The Plague, from the movie "Hackers