W32 Time

[Dan]

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.

I understand that the PDC should connect via NNTP to an outside source to keep time synchronization. However our Firewall restriction does not allow NNTP. As a result I keep getting the above error in the Logs.

Can anyone give me direction as to an acceptable way of synchronizing my network time.???

Thanks

[shovel204]

I take it you have more than one server running.
Why not have all the other servers sync time with the PDC.



------------
Dan at 5/21/2002 11:11:55 AM


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.

I understand that the PDC should connect via NNTP to an outside source to keep time synchronization. However our Firewall restriction does not allow NNTP. As a result I keep getting the above error in the Logs.

Can anyone give me direction as to an acceptable way of synchronizing my network time.???

Thanks