nfsd/portmapper and iptables on Linux 4

Ben Ransom bransom at ucdavis.edu
Thu Mar 10 23:28:32 UTC 2005


Cool, thanks a lot.
Similar question now tho ...I see that ypbind on clients also cannot find 
ypserv on the Redhat 4 machine (again, it is the firewall blocking 
ports).   Is there a similar solution for this?  (or dissimilar, i don't 
much care :)  )
-Ben

At 03:21 PM 3/10/2005 -0500, you wrote:
>Yes. I know this problem well :) There are a couple of RPC services in 
>addition to portmapper and nfs (rquotad and mountd) used by NFS that bind 
>to a random port at startup.
>
>The solution is to add the ports to your /etc/services file such as the 
>following:
>rquotad 950/tcp
>rquotad 950/udp
>mount 951/tcp
>mount 951/udp
>
>Restart nfs, and those two services will bind to the ports specified. Just 
>add those ports to your firewall rules and you should be in business.
>
>
>I hope that helps.
>
>
>Thanks,
>
>
>--
>--
>James Cooley
>Sr. Systems Analyst
>Information Technology
>Florida Tech
>321-674-7999
>jcooley at it.fit.edu
>
>
>
>
>
>
>
>Ben Ransom wrote:
>
>>I've just put up a Redhat 4 system (call it nfsServer) and am unable to 
>>nfs mount file systems from it on other machines ...unless I turn off 
>>iptables on nfsServer.
>>
>>I think the problem is the client is unable to see portmapper on 
>>nfsServer. In the past I've opened udp ports 111 and 2049 in iptables but 
>>this doesn't do the trick with the Redhat4 box. Note, I had SELinux 
>>turned on but have disabled it for now.
>>
>>Any suggestions?
>>Thanks,
>>-Ben
>
>--
>redhat-list mailing list
>unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
>https://www.redhat.com/mailman/listinfo/redhat-list




More information about the redhat-list mailing list