The /etc/hosts file on the server was the problem.
I've fixed it and got the client working.
Thanks for everyone's help.
    Doug

Old /etc/hosts from the server (oak) which was broken:
127.0.0.1  Oak  localhost.localdomain localhost
192.168.1.1  fw fw.basement.local
192.168.1.2  oak oak.basement.local
192.168.1.3  dot dot.basement.local
192.168.1.4  maple maple.basement.local
192.168.1.100  HP4050N HP4050N.basement.local

New /etc/hosts on the server (oak) which works:

127.0.0.1 localhost
192.168.1.1 fw fw.basement.local
192.168.1.2 oak oak.basement.local
192.168.1.3 dot dot.basement.local
192.168.1.4 maple maple.basement.local
192.168.1.100 HP4050N HP4050N.basement.local




Jan Harkes wrote:

> On Wed, Jun 14, 2000 at 09:38:28AM -0400, Dr. Douglas C. MacKenzie wrote:
> > I've attached as much log data as I could find.
> > After the failed connect, the server seems to still be alive.
> > I can log into venus running on the server and edit files in the coda
> > directory.
>
> What is the ip-address associated with your server in /etc/hosts?
> It should definitely _not_ be 127.0.0.1, but an address that the
> non-local client can connect to.
>
> If the ip-address was wrong, you need to regenerate the vldb and vrdb
> files on the server after correcting the /etc/hosts file and restarting
> the server. (bldvldb.sh; volutil makevrdb /vice/vol/VRList)
>
> Jan