I am having trouble with my coda setup. I have installed the latest coda
server on a fresh Debian box w/a 2.4.25 kernel. I have a RedHat 9 client
with the latest coda client. By "latest," I mean 6.0.6 debs & rpms.

I configure the server with vice-setup & the client with venus-setup.

Then I hand-start the server using the recipe printed out by vice-setup:
 - start the auth2 server as: auth2
 - start rpc2portmap as: rpc2portmap
 - start updatesrv as: updatesrv
 - start updateclnt as:  updateclnt -h lambda.csail.mit.edu
 - start the fileserver: startserver &
 - wait until the server is up: tail -f /vice/srv/SrvLog
 - create your root volume: createvol_rep coda:root E0000100 /vicepa

>From my client, I can start up venus. I can see 
    /coda/testserver.coda.cs.cmu.edu/
and can create files in the playground subdir.

>From my client, I can clog as the coda admin on my server. ctokens shows
the cadmin token. I can also create a non-admin user using pdbtool & au.

I can even create a subdirectory remotely. But when I try to run
    cfs sa /coda/lambda.csail.mit.edu/shivers rwlidka
I get
    /coda/lambda.csail.mit.edu: Connection timed out
and my linux console reports this lossage:
    May 11 20:34:48 mongkok kernel: coda_pioctl: Venus returns: -107 for (0xff000001.0x1.0x1)
    May 11 20:34:48 mongkok kernel: coda_pioctl: Venus returns: -107 for (0xff000001.0x1.0x1)
    May 11 20:36:31 mongkok kernel: coda_pioctl: Venus returns: -110 for (0x7f000000.0x1.0x1)
    May 11 20:36:31 mongkok kernel: coda_pioctl: Venus returns: -110 for (0x7f000000.0x1.0x1

Any clues as to what is going wrong?
    -Olin