On Wed, 2004-06-30 at 12:04, Alvin Oga wrote: > > broadcast 192.168.0.0 > > i assume your laptop ( the other ntp config ) is in this ip# range
The laptop happily loads web pages from the server, and I do all my testing by sshing to it. As per an earlier email: --- zen8100a:~# nmap -sU -p 122-124 -vv whiskas Starting nmap 3.50 ( http://www.insecure.org/nmap/ ) at 2004-06-25 17:03 EST Host whiskas (192.168.0.4) appears to be up ... good. Initiating UDP Scan against whiskas (192.168.0.4) at 17:03 The UDP Scan took 2 seconds to scan 3 ports. Adding open port 123/udp Interesting ports on whiskas (192.168.0.4): PORT STATE SERVICE 122/udp closed smakynet 123/udp open ntp 124/udp closed ansatrader Nmap run completed -- 1 IP address (1 host up) scanned in 2.350 seconds --- so the ntp port is accessible/ open, according to nmap. And: ___ 04-06-30 12:20:47 [EMAIL PROTECTED]:~ $ ifconfig eth0 Link encap:Ethernet HWaddr 00:04:76:4E:40:45 inet addr:192.168.0.211 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:126868 errors:0 dropped:0 overruns:0 frame:0 TX packets:108180 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:53098650 (50.6 MiB) TX bytes:8568141 (8.1 MiB) Interrupt:10 Base address:0xe800 ... > and besides, you need to make sure all your masks etc > are properly configured, including the firewall that > should allow ntp traffic > - your laptop only needs to point to whiskas Well, step one is getting the server running, and it doesn't seem to be. I'll run that test I assume is the one again... : whiskas:~# ntpq -cpe remote refid st t when poll reach delay offset jitter ============================================================================== gen21.ihug.com. .RSTR. 16 u - 64 0 0.000 0.000 4000.00 *LOCAL(0) LOCAL(0) 10 l 262 512 377 0.000 0.000 0.001 192.168.0.0 .BCST. 16 u - 64 0 0.000 0.000 4000.00 Note that tk1.ihug.. resolves the same as gen21.ihug.com.au - they're the same ip address. Given that you've said previously that delay and offsets of zero is bad, the server actually isn't running yet. Is this a correct assesment (to be honest, I'm still not sure)? > ------- > > do the same "ntpdate whiskas" from your laptop and you're done > if you get a non-zero offset I'm guessing I shouldn't be getting that zero offset on the server itself... Thanks heaps Zen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
