Topic: NTPD and client machines

[Jim Danvers]

Is the NTP (client or server?) on SME, well... just that - a client or a server?  Ie; I can trust that ~it's~ time is relatively accurate because I know that it periodically checks in with whatever I pointed it to (usually one of the navy servers, tick.usno.navy.mil), BUT....  are my client machines going to pick up the time from the SME box via the DHCP scope cfg?  This is no big deal...  I'm just re-doing my home lan / test network and am just wondering if I need to cfg the time service on 2K/XP machines to point to the mitel box, or if I should just use a net time \mitelbox /set /yes thing in the logon script.  It has been a long time since I cfg'd a DHCP server (windows machines), but I thought that there was a setting where you could pass the time down to client machines along with the IP lease (amongst other things)....

Thanks....

-=- jd -=-

[Dan Brown]

NTP on SME is both a client and a server.  However, the time isn't configured via DHCP; you'll need to use some kind of NTP client on your client machines.

My personal preference is to set the NTP server to broadcast (by adding "broadcast 192.168.1.255" to the ntp.conf file) and use a client like k9 on my client machines, but YMMV.

[Jim Danvers]

Good stuff - thanks Dan.  I'll have to read up / learn a little about the broadcast aproach that you take.

-=- jd -=-