From owner-freebsd-questions Sun Jan 13 9:44: 0 2002 Delivered-To: freebsd-questions@freebsd.org Received: from relay01.roc.frontiernet.net (alteon01b.roc.frontiernet.net [66.133.130.232]) by hub.freebsd.org (Postfix) with SMTP id 1C61037B404 for ; Sun, 13 Jan 2002 09:43:54 -0800 (PST) Received: (qmail 18816 invoked from network); 13 Jan 2002 17:43:52 -0000 Received: from unknown (HELO blacklamb.mykitchentable.net) ([207.173.227.80]) (envelope-sender ) by 0 (qmail-ldap-1.03) with SMTP for ; 13 Jan 2002 17:43:52 -0000 Received: from bigdaddy (bigdaddy [192.168.1.3]) by blacklamb.mykitchentable.net (Postfix) with SMTP id 4D9FCEE651; Sun, 13 Jan 2002 09:43:51 -0800 (PST) Message-ID: <003f01c19c59$dd03f110$0301a8c0@bigdaddy> From: "Drew Tomlinson" To: "Joe & Fhe Barbish" , "FBSD Questions" References: Subject: Re: ntpd as time server? Date: Sun, 13 Jan 2002 09:43:51 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Joe & Fhe Barbish" To: "FBSD Questions" Sent: Sunday, January 13, 2002 9:17 AM Subject: Re: ntpd as time server? > To all who replied to my original post, > > Thank you very much for your input and insight. > I have read every post in this thread and have come to > the following conclusions. Let me commend you for taking the time to write a follow-up post summarizing what you have learned. These types of posts are a great resource to have in the archives. > The ntpdate function is the brute force method of syncing > the pc hardware clock with any ntp internet server one > wants to use for this purpose. > For a home dialup ISP gateway box this is the recommended > method of keeping the gateway FBSD box's clock accurate > every time the box is booted. > > The small servers defined in inetd.conf include the > timed & timedc. This set of services use a different method > of pc clock syncing than ntpd. The main point is it does not > create a ntp protocol time server that can be accessed by IP address. > > The final option is ntpd. This function does get the time from a > internet ntp server to update the requesting FBSD box, and keeps > the clock accurate by making very small adjustment over long periods > of time. It can be configurated to broadcast time packets to all machines > on the private net it is connected to. > It is not a ntp time server with a unique IP address. I don't think this is correct. ntpd *IS* a time server and the IP address is the address of the machine you run it on. On my private network, I have a FBSD box on 192.168.20.4. I have a Win2K machine on 192.168.20.3. I have a ntp client program called "Automochron" that runs on the Win2K machine. In the client, I have the time server listed as 192.168.20.4 (the FBSD machine). The Win2K client gets time updates. I don't remember doing anything special with ntpd to set this up. I just used the standard xntpd that is bundled with the basic OS, put time server entries in ntp.conf, and ran the daemon. Please, anyone correct me if I'm missing something. Thanks, Drew > Only FBSD boxes on the private net with ntpd clients can hear > the broadcasted time packets and adjust there clocks. The only way for a > Winbox to use this function is to have Samba running on the FBSD to fake > out the Winboxs into thinking it's a NT or Win2k server. This sure is > overkill just to get synced time across the private net. One responder > did point out that there is a Winbox program which will utilize the ntpd > info to set the Winbox clock. This may be a option if I ever have to upgrade > all the Winboxs to a common release of Windows, other than that it would > be to hard to roll out a new clock program to all the Winbox users. > The main point again is it does not create a ntp protocol time server that > can be accessed by IP address from other Winboxs on the private net. > > So I would say this pretty well covers the facilities that are delivered as > part of the base install. None of then are compatible with what is currently > running on the Winboxs in my private LAN behind the FBSD gateway/firewall. > > It is now time to review the ports for a ntp time server. > Does anybody out there know of or use a FBSD time server port? > > Thanks again for all your combined help in this matter. > > Joe > > > > -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Joe & Fhe Barbish > Sent: Saturday, January 12, 2002 8:44 PM > To: FBSD Questions > Subject: ntpd as time server? > > My LAN is full of winboxs? Each one has this TSR pgm socketWatch. > This pgm checks a internet time server and resets the pc time. > Instead of 700 machines hitting the internet time server once a hour, > I would like to setup ntpd to go out to the internet time server > once a hour for a update to the FBSD machine and them have my > windows LAN boxes get the time from FBSD time server. > I could not find anything in the ntpd man page that talks about > setting up ntpd as a time server to service time requests from > other machines. What I read is that ntpd will broadcast the time > down the LAN network for any listening clients to pick and user > the time info. The win SocketWatch pgm does not work that way. > Is ntpd the wrong software product for what I want to do? > Does anybody know of something better suited? > > Thanks > Joe > > > > > > > > > > > > > My LAN is full of winboxs? Each one has this TSR pgm socketWatch. > This pgm checks a internet time server and resets the pc time. > Instead of 700 machines hitting the internet time server once a hour, > I would like to setup ntpd to go out to the internet time server > once a hour for a update to the FBSD machine and them have my > windows LAN boxes get the time from FBSD time server. > I could not find anything in the ntpd man page that talks about > setting up ntpd as a time server to service time requests from > other machines. What I read is that ntpd will broadcast the time > down the LAN network for any listening clients to pick and user > the time info. The win SocketWatch pgm does not work that way. > Is ntpd the wrong software product for what I want to do? > Does anybody know of something better suited? > > Thanks > Joe > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message