Network problems and time server

[Yardyy]

I go these problem on our only win2k advanced server, all our other servers are NT4, we get a warning message in the event log saying
"Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 64
Date: 13-09-2002
Time: 14:03:50
User: N/A
Computer: Server Name
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:"

After that the whole network locks up, some users get the error message "the session has been cancelled"..

Am completely baffled, there are no other errors messages thats it, please can anyone help.. Yardyy

 

[IKnowNothing]

Your network is trying to synchronize with the global clock. If you dont have internet connectivity it will not synchronize. It is not a major error.

 

[Yardyy]

The problem is that all the computers on all the network freeze, you cant do anything cos the server is also the only fileserver..

If i disable the time service will that have any major effects on the server, that is the only the win2k server that we have Yardyy

 

[devilman0]

What you can do is have it set so that it doesn't sync at all. You should keep the time service running, this may have some adverse effects on the client computers. There was a microsoft white paper on the registry settings for win32tm (i think that is the 'technical' name for the time service). If you aren't too familular with the registry, i suggest not doing this on the important server, i would use a test server first. just my 2 cents.

Thanks,
James

 

[GiaBetiu]

Time is vital in a windows 2000 network because Kerberos protocol needs an accurate time synchronization.
look on this link:

http://support.microsoft.com/defaul...port/kb/articles/Q224/7/99.ASP&NoWebContent=1

Gia Betiu
gia@almondeyes.net
Computer Eng. CNE 4, CNE 5, MCSE Win2K
new:

http://www.almondeyes.net

(just started)

 

[devilman0]

Exacticaly, i had problems (major) when i disabled the win32 time, but then i re-enabled it and set the server to 'time is trusted' and the server won't (or shouldn't) try to set it's time by the internet. Later when we got a 24hr connection, i un-did that and entered on of the many time servers that are around the world. Also this way it keeps everything on time. When i mastakenly stoped the time, i had to go to the recovery console to be able to set the time back to automatic, it wasn't that big of a deal, but the server was down for like an hour while i fixed, tested, and brouht it back on line.

Thanks,
James