I recently installed a new F8 system, similar to what I had done
previously. The firewall is preventing the export of file systems from
this system. I have NFS trusted, but the problem appears to be with port
111.
If I attempt to mount the F8 system files (with firewall enabled) on
system "B" I receive:
mount -v /dfpc74
mount: Unable to connect to 192.168.7.4:111, errno 113 (No route to host)
mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 47097
mount: Unable to connect to 192.168.7.4:47097, errno 113 (No route to host)
Exit 32
With the firewall disabled the mount is successful.
mount -v /dfpc74
mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 2049
mount: trying 192.168.7.4 prog 100005 vers 3 prot udp port 32771
What am I missing in my setup. I work from the command line, so please
reply in a way that is not GUI dependent.
Thanks
don
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
01-05-2008, 07:33 PM
"Mr.Scrooge"
F8, portmap, 111, and NFS failure
Maybe you need to setup a couple of rules using iptables?
--- don fisher <dfisher@as.arizona.edu> wrote:
> I recently installed a new F8 system, similar to what I had done
> previously. The firewall is preventing the export of file systems from
> this system. I have NFS trusted, but the problem appears to be with port
> 111.
>
> If I attempt to mount the F8 system files (with firewall enabled) on
> system "B" I receive:
>
> mount -v /dfpc74
> mount: Unable to connect to 192.168.7.4:111, errno 113 (No route to host)
> mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 47097
> mount: Unable to connect to 192.168.7.4:47097, errno 113 (No route to host)
> Exit 32
>
> With the firewall disabled the mount is successful.
>
> mount -v /dfpc74
> mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 2049
> mount: trying 192.168.7.4 prog 100005 vers 3 prot udp port 32771
>
>
> What am I missing in my setup. I work from the command line, so please
> reply in a way that is not GUI dependent.
>
> Thanks
> don
>
> --
> fedora-list mailing list
> fedora-list@redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
__________________________________________________ __________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
__________________________________________________ __________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
01-05-2008, 07:34 PM
"Amadeus W.M."
F8, portmap, 111, and NFS failure
On Sat, 05 Jan 2008 12:39:16 -0700, don fisher wrote:
> I recently installed a new F8 system, similar to what I had done
> previously. The firewall is preventing the export of file systems from
> this system. I have NFS trusted, but the problem appears to be with port
> 111.
>
> If I attempt to mount the F8 system files (with firewall enabled) on
> system "B" I receive:
>
> mount -v /dfpc74
> mount: Unable to connect to 192.168.7.4:111, errno 113 (No route to
> host) mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 47097
> mount: Unable to connect to 192.168.7.4:47097, errno 113 (No route to
> host) Exit 32
>
> With the firewall disabled the mount is successful.
>
> mount -v /dfpc74
> mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 2049 mount:
> trying 192.168.7.4 prog 100005 vers 3 prot udp port 32771
>
>
> What am I missing in my setup. I work from the command line, so please
> reply in a way that is not GUI dependent.
>
> Thanks
> don
You're missing a message I posted on Jan 1st. Look for "NFS vs the
firewall". Essentially you must force the rpc services to start on
predefined ports by specifying them in /etc/sysconfig/nfs, then open
those ports (udp and tcp) in the firewall besides the nfs port (2049) and
the portmapper (111).
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
01-05-2008, 07:42 PM
don fisher
F8, portmap, 111, and NFS failure
Thanks. Any suggestions on what rules to apply? I tried making 111
available, but the mount still hung. That is why I posted the question.
Thanks for any assistance,
don
Mr.Scrooge wrote:
Maybe you need to setup a couple of rules using iptables?
--- don fisher <dfisher@as.arizona.edu> wrote:
I recently installed a new F8 system, similar to what I had done
previously. The firewall is preventing the export of file systems from
this system. I have NFS trusted, but the problem appears to be with port
111.
If I attempt to mount the F8 system files (with firewall enabled) on
system "B" I receive:
mount -v /dfpc74
mount: Unable to connect to 192.168.7.4:111, errno 113 (No route to host)
mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 47097
mount: Unable to connect to 192.168.7.4:47097, errno 113 (No route to host)
Exit 32
With the firewall disabled the mount is successful.
mount -v /dfpc74
mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 2049
mount: trying 192.168.7.4 prog 100005 vers 3 prot udp port 32771
What am I missing in my setup. I work from the command line, so please
reply in a way that is not GUI dependent.
Thanks
don
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
__________________________________________________ __________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
__________________________________________________ __________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
--
-------------------------------------------------------------------
| Don Fisher dfisher@as.arizona.edu |
| Steward Observatory |
| 933 N. Cherry Ave. VOICE: (520)888-7613 |
| University of Arizona |
| Tucson, AZ 85721 |
-------------------------------------------------------------------
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
01-05-2008, 07:47 PM
John Summerfield
F8, portmap, 111, and NFS failure
don fisher wrote:
Thanks. Any suggestions on what rules to apply? I tried making 111
available, but the mount still hung. That is why I posted the question.
Thanks for any assistance,
don
This topic has been discussed twice, at least, recently on this list.
Please use the archives and/or google.
Mr.Scrooge wrote:
Maybe you need to setup a couple of rules using iptables?
--- don fisher <dfisher@as.arizona.edu> wrote:
I recently installed a new F8 system, similar to what I had done
previously. The firewall is preventing the export of file systems
from this system. I have NFS trusted, but the problem appears to be
with port 111.
If I attempt to mount the F8 system files (with firewall enabled) on
system "B" I receive:
mount -v /dfpc74
mount: Unable to connect to 192.168.7.4:111, errno 113 (No route to
host)
mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 47097
mount: Unable to connect to 192.168.7.4:47097, errno 113 (No route to
host)
Exit 32
With the firewall disabled the mount is successful.
mount -v /dfpc74
mount: trying 192.168.7.4 prog 100003 vers 3 prot tcp port 2049
mount: trying 192.168.7.4 prog 100005 vers 3 prot udp port 32771
What am I missing in my setup. I work from the command line, so
please reply in a way that is not GUI dependent.
F8, portmap, 111, and NFS failure
