In Windows 2000 and Windows XP Pro, a common time standard is critical to a secure network communication within a Domain. The windows time service runs in the background and syncronizes the workstation's time with that of the domain. A hierarchy is established that determines which servers (authoritative) provide the time to the lower elements in the domain. MSFT systems expect the time in a domain to be within 2 seconds of each other and if not, the workstations will not be able to authenticate in the domain. For WANS, this is typically 20-30 seconds. This can be configured by the domain admin though. It is crucial that you do not sync your workstation to the atomic clock if the authoritative time server is not synced with it also or the next time you try to authenticate, you may not be able to until you correct your time on the workstation to be within the parameters allowed in the domain if your domain admin has configured authentication this way. You might want to check first.

Tracy

Some more info:

http://www.microsoft.com/windows2000/techinfo/howitworks/security/wintimeserv.asp


>>The other day my computer clock was off by 15 minutes which made
>>me late for a meeting. I know I can simply update the clock
>>every now and then but is there a way to grab the time from a
>>web site that provides the atomic time?
>>
>>After that I just need to know how to set the current time
>>on my computer using VFP.
>
>I use Atomic Clock on my home PC. The network guy at work said you should *never* change the system time from a workstation on the office network, it can cause all sorts of network problems. I don't know whether he's right or not but thought I would pass it along as a "FWIW".
>
>Mike