w32time

[scooter1974]

After this message user's cannot connect. The folowing mornig everything is back to Normal. I work with two Windows 2000 servers with Termnial Services and Citrix as member servers in a Windows NT 4.0 Domain.

Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 64
Date: 16-01-2002
Time: 17:34:44
User: N/A
Computer: CITRIX1
Description:
Because of repeated network problems, the time service has not been able to find a domain controller to synchronize with for a long time. To reduce network traffic, the time service will wait 960 minutes before trying again. No synchronization will take place during this interval, even if network connectivity is restored. Accumulated time errors may cause certain network operations to fail. To tell the time service that network connectivity has been restored and that it should resynchronize, execute "w32tm /s" from the command line.
Data:
0000: e5 03 00 00 å...
Robin Plomp
Senior System Engineer
CCA

Is a dream a lie if it don't come true
Or is it something worse

 

[janicef]

Search Microsoft Tech net for this problem. It is a known problem with W2K. I don't know why your user can't connect, I would not think this would cause a problem but you never know.

Janice

 

[Guest_imported]

Hey Scooter,
I had the same problem a few months ago- except it wouldn't go away the next morning! It turns out that Win2k _needs_ time synch to authenticate users. There were some good KB articles on MS's site about it. The short version is that there is a slight difference in how NT and Win2k handle time synch updates. A Win2k server will use the NT PDC, but can't understand the NTP packets it gets. Here's the registry entries that work for me....

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters]
"LocalNTP"=dword:00000000
"Period"="SpecialSkew"
"type"="NTP"
"ntpserver"="Your PDC IP address"
"Adj"=dword:0002625a
"msSkewPerDay"="-1566.0000"