The NFS port is 2049. The rpc.portmapper port is 111, and it is involved in NFS mounts. I really don't know the detials of how this should work through a firewall (unlike you, I *do* get the "last word" here, and we wouldn't even try this), but the "RPC" in your failure message is probably the failed Remote Procedure Call to the portmapper. (I assume the 1.2.3.4 part of what you posted is fake and you are using the correct real IP address.)
I'm sorry I can't help you more specifically than this. You're probably going to have to experiment a bit to get this working right, and once you do, it may be worth your posting the details here, since I haven't ever seen this question posed before. At 08:39 PM 1/28/02 -0500, Lonnie Cumberland wrote: >Hello Ray, > >Actually because of the nature of our setup here, w have 2 machines >that need allow for nfs mounting and although my personnal thoughts >are that they too should be behind the firewall completely, >unfortunately I do not get the last word in this. > >Opening port 2049 means that I have added this rule to the >ipfilter.conf file. > >$IPMASQADM portfw -a -P udp -L $EXTERN_IP 2040 -R 192.168.1.16 2049 > >That is strance because the information that I was seeing from nmap >suggested taht the nfs port was udp and on 2049 although I might be >wrong. > >I actually do, from the client "mount 1.2.3.4:/testdir /test" >and after about 3 - 4 minutes I get: > >mount: RPC: Timed out > >does this help to clear things up? > >Do I also need to open udp/tcp port 111? [old stuff deleted] -- ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo Palo Alto, CA [EMAIL PROTECTED] ---------------------------------------------------------------- _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
