rokerij
Technical User
- Feb 12, 2003
- 199
- 0
- 0
We are running on a Win NT 4.0 Server and have a mix operating systems across our network, using NT and Win 2000 Pro. One of our machines began to have some slow down yesterday afternoon with Send/Receive using Outlook (POP3), then the internet began to give errors and would not make a connection. Our internet utilizes our network to make the connection - we are able to connect to the network and use the shared files on the server. We have ran a Anti Virus program to be sure that it was not a virus. I have also gone ahead and ran defrag. We have been able to use a ping successfully and a tracert in the cmd prompt. There have been no changes to the network or workstation. We are not able to get to the net or use email, but have network connections to the server. We checked the event viewer and found a error message:
"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."
Upon researching the w32 on the net we found that if something was to go wrong during the process that we may have to reinstall the OS, well that detered me from running the w32tm /s in the command line. Has anyone ever experianced this?
"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."
Upon researching the w32 on the net we found that if something was to go wrong during the process that we may have to reinstall the OS, well that detered me from running the w32tm /s in the command line. Has anyone ever experianced this?
