winxp time server

[steve]

i am operating a peer to peer network with several PCs running both Win2000 and WinXP
and NO internet access. I find it useful to have all the computers synchronize their
system time with 1 computer on the network. i then just set that 1 computer's clock
about once every week or 2 or 3 just to keep it close to accurate. that computer was
running Win2000, however i am getting rid of that computer and replacing it with a
newer 1 running WinXP. the registry settings controlling time got much more
complicated going from Win2000 to WinXP. Even after reading over the MS technote on
configuring an authoritative time server in WinXP, I am still not sure just how to do
this. seems to be written more for a domain time servers rather than P2P. I just
want the new XP computer to be able act as a time server so that the others query the
it for its system time and it responds. of course, the new XP computer would not go
out anywhere to synchronize its clock, i do this manually. i would appreciate any
help with registry settings for the new XP computer.

i tried posting in the configuration management newsgroup but no response, thought i
might try here.

TIA
steve

 

[Ken Blake, MVP]

i am operating a peer to peer network with several PCs running both Win2000 and WinXP
and NO internet access. I find it useful to have all the computers synchronize their
system time with 1 computer on the network. i then just set that 1 computer's clock
about once every week or 2 or 3 just to keep it close to accurate. that computer was
running Win2000, however i am getting rid of that computer and replacing it with a
newer 1 running WinXP. the registry settings controlling time got much more
complicated going from Win2000 to WinXP. Even after reading over the MS technote on
configuring an authoritative time server in WinXP, I am still not sure just how to do
this. seems to be written more for a domain time servers rather than P2P. I just
want the new XP computer to be able act as a time server so that the others query the
it for its system time and it responds. of course, the new XP computer would not go
out anywhere to synchronize its clock, i do this manually. i would appreciate any
help with registry settings for the new XP computer.

No registry settings are needed. Just run the following command on
each computer that needs to synch with the "server":

net time \computername-of-the-server /set

You can do that manually on each computer, or else put it in a batch
file that is scheduled to be run as often as you want.

 

[Olórin]

No registry settings are needed. Just run the following command on
each computer that needs to synch with the "server":

net time \computername-of-the-server /set

You can do that manually on each computer, or else put it in a batch
file that is scheduled to be run as often as you want.

Quick amendment, if OP goes this route: s/be a double backslash, thusly:

net time \\computername-of-the-server /set

 

[M.I.5¾]

No registry settings are needed. Just run the following command on
each computer that needs to synch with the "server":

net time \computername-of-the-server /set

You can do that manually on each computer, or else put it in a batch
file that is scheduled to be run as often as you want.

There seems to be a problem with the time servers at present, because all of
the PCs under my control have not been synchronizing for a few weeks now.
An error is reported for every time server. A trawl around various
discussion forums suggests that I am not alone, though some seem to have got
results from one or two servers.

I have heard a whisper (and it is nothing more than that) that the time
servers have adopted measures to guard against DOS attacks and the the
manner in which windows interrogates the servers is interpreted as such an
attack and the originating IP is then temporarily blocked. But it is only a
whisper, though quite plausible.

 

[Hodges]

There seems to be a problem with the time servers at present, because allof
the PCs under my control have not been synchronizing for a few weeks now.
An error is reported for every time server.  A trawl around various
discussion forums suggests that I am not alone, though some seem to have got
results from one or two servers.

I have heard a whisper (and it is nothing more than that) that the time
servers have adopted measures to guard against DOS attacks and the the
manner in which windows interrogates the servers is interpreted as such an
attack and the originating IP is then temporarily blocked.  But it is only a
whisper, though quite plausible.

The Windows timeservers have never worked for me in the years that
I've been using it. nist.time.gov sometimes does, I found one or two
more but I'm not at home to check. I use AnalogX Atomic Timesync to
sync my clock.

 

[kim]

Don`t know if this is the sort of thing you`re after Atomic Clock Sync v3.0
.. http://www.worldtimeserver.com/atomic-clock/ A good freeware program.

message








There seems to be a problem with the time servers at present, because all
of
the PCs under my control have not been synchronizing for a few weeks now.
An error is reported for every time server. A trawl around various
discussion forums suggests that I am not alone, though some seem to have
got
results from one or two servers.

I have heard a whisper (and it is nothing more than that) that the time
servers have adopted measures to guard against DOS attacks and the the
manner in which windows interrogates the servers is interpreted as such an
attack and the originating IP is then temporarily blocked. But it is only
a
whisper, though quite plausible.

The Windows timeservers have never worked for me in the years that
I've been using it. nist.time.gov sometimes does, I found one or two
more but I'm not at home to check. I use AnalogX Atomic Timesync to
sync my clock.

 

[Hodges]

Don`t know if this is the sort of thing you`re after Atomic Clock Sync v3..0
.http://www.worldtimeserver.com/atomic-clock/A good freeware program.






The Windows timeservers have never worked for me in the years that
I've been using it.  nist.time.gov sometimes does, I found one or two
more but I'm not at home to check.  I use AnalogX Atomic Timesync to
sync my clock.

No. I already said I use AnalogX Atomic Timesync, I never asked for a
program. All of Analog X's software is free, and Atomic Timesync is
available at http://analogx.com/contents/download/Network/ats/Freeware.htm

Also, the timeserver I use is nist1.symmetricom.com and it's up more
than time.windows.com and time.nist.gov

 

[M.I.5¾]

message








There seems to be a problem with the time servers at present, because all
of
the PCs under my control have not been synchronizing for a few weeks now.
An error is reported for every time server. A trawl around various
discussion forums suggests that I am not alone, though some seem to have
got
results from one or two servers.

I have heard a whisper (and it is nothing more than that) that the time
servers have adopted measures to guard against DOS attacks and the the
manner in which windows interrogates the servers is interpreted as such an
attack and the originating IP is then temporarily blocked. But it is only
a
whisper, though quite plausible.

The Windows timeservers have never worked for me in the years that
I've been using it. nist.time.gov sometimes does, I found one or two
more but I'm not at home to check. I use AnalogX Atomic Timesync to
sync my clock.

 

[Richard]

The Windows timeservers have never worked for me in the years that
I've been using it. nist.time.gov sometimes does, I found one or two
more but I'm not at home to check. I use AnalogX Atomic Timesync to
sync my clock.

I've noticed that time.windows.com has been getting errors lately.
I just tried time.nist.gov and it updated without problem.
(Using Windows XP Professional Edition Service Pack 3, fully patched.)

FWIW. --Richard