Re: [leaf-user] dachstein NTP Internal Time Server - Up and running

2003-03-17 Thread Charles Steinkuehler
William Brinkman wrote: All, I put the NTP rpm in my mandrake 9.0 linux box. Set the ntp.conf server to 192.168.1.254 (firewall address). Inserted a /etc/ntp.drift and put a 1 in the file. Started the ntpd daemon. Tested out the troubleshooting guide and on the mandrake box tried a: # ntpq -p

Re: [leaf-user] dachstein NTP Internal Time Server - Up and running

2003-03-17 Thread Kevin
: Mon, 17 Mar 2003 07:00:00 -0600 From: Charles Steinkuehler [EMAIL PROTECTED] To: William Brinkman [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: [leaf-user] dachstein NTP Internal Time Server - Up and running William Brinkman wrote: All, I put the NTP rpm in my mandrake 9.0 linux box

Re: [leaf-user] dachstein NTP Internal Time Server - Up and running

2003-03-17 Thread Charles Steinkuehler
Kevin wrote: I was curious, so I tried to hit my firewall without making any changes to its current state. I used a program call NetLab 1.4, freeware for windows. It has a time snyc function I use to keep my clocks updated. When I hit the main time server that worked through the firewall -

Re: [leaf-user] dachstein NTP Internal Time Server - Up and running

2003-03-16 Thread William Brinkman
All, I put the NTP rpm in my mandrake 9.0 linux box. Set the ntp.conf server to 192.168.1.254 (firewall address). Inserted a /etc/ntp.drift and put a 1 in the file. Started the ntpd daemon. Tested out the troubleshooting guide and on the mandrake box tried a: # ntpq -p 192.168.1.254 The