Does the client use port 2049? I am not an expert, but I don't think the client can use port 2049. I think that would prevent using the server and the client on the same host.
-----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of James Melin Sent: Tuesday, September 18, 2007 8:42 AM To: [email protected] Subject: NFS, Firewalls and ports Good morning (or evening, depenging) everyone. I am hoping someone can shed some light on something for me... Trying to a read-only NFS export of a directory through the DMZ firewall to a local linux instance. From what I have read, NFSV4 uses port 2049 to make it's connections. Presumable this is for both client and server as I've seen nothing about such a distinction. Both systemsare SLES-10 SP1. When the external firewall rules are set specifically allow port 2049 between the two machines it fails with a "mount server reported tcp not available, falling back to udp" error and then eventually just gives up. When the firewall is set to allow all connections between these two hosts it works. So obviously port 2049 isn't really it, or it isn't all of the answer. So, what am I missing? ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 CONFIDENTIALITY NOTICE: This email from the State of California is for the sole use of the intended recipient and may contain confidential and privileged information. Any unauthorized review or use, including disclosure or distribution, is prohibited. If you are not the intended recipient, please contact the sender and destroy all copies of this email. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
