RE: [SLE] mount and an rpc error
Looks wide open??? # iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination -----Original Message----- From: Anders Johansson [mailto:andjoh@rydsbo.net] Sent: Wednesday, October 06, 2004 8:54 AM To: suse-linux-e@suse.com Subject: Re: [SLE] mount and an rpc error On Wednesday, 6 October 2004 16.09, Patrick B. O'Brien wrote:
No doubt, this is the client. I desperatly started all nfs daemons, in hopes of getting rid of of this RPC obstacle.
I never turned on the firewall or messed with the /etc/allow,deny, never had to. What is the firewall daemon?
There is no daemon, but you can check your rules with iptables -L If you get a ton of stuff there, then your firewall is running. If so, you need to either turn it off ("rcSuSEfirewall2 stop" if it's a recent-ish suse version) or make sure port 111 is allowed through it Also check on the server, both firewall rules and /etc/hosts.allow and /etc/hosts.deny to make sure the rules don't block this new client. (Could easily happen, if the RH client is on a different subnet and that subnet is explicitly allowed and nothing else, or if the rules explicitly let through the RH client and nothing else) -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Wednesday, 6 October 2004 20.08, Patrick B. O'Brien wrote:
Looks wide open???
# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination
Chain FORWARD (policy ACCEPT) target prot opt source destination
Chain OUTPUT (policy ACCEPT) target prot opt source destination
Yes it does. So, to sum up portmap runs on the client no firewall on the client no hosts.allow or hosts.deny on the client blocking the server server can serve other clients no firewall on the server blocking this client no hosts.allow or hosts.deny on the server blocking this client Is this right? Then I'm afraid I'm out of ideas. As far as I can see everything is correct and should work I don't suppose you get anything in the system log on either client or server when you try to mount that would shed any light on this?
On Wednesday 06 October 2004 14:08, Patrick B. O'Brien wrote:
Looks wide open???
# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination
Chain FORWARD (policy ACCEPT) target prot opt source destination
Chain OUTPUT (policy ACCEPT) target prot opt source destination
Have you checked /etc/exports on the server to be sure that this client is allowed? Is it in an allowed subnet? Does the user have permissions on the filesystem to be mounted? Does the server have a firewall that might block the connection? This doesn't look like a server error but at this point I don't have any other suggestions. Jeff
participants (3)
-
Anders Johansson -
Jeffrey Laramie -
Patrick B. O'Brien