To: Paladin2
I finally figured it out. The resolv.conf file was missing, so the client couldn't find its servers. The solution didn't immediately jump out at me, because I was logged into the laptop remotely (via ssh). So, I knew the networking was up, but didn't think about checking name resolution until I'd beat my head against the wall for a while.
54 posted on
01/02/2006 12:28:38 PM PST by
zeugma
(Warning: Self-referential object does not reference itself.)
To: zeugma
I don't have any *nix computers running FAH - they are even slower machines than the ones that are running FAH.
"The resolv.conf file resides in the /etc directory and contains the IPs of domain name servers that you will probably need if you are going to do anything on the internet! You can think of a domain name server as a hugh [sic!] automated phone book which gives you back a number (an IP) when you send it a name." - 'splains everything
55 posted on
01/02/2006 12:39:03 PM PST by
Paladin2
(If the political indictment's from Fitz, the jury always acquits.)
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson