[Techtalk] stupid network problem/new to list

[MMP - Barb Fox]

I didn't see any mention of resolv.conf.  This file should contain a line
which identifies who hp should ask if it doesn't have an IP for a hostname.

nameserver 192.168.100.200

If this is the problem, then you should still be able to talk to machines
on the internet by IP address, just not by name. After making this
change, then you should be able to get anywhere by name.

Barb Fox
mmp_fox at bellsouth.net



>"hp" RH9 client that is unable to go online, but can communicate to
>box b (ping, ssh)
>"lap" osx client that is able to go online
>
>pi: /etc/hosts
>127.0.0.1       localhost.localdomain   localhost
>192.168.100.200 pi.kewlnet      pi
>192.168.100.201 lap.kewlnet     lap
>192.168.100.202 hp.kewlnet      hp
>
>hp: /etc/hosts
>127.0.0.1       localhost.localdomain   localhost
>192.168.100.202 hp.kewlnet      hp
>192.168.100.200 pi.kewlnet      pi
>
>lap: mac os x stuff
>
>pi: /etc/sysconfig/network
>NETWORKING=yes
>HOSTNAME=localhost.localdomain
>
>hp: /etc/sysconfig/network
>NETWORKING=yes
>HOSTNAME=localhost.localdomain
>GATEWAYDEV=eth0
>
>lap: mac osx stuff
>
>Pi has ipforwarding enabled.
>All boxes have assigned ip addresses.  The clients have pi's  ip
>address as the default gateway address.  They all have the correct
>sub-addresses.
>
>The question:
>ack ack ack! What gives? It seems that hp can't resolve addresses, but
>why? why why why?  Of course, hp is the one I built for my man and
>he's bummed that he can't use the box I built for him to go online.
>argh..
>
>Any help is more than appreciated,
>Jere
>_______________________________________________
>Techtalk mailing list
>Techtalk at linuxchix.org
>http://mailman.linuxchix.org/mailman/listinfo/techtalk