The problem was due to a duplex mismatch between the two machines.
Both alphas (AS1000A) have DE500 NICs. One is set to 100Mpbs full
duplex, with autonegotiating off, the other had autonegotiating on, but
didn't.
I set the card to full-duplex, fast mode at the SRM prompt:
>>> set ewa_mode fastfd
and also had to append 'speed 200' to the IFCONFIG_0 line in
/etc/rc.config
Thanks to Sean O'Connell for providing all the answers.
Rolf Habing
Original question:
Hello all,
I'm experiencing problems with NFS. Our mail server was getting rather
full. To create more space I had to put part of the folder areas (not
the spool area) onto another server. although it seems to work, I keep
on getting erro messages on the client console like this:
Mar 20 10:39:15 basil vmunix: NFS2 server tarragon not responding still
trying
Mar 20 10:39:15 basil vmunix: NFS2 server tarragon ok
Mar 20 10:39:15 basil vmunix: NFS2 server tarragon not responding still
trying
Mar 20 10:39:15 basil vmunix: NFS2 server tarragon ok
Mar 20 10:39:15 basil vmunix: NFS2 server tarragon not responding still
trying
Mar 20 10:39:15 basil vmunix: NFS2 server tarragon ok
Mar 20 10:39:16 basil vmunix: NFS2 server tarragon not responding still
trying
Mar 20 10:39:16 basil vmunix: NFS2 server tarragon ok
Mar 20 10:39:16 basil vmunix: NFS2 server tarragon not responding still
trying
Mar 20 10:39:16 basil vmunix: NFS2 server tarragon ok
The link is made in fstab with:
/usr/users/staff_at_tarragon /usr/users/staff nfs
rw,bg,timeo=10,retrans=30 0 0
and is exported with
/usr/users/staff -rw=basil -root=basil basil
I've tried al sorts of permutations with timeo, retrans, etc. on the
client, as well as changing the
number of tcp/udp daemons on the server, but to no avail.
Any suggestions as to what I might be doing wrong are most welcome.
Thanks,
Rolf Habing
Canterbury Christ Church University College
Received on Tue Mar 21 2000 - 09:03:08 NZST