>> 
>> > > The only thing that I have noticed that is strange is:
>> > >
>> > > [alant@sage alant]$ domainname
>> > > (none)
>> > >
>> > > [alant@sage alant]$ hostname
>> > > sage.my.home
>> 
>> The command domainname refers to a NIS domain, not the DNS command. The
>> hostname command is what you want and is given the correct info.
>> 
>> What happens if you ping sage.my.home from bigdog?
>> 

Checking now, when bigdog is connected to the ISP:

-------------------------------------
[root@bigdog /root]# ping sage  
PING sage.my.home (192.168.1.1) from 192.168.1.2 : 56(84) bytes of data.
64 bytes from sage.my.home (192.168.1.1): icmp_seq=0 ttl=255 time=2.107 msec
64 bytes from sage.my.home (192.168.1.1): icmp_seq=1 ttl=255 time=1.607 msec
64 bytes from sage.my.home (192.168.1.1): icmp_seq=2 ttl=255 time=1.555 msec
64 bytes from sage.my.home (192.168.1.1): icmp_seq=3 ttl=255 time=1.560 msec
64 bytes from sage.my.home (192.168.1.1): icmp_seq=4 ttl=255 time=1.562 msec
-------------------------------------
bigdog is an old 486 and the network is a 10mb. I don't know if those
times are what you would expect.

I will check it when bigdog is not connected to the Internet. If it is a
routing problem, presumably it will show up with ping?

-- 
------------------------------------------------------
Alan L Tyree    [EMAIL PROTECTED]
http://www.law.usyd.edu.au/~alant
Tel: +61 2 4782 2670
Mobile: +61 419 638 170
Fax: +61 2 4782 7092
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug

Reply via email to