From: Blichfeldt, Bjarne (Bjarne.Blichfeldt@hp.com)
Date: Thu Jun 27 2002 - 07:31:39 EDT
Many thanks to Peter Stern and Jesper Frank Nemholt for their replies.
It turned out however, that it was a simple routing problem. The new interface was given
an ip adress on the same net as one of the old interfacecards and the netmasks was not
changed to reflect that.
Regards
Bjarne Blichfeldt
Original post :
We have a TRU64 4.0F NFS server, which we have recently upgraded from 2 to 3 network interfaces.
The 3 interfaces each runs on seperate networks, eg. 10.1.1.0 , 20.1.1.0 and 30.1.1.0
The nfs service runs fine on the two "old" interfaces, but the new third interface does not seem
to respond to NFS requests.
The "new" third interface works in all other respects, telnet to/from, ping to/from, traceroute etc., but not as nfs server.
If we try to mount a filesystem which is not exported, we get permission denied, indicating we
have access to mountd on the server.
After the filesystem is exported, the mount request get a time out, indicating that mountd on the
server has accepted the request and handed it off to nfsd which does not listen.
When we do a "rpcinfo -u new-server-interface mount" we get a timeout.
It seems that we somewhere on the server has to configure the new interface.
But where ?
Any hints ?
Thanks
Bjarne Blichfeldt
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:44 EDT