2 macs and a linux on a LAN

[ME]

On Fri, 4 Aug 2000, John F. Kohler wrote:
> I can ping the both macintosh computers from the Linux box.
> I can ping the router (192.168.1.1) from the Linux box.  I
> can ping the router and linux box from one of
> the macintosh machines.

Kewl.

> I cannot get the Netscape Communicator to get past the LAN
> out to the ISP, however. Netscape generates 2 dialog boxes
> which I don't understand.
> 
> First:
> 
> Netcape error...
> 
> Netscape is unable to locate the server sfpl.lib.ca.us.
> Please check the server name and try again.  Using
> previously cached copy instead.

OK

> Second:
> 
> Netscape errorP
> 
> Warning: The following hosts are unknown"
> 
>     home.netscape.com
> home6.netscape.com
> internic.net
> 
> This means that some or all  hosts are unreachable.
> 
> perhaps there is a problem with your name server?

Nameserver seems most likely.

check the file:
/etc/resolve.conf

Mayebe even dump the contents here
it should have your name servers specified in it.
Without this, your linux box may not perform DNS lookups to convert names
into IP addresses.

Format:
/etc/resolve.conf:
---
search sonoma.edu intra.sonoma.edu
nameserver      130.157.2.5
nameserver      130.157.2.3
nameserver      130.157.2.2
nameserver      130.157.2.1
---

This is for my campus. The above shows "search" and two arguements. This
is the default assumed domain. If I type "www" on my web browser, or in a
shell I type 
"telnet www" then the linux box first checks /etc/hosts, then tries to
append "sonoma.edu" to www and then perform a DNS lookup. If all of the
above fail, then netscape takes it upon itself to assume you wanted to go
to www.com or www.www.com...

Could you show us your /etc/resolve.conf?

Your resolve.conf will likelt hve different IP numbers for you name
serversrom your ISP. The above DNS probably won't work for you.

The other choice is that you have set up a SOCKS proxy / fiirewall. This
seems unlikely.

> If your site must use a non-root nameserver, you will
> need to set the $SOCKS_NS environment variable to point
> at the appropriate name server.  It may (or may not)
> be necessary to set this variable or the SOCKS host
> preference, to the IP address of the host inquestion rather
> than its name.
> 
> consult your system administrater
> 
> (OK)
> 
> The problem is, for the LAN in my house, I am the system
> administrator.