Most people assume that computer clocks in servers, workstations and network devices are inherently accurate.ÌýThis is incorrect.ÌýMost of these clocks are set by hand to within a minute or two of actual time and are rarely checked after that.ÌýMany of these clocks are maintained by a battery-backedÌýdevice that may drift as much as a second per day.ÌýHaving any sort of accurateÌýtime synchronization is impossible if theseÌýclocks are allowed to run on their own.
In modern computer networks, time synchronization is critical because every aspect of managing, securing, planning, and debugging a network involves determining when events happen.Ìý Time also provides the only frame of reference between all devices on the network.ÌýWithout synchronized time, accurately correlating log files between these devices is difficult, even impossible.ÌýAlso:
TheÌýÌýhas long been the leader in time-setting software.ÌýSome companies solve the problem of synchronizing their networks by using NTP to go out on the Internet to get time from a publicÌýInternet Time Server.ÌýBut, this approach is a security concern because there must beÌýa "hole" left open in the firewall (UDP port 123) to allow packets containing the time information through.Ìý
A dedicated network time server behind your firewall protects you from the security risks inherent in obtaining Internet time. Also, a network time server on your LAN can reliably keep all the servers, workstations and network devices synchronized to within 1/2 to 2 milliseconds of each other (typical). This is much better than the many tens of milliseconds sync accuracy you would typically get from an Internet Time Server.
At É«ÓûÍõ³¯ we specialize in the manufacturing of very high-qualityÌýTime Servers.Ìý If you are an IT Administrator interested in time synchronization and in maintaining a high level of security on your network then clickÌýhereÌýfor more information.
Ìý