I have a NFS network which looks like this:
The server is 192.168.1.3, the client is 192.168.1.4
- the /etc/exports on the server contains:
/scoop *(rw,sync)
- the /etc/hosts on server contains:
127.0.0.1 CASA1localhost.localdomain localhost
192.168.1.4 CASA2
- the /etc/hosts.allow and /etc/hosts.deny on the server and client are all
blank!!!!
- the /etc/hosts on client contains:
127.0.0.1 CASA2 localhost.localdomain localhost
192.168.1.3 CASA1
When I go to client and give
#mount 192.168.1.3:/scoop /mnt/1
it works well and I can use the /mnt/1 directory in read-write mode
Ok by now. I give on client
#umount /mnt/1
I give on server
#service nfs restart
I give on client:
#mount 192.168.1.3:/scoop /mnt/1
I receive error: connection failed: the server is down
>From now one, no mater how many times I restart the nfs services on server,
the client tell's me the server is down.
If I rboot the server Linux then all will work fine again (I can mount all
stuff untill I need to restart nfs services which forces me to reboot the
server linux station)
That's a wierd problem. I'm using Fedora Core 2 on all stations. It can be a
distribution problem.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs