John Bartow
john at winhaven.net
Tue Jul 29 09:04:03 CDT 2003
I use NISTime32 to synch the server with an atomic clock and NET TIME to synch the workstations to the server. As someone mentioned the machine clocks aren't that far off that I have to update the server more than once a day or so (I'm not in a nuclear power plant or anything). I use NET TIME to keep all machines in synch with each other because then my network based file comparison/synching is more accurate, etc. My machines are all in very close synch my network may not be :o) John B. BTW My quick email to JC yesterday may have given the impression of such but the Net Time server does not need to be a "server" it can be any NT OS based machine on your network. > > On 29 Jul 2003 at 8:21, Erwin Craps wrote: > > > > > > > NET TIME has the advantage you do'nt need an internet connection (and > > you have less internet trafic, but I supose that aint much for an atomic > > clock). > > Don't forget that not all computers in a network are autorized to have > > internet access and certainly not routing functions. > > (I supose D4 or AtomTime (is another one) is not using port 80... > > > > Depends on which protocol(s) they use. > I use About Time (careware by Paul Lutus, developer of the HTML editor > Archnophilia). It can use one or more of 3 protocols > > Daytm - Port 13 > Time - Port 37 see RFC 738 > SNTP - Port 123 see RFC 2030 (and RFC 1305 for NTP) > > -- > Stuart McLachlan > Lexacorp Ltd > Application Development, IT Consultancy > http://www.lexacorp.com.pg