Time synchronisation errors

[sggaunt]

I cannot get Time sync to work on our networked machines

I getting the following mewssages for each of these time servers...

an error occured while windows was synchronizing with time.windows.com

or

an error occured while windows was synchronizing with time.nist.gov

or

an error occured while windows was synchronizing with

http://www.time.cx.co.uk,

The peer is unreachable.

Steve [The sane]: Delphi a feersum engin indeed.

 

[Freestone]

NTP uses UDP port 123. Do you have a firewall blocking that port?

http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/intmgmt/26_xpwts.mspx

 

[bigbadbet]

It appears as though your not the only one.
it seems the best way is to do the following:

net stop w32time
w32tm /unregister [ignore error message]
w32tm /unregister [enter a second time]
w32tm /register
reg add hklm\system\currentcontrolset\services\w32time\parameters\ /v NtpServer /t reg_sz /d time.nist.gov /f
net start w32time

You might also want to read this before doing anything, note the post by MJJL:

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=1459955&SiteID=17

Tim
MCSA, A+, Network+

 

[bigbadbet]

Any Joy???
Tim

 

[aftertaf]

Once again, the time issue raises its head...

-We have W2000 & W XP machines.
-We have a NT4 domain, soon to migrate to AD.
-The PCs I am managing are not and will not be members of this domain, but of a workgroup having a different name than the domain.
-The PCs are on a separate network subnet than the NT4/2000/2003 servers.
-On both OSs, hosts file contains an entry from NTPSERVER being the router that links the 2 subnets.
-%FILESERVER% is our sql server and we can ping PCs from server, and ping server from lines.... (routing works)

Until now we used (unsuccessfully):

net time \\%FILESERVER% /DOMAIN:[domain] /SET /YES

unsuccessfully, as in we get an error message saying access denied.

With windows 2000 I have found the "w32tm -once" command that i place in a script we use to start our application -
I have also changed the Period setting in w32time registry from SpecialSkew to Weekly. We need to be able to control when the pc resynchronises, because sometimes they run ahead slightly and when it is resynched it causes problems in our application...
- My initial tests seem to be good.

But, I can't find the correct equivalent in XP that works.

I've tried BCastner's

net stop w32time
w32tm /unregister
w32tm /unregister
w32tm /register
net start w32time

on my test machine (which is my domain joined desktop machine....)


Aftertaf

Sometimes it just needs a good kicking.

 

[linney]

What are they going on about here? Have you got the time to try it?

w32tm, where's the "-once"

http://web2.minasi.com/forum/topic.asp?TOPIC_ID=15913

 

[aftertaf]

Hi Linney,

thanks for that link.

I'll check out all the different steps I see there, though I have already tried different /switch combinations....

Unsure whether the w32time service needs stopping and restarting before, after or during the tests itself.

Another complication I have is that the PC I have for testing is an XP, membr of a NT4 domain (with 2000+2003 AD servers, in place ready for a migration.... but still a NT4 domain) and the PCs I need to do this on with scripting are workgroup PCs.

I know that domain PCs resynchronise themselves, and maybe that is why the tests dont work on my desktop PC, but I also have had the RPC error on this PC and on a workgroup PC.
I run the commands as admin on the workgroup PC as the 'normal' user is just that, a Users member without admin rights on the PC. I have also used local GPO to restrict time changes to the admin account...

Like I said, I'll test different techniques mentioned in that other thread and ill keep you posted.

David

Aftertaf

Sometimes it just needs a good kicking.

 

[aftertaf]

I also have found this, in a similar google search:

By default, XP and higer OS do not enable "external" access of WMI services.
You'll have to set each PC's WMI security according your requirements.

and

I FOUND IT !!!

If your time service can't start it's because it's not set as 'Manual'
'automatic' start isn't good for this service

once i put it as manual start, i could start it with the command
net start w32time

and then the time sync could work !!!

i'll try that too.



Aftertaf

Sometimes it just needs a good kicking.