On Sun, Mar 02, 2003 at 08:08:32PM -0500, John Lowell wrote: > > > Well, Jeffrey, we get to the heart of the matter! I'd been advised to > turn off the firewall on both machines with the command "service > iptables off" when the right command is service iptables stop"!! What a > difference that makes: I'm now able to mount /mnt/192.168.1.100 from the > client machine that way without difficulty! Excellent, so now we know where the problem is. > Now, a follow-up question for you: Now that I know for certain that the > firewall is the problem here, what port number do I give the firewall > configuration program to ensure that NFS communication is enabled. Would > I be right to assume 2049? I haven't done much work with NFS through a firewall, the boxes I have running nfs are behind a firewall on a trusted network so I don't have to deal with the firewall issue. It appears you would have to open port 111, the portmapper and port 2049, where it gets tricky is the mountd port which is handled dynamically by default. There appear to be two ways around this. One, try using the record-rpc portion of netfilter. (You can google on record-rpc and netfilter for more info here). Two, you can start the nfs services with the -p flag for mountd. man rpc.mountd will give more information on that switch. Keep in mind I have tried neither of these, but the information may be enough to get you started. If all else fails post back here and maybe someone else can help since we appear to have narrowed it down to a firewall issue. > > Many thanks to you. Glad to be of help. /jft -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
