Re: Auto Sync Client Time with Server

From: Tobias Redelberger (T.Redelberger_at_starnet-services.net)
Date: 04/06/04


Date: Tue, 6 Apr 2004 18:33:27 +0200

Should work automaticly if the client is well integrated in the AD-Structure
an no extra entires made e.g. via "net time".

Background-Info:

[..]
Windows 2000 Time Services

Windows 2000 provides W32Time service as a means of synchronizing time
across an Active Directory forest. W32Time uses Simple Network Time Protocol
(SNTP), which is a simplified version of Network Time Protocol (NTP). NTP
and SNTP are standards-based protocols, covered by RFC1305 and RFC 1769
(www.ietf.org for copies of these standards).

 NTP provides accuracies of 1 to 50 milliseconds, however its algorithms are
quite complex, and therefore the simplified SNTP protocol is used by Windows
2000 for the 'loose time synchronization' required by Kerberos.

 W32Time is installed by default on all Windows 2000 computers and starts
automatically on all computers joined to a domain. Net Logon service locates
and authenticates with a domain controller. The W32Time service then
requests time synchronization with the domain controller. Messages are sent
between the client and domain controller to estimate the network delay
between the two computers. To provide security, W32Time transmissions
between a client PC and the closest domain controller are signed using the
client's secure account password.

 If the client clock is behind the domain controller, it is adjusted
immediately. If it is more than 3 minutes ahead, it is also adjusted
immediately. If it is less than 3 minutes ahead, it is adjusted in steps
over a period of time.

 W32Time attempts synchronization every 45 minutes until the clocks have
synchronized successfully for 3 times. Synchronization occurs every 8 hours
after that.
[..]

Source: http://home.att.net/~HemantPatel/ADTime.doc

Tobias Redelberger

StarNET Services (HomeOffice)
Schoenbornstr. 57
D-97440 Werneck
Germany

Tel: +49-(0)9722-4835
Fax: +49-(0)9722-4836
Mobil: +49-(0)179-25 98 341

Email: T.Redelberger@starnet-services.net
Web-Tel: +49-(0)1212-5-11651621
Web-Fax: +49-(0)1212-5-11651621

"Brian Bonewitz" <bkbonew@aogeotech.com> schrieb im Newsbeitrag
news:162bc01c41bf1$c173b330$a601280a@phx.gbl...
> I know this has been addressed earlier in this newsgroup,
> but I was wanting
> to have the client's time updated everytime they logon to
> their computer
> with the server's time. Is there a setting or a script I
> can do to make
> this happen vs. manually setting the time on each client?
>
> Thanks,
> Brian



Relevant Pages

  • Site-tosite VPN Issue
    ... Windows Server 2003 domain controller ... Mixture of PCs running Windows 2000 Profressional with SP3 and Windows XP ... the VPN to the Windows Server 2003 domain controller. ... 12.7MB file from the server to the client PC. ...
    (microsoft.public.windows.server.networking)
  • Re: Client performance problem windows 2003 server...
    ... In addition, if you have the same problem with non-English client, please ... >Subject: Re: Client performance problem windows 2003 server... ... >>>Deploying Active Directory for Branch Office Environments ... >>>results from not having a domain controller in a particular site. ...
    (microsoft.public.windows.server.networking)
  • Re: group policy to turn off synchronization
    ... If the GP is not working then go to the client and turn off offline files. ... Windows Explorer/Tools/Folder Options/Offline Files tab ... > We are having a problem with errors on synchronization on XP SP2 clients ... > always occurrs after logoff and generates errors. ...
    (microsoft.public.windows.group_policy)
  • Re: Some clients cant access server
    ... Windows cannot obtain the domain controller name for your computer ... Group Policy processing aborted. ... This is from the client, ... Windows cannot access the file gpt.ini for GPO ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with an NT client in a Win 2k Domain
    ... Chriss,he client) utilize NetBI?OS, which if i recall ... correctly does use server message blocks. ... >> company uses a Windows 2000 Server as a Pimary Domain ... >> will not connect to the Domain Controller .. ...
    (microsoft.public.windows.server.active_directory)