winxp time server

steve · External Since: Sep 07, 2009 Posts: 1

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 · External Since: Feb 19, 2004 Posts: 7325

On Mon, 07 Sep 2009 15:37:54 -0400, steve <steve RemoveThis @email.net> wrote:

> 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.

--
Ken Blake, Microsoft MVP - Windows Desktop Experience
Please Reply to the Newsgroup

Olórin · External Since: Feb 02, 2009 Posts: 50

Ken Blake, MVP wrote:
> On Mon, 07 Sep 2009 15:37:54 -0400, steve <steve.RemoveThis@email.net> wrote:
>
>> 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.

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

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

M.I.5¾ · External Since: Jul 12, 2006 Posts: 239

"Ken Blake, MVP" <kblake.DeleteThis@this.is.an.invalid.domain> wrote in message
news:j4qaa55uqifutjtm49hsudqpvbdphsgaun@4ax.com...
>
> On Mon, 07 Sep 2009 15:37:54 -0400, steve <steve.DeleteThis@email.net> wrote:
>
>> 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.
>

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 · External Since: Sep 08, 2009 Posts: 10

On Sep 8, 8:01 am, "M.I.5¾" <no.....TakeThisOut@no.where.NO_SPAM.co.uk> wrote:
> "Ken Blake, MVP" <kbl....TakeThisOut@this.is.an.invalid.domain> wrote in messagenews:j4qaa55uqifutjtm49hsudqpvbdphsgaun@4ax.com...
>
>
>
>
>
> > On Mon, 07 Sep 2009 15:37:54 -0400, steve <st....TakeThisOut@email.net> wrote:
>
> >> 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.
>
> 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 · External Since: Sep 08, 2009 Posts: 10

On Sep 8, 8:05 pm, "kim" <fi... RemoveThis @ntlworld.com> wrote:
> 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.
>
> "Hodges" <mrezous... RemoveThis @garrifulio.mailexpire.com> wrote in message
>
> news:c6c9203b-79de-451b-9c86-a27bd8c9afd1@t2g2000yqn.googlegroups.com...
> On Sep 8, 8:01 am, "M.I.5¾" <no.... RemoveThis @no.where.NO_SPAM.co.uk> wrote:
>
>
>
> > "Ken Blake, MVP" <kbl... RemoveThis @this.is.an.invalid.domain> wrote in
> > messagenews:j4qaa55uqifutjtm49hsudqpvbdphsgaun@4ax.com...
>
> > > On Mon, 07 Sep 2009 15:37:54 -0400, steve <st... RemoveThis @email.net> wrote:
>
> > >> 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.
>
> > 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.

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

kim · External Since: Sep 09, 2009 Posts: 2

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.

"Hodges" <mrezoustah.TakeThisOut@garrifulio.mailexpire.com> wrote in message
news:c6c9203b-79de-451b-9c86-a27bd8c9afd1@t2g2000yqn.googlegroups.com...
On Sep 8, 8:01 am, "M.I.5¾" <no.....TakeThisOut@no.where.NO_SPAM.co.uk> wrote:
> "Ken Blake, MVP" <kbl....TakeThisOut@this.is.an.invalid.domain> wrote in
> messagenews:j4qaa55uqifutjtm49hsudqpvbdphsgaun@4ax.com...
>
>
>
>
>
> > On Mon, 07 Sep 2009 15:37:54 -0400, steve <st....TakeThisOut@email.net> wrote:
>
> >> 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.
>
> 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.

M.I.5¾ · External Since: Jul 12, 2006 Posts: 239

"Hodges" <mrezoustah RemoveThis @garrifulio.mailexpire.com> wrote in message
news:c6c9203b-79de-451b-9c86-a27bd8c9afd1@t2g2000yqn.googlegroups.com...
On Sep 8, 8:01 am, "M.I.5¾" <no.... RemoveThis @no.where.NO_SPAM.co.uk> wrote:
> "Ken Blake, MVP" <kbl... RemoveThis @this.is.an.invalid.domain> wrote in
> messagenews:j4qaa55uqifutjtm49hsudqpvbdphsgaun@4ax.com...
>
>
>
>
>
> > On Mon, 07 Sep 2009 15:37:54 -0400, steve <st... RemoveThis @email.net> wrote:
>
> >> 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.
>
> 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.

----------

You need 'nist.time-a.gov' for Windows XP. 'nist-time.gov' was modified to
support Vista (though apparently that doesn't work at present either).

Richard · External Since: May 13, 2009 Posts: 36

"M.I.5¾" <no.one.DeleteThis@no.where.NO_SPAM.co.uk> wrote in message
news:4aa76745$1_1@glkas0286.greenlnk.net...
>
> "Hodges" <mrezoustah.DeleteThis@garrifulio.mailexpire.com> wrote in message
> news:c6c9203b-79de-451b-9c86-a27bd8c9afd1@t2g2000yqn.googlegroups.com...
> On Sep 8, 8:01 am, "M.I.5¾" <no.....DeleteThis@no.where.NO_SPAM.co.uk> wrote:
>> "Ken Blake, MVP" <kbl....DeleteThis@this.is.an.invalid.domain> wrote in
>> messagenews:j4qaa55uqifutjtm49hsudqpvbdphsgaun@4ax.com...
>>
>>
>>
>>
>>
>> > On Mon, 07 Sep 2009 15:37:54 -0400, steve <st....DeleteThis@email.net> wrote:
>>
>> >> 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.
>>
>> 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.
>
> ----------
>
> You need 'nist.time-a.gov' for Windows XP. 'nist-time.gov' was modified
> to support Vista (though apparently that doesn't work at present either).

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