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

 

[ShackDaddy]

What output do you get when you type 'w32tm -source -v' on CITRIX1? Post it here, and I'll walk you through fixing this.

ShackDaddy

 

[cowboy00242]

I wonder if the issue is the time service, or that what you're seeing is just a symptom of another problem.

You say that nobody can log into the machine after this error occurs.

Time service error should not effect login, but not finding a domain controller in a timely manner will effect both the login attempts and the time synchronization. I think you have a problem relating to your network traffic...