To: zeugma
I think if you add a local & -config to the command to start line and answer the config questions, things will work out. Then for future starts, just use the -local switch.
29 posted on
01/02/2006 10:49:07 AM PST by
Paladin2
(If the political indictment's from Fitz, the jury always acquits.)
To: Paladin2
"-local" & "-config" seperated by spaces.
31 posted on
01/02/2006 10:54:09 AM PST by
Paladin2
(If the political indictment's from Fitz, the jury always acquits.)
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.)
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson