synroniza time on a Win2K domain

  • Thread starter Thread starter John Smith
  • Start date Start date
J

John Smith

how to force the clients (win2k pro) to update their time from
the 2k server domain controller?
 
This should be happening already by default. If you type

net time <enter>
 
Nah, Lanwench, not W2K. You just have to tell it once to synchronize with
the server:

net time /setsntp:servername
net stop w32time
w32tm -once -v
net start w32time

--
Regards,

Marina
Microsoft SBS-MVP

"Lanwench [MVP - Exchange]"
 
If the clients are joined to the domain this should be happening
automatically. The only flaw may be that the domain controller is not
synchronizing its time from an external source and may have disabled the
W32Time service as a result. Have you configured it to do so? If not, see
here:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;216734

If your computers are not domain members you will need to configure them to
pull the time from the domain controller.
 
the problem is: i change the time on the server and it takes a lot of time
for all the clients to get the new time
and during that period they cannot use any resources on the server
and i cant use computer managment to connect to the clients
 
Current time at \\SERVER01 is 5/4/2004 11:54 AM

The command completed successfully.


"Lanwench [MVP - Exchange]"
 
Unfortunately, that will happen if time synch gets too far out of bounds
between the server and the clients. But why would you change the time on
the server? That should not be necessary, especially if you have followed
proper practice as I mentioned in an earlier reply and set your server up to
keep its clock synchronized with an external time source.
 
well our accounting app requires some
operations to be done by the end of some
period - so sometimes i just move the clock
2 hours backward

Richard G. Harper said:
Unfortunately, that will happen if time synch gets too far out of bounds
between the server and the clients. But why would you change the time on
the server? That should not be necessary, especially if you have followed
proper practice as I mentioned in an earlier reply and set your server up to
keep its clock synchronized with an external time source.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


John Smith said:
the problem is: i change the time on the server and it takes a lot of time
for all the clients to get the new time
and during that period they cannot use any resources on the server
and i cant use computer managment to connect to the clients
 
That's going to cause problems.....any other way around this?

John said:
well our accounting app requires some
operations to be done by the end of some
period - so sometimes i just move the clock
2 hours backward

Richard G. Harper said:
Unfortunately, that will happen if time synch gets too far out of
bounds between the server and the clients. But why would you change
the time on the server? That should not be necessary, especially if
you have followed proper practice as I mentioned in an earlier reply
and set your server up to keep its clock synchronized with an
external time source.

--
Richard G. Harper [MVP Win9x] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


John Smith said:
the problem is: i change the time on the server and it takes a lot
of time for all the clients to get the new time
and during that period they cannot use any resources on the server
and i cant use computer managment to connect to the clients
 
Hmmm - that hasn't been my experience - NT4 & Win9x need a command in the
login script AFAIK - but by default all the win2k computers I've set up on
AD domains just pick it up automatically - and I set the server itself to
sync to an external time source. :-)
Nah, Lanwench, not W2K. You just have to tell it once to synchronize
with the server:

net time /setsntp:servername
net stop w32time
w32tm -once -v
net start w32time


"Lanwench [MVP - Exchange]"
This should be happening already by default. If you type

net time <enter>
 
Back
Top