* Bernhard Voelker <mail@bernhard-voelker.de> [04-22-14 13:47]:
On 04/22/2014 06:31 PM, Patrick Shanahan wrote:
Well, since I stopped the server firewall, restart nfs, mounted the shares from remote and restarted the firewall, there is no failure. But I will retain this and if it happens again, try.
What I do not understand is how stopping the firewall and then restarting it does not destroy the connection as it apparently thought it was originally supposed to do. And no changes have been made to the server in between nfs working and it not :^( ??? puzzled.
I'm no NFS expert, but as far as I understand "mount -t nfs ..." first tries to resolve the NFS service on the server side by contacting the portmapper. Therefore my (wild) guess is that only NFS is configured in the firewall, but the portmapper is blocked. Once the connection is up, the portmapper is not needed anymore, and you could start the firewall ... and NFS would still be working. Just a guess.
BTW: you can consult your firewall logs - there should be an entry about an connecting attempt to port 111 being blocked.
BTW2: there may even be 2 (or more) firewalls be involved, of course ...
In "BTW2", disabling *one* and suceeding would appear to disprove? Firewall logs from the server show access from 192.168.1.10 on dpt=111 to 192.168.1.3 dropped until I stopped the firewall and accessed the shares. Upon restarting the firewall access is allowed ??? No other changes were made on the server, 192.168.1.3, before or after problem occurred. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org