NFS problem
I'm trying to set up an NFS file server on one of the boxes on my LAN
and have gotten stuck. On the server, I used system-config-nfs to create the following /etc/exports file: /home/magnusg/music 192.168.1.11(rw,sync) 192.168.1.12(rw,sync) 192.168.1.13(rw,sync) to allow the other three boxes r/w access to the directory /home/magnusg/music on the server (192.168.1.14). Also on the server, I used system-config-services to start nfs and nfslock on run levels 3 and 5. Then I checked NFS4 on the firewall configuration widget system-config-firewall to open tcp and udp ports 2049. Then I rebooted the server. On one of the clients I then did (as root): mkdir /mnt/PuteF mount 192.168.1.14:/home/magnusg/music /mnt/PuteF and got the error message: mount: mount to NFS server '192.168.1.14' failed: System Error: No route to host I'm guessing I need to open more ports, but which ones and where? The four boxes are connected to a Linksys router. Thanks for the help! --Jerry -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list |
NFS problem
On Monday 24 March 2008 00:43:44 Gerhard Magnus wrote:
> I'm trying to set up an NFS file server on one of the boxes on my LAN > and have gotten stuck. On the server, I used system-config-nfs to create > the following /etc/exports file: > > /home/magnusg/music 192.168.1.11(rw,sync) 192.168.1.12(rw,sync) > 192.168.1.13(rw,sync) > > to allow the other three boxes r/w access to the > directory /home/magnusg/music on the server (192.168.1.14). > > Also on the server, I used system-config-services to start nfs and > nfslock on run levels 3 and 5. Then I checked NFS4 on the firewall > configuration widget system-config-firewall to open tcp and udp ports > 2049. Then I rebooted the server. > > On one of the clients I then did (as root): > > mkdir /mnt/PuteF > mount 192.168.1.14:/home/magnusg/music /mnt/PuteF > > and got the error message: > mount: mount to NFS server '192.168.1.14' failed: System Error: No route > to host > > I'm guessing I need to open more ports, but which ones and where? The > four boxes are connected to a Linksys router. > > Thanks for the help! --Jerry Hi Try turning your firewall off completely for a while - "service iptables stop" or "service ip6tables stop" will do it from the shell. I don't bother with firewalls on my internal network machines, but then my kids are only young! If turning it off makes nfs work then turn it back on using service iptables start and send the output from service iptables status to the list. N -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list |
NFS problem
On Mon, 2008-03-24 at 10:38 -0600, Aaron Konstam wrote:
> On Sun, 2008-03-23 at 17:43 -0700, Gerhard Magnus wrote: > > I'm trying to set up an NFS file server on one of the boxes on my LAN > > and have gotten stuck. On the server, I used system-config-nfs to create > > the following /etc/exports file: > > > > /home/magnusg/music 192.168.1.11(rw,sync) 192.168.1.12(rw,sync) > > 192.168.1.13(rw,sync) > > > > to allow the other three boxes r/w access to the > > directory /home/magnusg/music on the server (192.168.1.14). > > > > Also on the server, I used system-config-services to start nfs and > > nfslock on run levels 3 and 5. Then I checked NFS4 on the firewall > > configuration widget system-config-firewall to open tcp and udp ports > > 2049. Then I rebooted the server. > > > > On one of the clients I then did (as root): > > > > mkdir /mnt/PuteF > > mount 192.168.1.14:/home/magnusg/music /mnt/PuteF > > > > and got the error message: > > mount: mount to NFS server '192.168.1.14' failed: System Error: No route > > to host > > > > I'm guessing I need to open more ports, but which ones and where? The > > four boxes are connected to a Linksys router. > > > No route to host sounds more like a connection problem. You can ssh between the machines? > -- ssh works fine. I've been googling this problem and found that other people have had it and it may be a serious bug. Could it be that NFS doesn't work in fedora and that everybody uses samba anyway? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list |
NFS problem
On Sun, 2008-03-23 at 17:43 -0700, Gerhard Magnus wrote:
> I'm trying to set up an NFS file server on one of the boxes on my LAN > and have gotten stuck. On the server, I used system-config-nfs to create > the following /etc/exports file: > > /home/magnusg/music 192.168.1.11(rw,sync) 192.168.1.12(rw,sync) > 192.168.1.13(rw,sync) > > to allow the other three boxes r/w access to the > directory /home/magnusg/music on the server (192.168.1.14). > > Also on the server, I used system-config-services to start nfs and > nfslock on run levels 3 and 5. Then I checked NFS4 on the firewall > configuration widget system-config-firewall to open tcp and udp ports > 2049. Then I rebooted the server. > > On one of the clients I then did (as root): > > mkdir /mnt/PuteF > mount 192.168.1.14:/home/magnusg/music /mnt/PuteF > > and got the error message: > mount: mount to NFS server '192.168.1.14' failed: System Error: No route > to host > > I'm guessing I need to open more ports, but which ones and where? The > four boxes are connected to a Linksys router. > > Thanks for the help! --Jerry No route to host sounds more like a connection problem. You can ssh between the machines? -- ================================================== ===================== All right, you degenerates! I want this place evacuated in 20 seconds! ================================================== ===================== Aaron Konstam telephone: (210) 656-0355 e-mail: akonstam@sbcglobal.net -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list |
NFS problem
Gerhard Magnus wrote:
On Mon, 2008-03-24 at 10:38 -0600, Aaron Konstam wrote: No route to host sounds more like a connection problem. You can ssh between the machines? -- ssh works fine. I've been googling this problem and found that other people have had it and it may be a serious bug. Could it be that NFS doesn't work in fedora and that everybody uses samba anyway? Nope, NFS works fine in FC8, both the default kernel, and a number of the upgrade kernels, no one in their right mind uses SAMBA within a group of Linux/Unix machines, Samba is typically only used when exporting Linux/Unix disk to machines that don't have NFS support. "no route to host" *IS* a connection problem, run the commands "netstat -r" and "ifconfig -a" on both the server and client machine, and return the output. Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list |
NFS problem
On Mon, 24 Mar 2008 07:51:26 -0700
Gerhard Magnus <magnus@agora.rdrop.com> wrote: > Could it be that NFS > doesn't work in fedora and that everybody uses samba anyway? No, it couldn't be. I use and have used NFS on every Fedora release up to and including F8 without difficulty. And I don't use Samba at all. -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list |
NFS problem
On Mon, 2008-03-24 at 12:55 -0500, Roger Heflin wrote:
> Gerhard Magnus wrote: > > On Mon, 2008-03-24 at 10:38 -0600, Aaron Konstam wrote: > > >> No route to host sounds more like a connection problem. You can ssh between the machines? > >> -- > > ssh works fine. I've been googling this problem and found that other > > people have had it and it may be a serious bug. Could it be that NFS > > doesn't work in fedora and that everybody uses samba anyway? > > > > Nope, NFS works fine in FC8, both the default kernel, and a number of the > upgrade kernels, no one in their right mind uses SAMBA within a group of > Linux/Unix machines, Samba is typically only used when exporting Linux/Unix disk > to machines that don't have NFS support. > > "no route to host" *IS* a connection problem, run the commands "netstat -r" and > "ifconfig -a" on both the server and client machine, and return the output. > > Roger > OK... Here's the server: magnusg@PuteF Mon Mar 24 11:22:24 [264] ~ $ netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 link-local * 255.255.0.0 U 0 0 0 eth0 default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 magnusg@PuteF Mon Mar 24 11:24:27 [265] ~ $ ifconfig -a eth0 Link encap:Ethernet HWaddr 00:16:76:C2:73:01 inet addr:192.168.1.14 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::216:76ff:fec2:7301/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:50516340 errors:0 dropped:0 overruns:0 frame:0 TX packets:25841001 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:3951842179 (3.6 GiB) TX bytes:1853560016 (1.7 GiB) Base address:0x20e0 Memory:e0300000-e0320000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1665 errors:0 dropped:0 overruns:0 frame:0 TX packets:1665 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1492676 (1.4 MiB) TX bytes:1492676 (1.4 MiB) ...and the client: magnusg@PuteB Mon Mar 24 11:26:53 [564] ~ $ netstat -r Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 * 255.255.255.0 U 0 0 0 eth0 192.168.122.0 * 255.255.255.0 U 0 0 0 virbr0 link-local * 255.255.0.0 U 0 0 0 eth0 default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 magnusg@PuteB Mon Mar 24 11:27:03 [565] ~ $ ifconfig -a eth0 Link encap:Ethernet HWaddr 00:13:20:8C:8D:D2 inet addr:192.168.1.13 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::213:20ff:fe8c:8dd2/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:271098 errors:0 dropped:0 overruns:0 frame:0 TX packets:141001 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:386786386 (368.8 MiB) TX bytes:9791269 (9.3 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:334 errors:0 dropped:0 overruns:0 frame:0 TX packets:334 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:36716 (35.8 KiB) TX bytes:36716 (35.8 KiB) virbr0 Link encap:Ethernet HWaddr 06:D4:47:1F:4A:72 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::4d4:47ff:fe1f:4a72/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:29 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:5150 (5.0 KiB) -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list |
NFS problem
On Mon, 2008-03-24 at 06:15 +0000, Nicholas Robinson wrote:
> On Monday 24 March 2008 00:43:44 Gerhard Magnus wrote: > > I'm trying to set up an NFS file server on one of the boxes on my LAN > > and have gotten stuck. On the server, I used system-config-nfs to create > > the following /etc/exports file: > > > > /home/magnusg/music 192.168.1.11(rw,sync) 192.168.1.12(rw,sync) > > 192.168.1.13(rw,sync) > > > > to allow the other three boxes r/w access to the > > directory /home/magnusg/music on the server (192.168.1.14). > > > > Also on the server, I used system-config-services to start nfs and > > nfslock on run levels 3 and 5. Then I checked NFS4 on the firewall > > configuration widget system-config-firewall to open tcp and udp ports > > 2049. Then I rebooted the server. > > > > On one of the clients I then did (as root): > > > > mkdir /mnt/PuteF > > mount 192.168.1.14:/home/magnusg/music /mnt/PuteF > > > > and got the error message: > > mount: mount to NFS server '192.168.1.14' failed: System Error: No route > > to host > > > > I'm guessing I need to open more ports, but which ones and where? The > > four boxes are connected to a Linksys router. > > > > Thanks for the help! --Jerry > > Hi > > Try turning your firewall off completely for a while - "service iptables stop" > or "service ip6tables stop" will do it from the shell. > > I don't bother with firewalls on my internal network machines, but then my > kids are only young! > > If turning it off makes nfs work then turn it back on using service iptables > start and send the output from service iptables status to the list. > > N After executing "service iptables stop" on both server and client I was able to mount the shared directory. After running "service iptables start" on both boxes I am still able to access files in the shared directory from the client. Here's the output of service iptables status on the server (with the firewalls back up): root@PuteF Mon Mar 24 11:30:51 [129] /home/magnusg $ service iptables status Table: filter Chain INPUT (policy ACCEPT) num target prot opt source destination 1 RH-Firewall-1-INPUT all -- 0.0.0.0/0 0.0.0.0/0 Chain FORWARD (policy ACCEPT) num target prot opt source destination 1 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) num target prot opt source destination Chain RH-Firewall-1-INPUT (1 references) num target prot opt source destination 1 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 2 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 255 3 ACCEPT esp -- 0.0.0.0/0 0.0.0.0/0 4 ACCEPT ah -- 0.0.0.0/0 0.0.0.0/0 5 ACCEPT udp -- 0.0.0.0/0 224.0.0.251 udp dpt:5353 6 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:631 7 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:631 8 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 9 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:2049 10 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:2049 11 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 12 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:111 13 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited ...and on the client: root@PuteB Mon Mar 24 11:42:33 [240] /mnt/PuteF/mp3/songs $ service iptables status Table: filter Chain INPUT (policy ACCEPT) num target prot opt source destination 1 RH-Firewall-1-INPUT all -- 0.0.0.0/0 0.0.0.0/0 Chain FORWARD (policy ACCEPT) num target prot opt source destination 1 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) num target prot opt source destination Chain RH-Firewall-1-INPUT (1 references) num target prot opt source destination 1 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 2 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 icmp type 255 3 ACCEPT esp -- 0.0.0.0/0 0.0.0.0/0 4 ACCEPT ah -- 0.0.0.0/0 0.0.0.0/0 5 ACCEPT udp -- 0.0.0.0/0 224.0.0.251 udp dpt:5353 6 ACCEPT udp -- 0.0.0.0/0 0.0.0.0/0 udp dpt:631 7 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:631 8 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED 9 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 10 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited I really want to learn samba eventually but I thought I'd master something simpler first :) -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list |
NFS problem
Gerhard Magnus wrote:
On Mon, 2008-03-24 at 12:55 -0500, Roger Heflin wrote: Gerhard Magnus wrote: On Mon, 2008-03-24 at 10:38 -0600, Aaron Konstam wrote: No route to host sounds more like a connection problem. You can ssh between the machines? -- ssh works fine. I've been googling this problem and found that other people have had it and it may be a serious bug. Could it be that NFS doesn't work in fedora and that everybody uses samba anyway? Nope, NFS works fine in FC8, both the default kernel, and a number of the upgrade kernels, no one in their right mind uses SAMBA within a group of Linux/Unix machines, Samba is typically only used when exporting Linux/Unix disk to machines that don't have NFS support. "no route to host" *IS* a connection problem, run the commands "netstat -r" and "ifconfig -a" on both the server and client machine, and return the output. Roger OK... Here's the server: ...and the client: I don't see anything in either that stands out as wrong, both machines are plugged into the "LAN" ports of the router? Try "arp -a" on both the client and server, and see what returns. If the arp command does not show the other machine, try pinging the other machine and rerun the "arp -a". And can you both ping and ssh both directions? client -> server and server -> client? Roger -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list |
NFS problem
On Mon, 2008-03-24 at 13:49 -0500, Roger Heflin wrote:
> Gerhard Magnus wrote: > > On Mon, 2008-03-24 at 12:55 -0500, Roger Heflin wrote: > >> Gerhard Magnus wrote: > >>> On Mon, 2008-03-24 at 10:38 -0600, Aaron Konstam wrote: > >>>> No route to host sounds more like a connection problem. You can ssh between the machines? > >>>> -- > >>> ssh works fine. I've been googling this problem and found that other > >>> people have had it and it may be a serious bug. Could it be that NFS > >>> doesn't work in fedora and that everybody uses samba anyway? > >>> > >> Nope, NFS works fine in FC8, both the default kernel, and a number of the > >> upgrade kernels, no one in their right mind uses SAMBA within a group of > >> Linux/Unix machines, Samba is typically only used when exporting Linux/Unix disk > >> to machines that don't have NFS support. > >> > >> "no route to host" *IS* a connection problem, run the commands "netstat -r" and > >> "ifconfig -a" on both the server and client machine, and return the output. > >> > >> Roger > >> > > OK... Here's the server: > > > > > > > ...and the client: > > In trying to fix this, I've since run "service iptables stop" on both boxes to shut down the firewalls. Then I was able to mount the shared directory on the client without problems. I started iptables again and can still see the shared directory on the client. > I don't see anything in either that stands out as wrong, both machines are > plugged into the "LAN" ports of the router? yes > > Try "arp -a" on both the client and server, and see what returns. Here's the server: magnusg@PuteF Mon Mar 24 12:04:28 [270] ~ $ arp -a PuteB.SMAssociates.com (192.168.1.13) at 00:13:20:8C:8D:D2 [ether] on eth0 ...and the client: magnusg@PuteB Mon Mar 24 12:11:05 [583] /mnt/PuteF $ arp -a PuteF.SMAssociates.com (192.168.1.14) at 00:16:76:C2:73:01 [ether] on eth0 ? (192.168.1.1) at 00:06:25:09:6C:22 [ether] on eth0 > If the arp command does not show the other machine, try pinging the other > machine and rerun the "arp -a". "arp -a" on the server shows the client, while "arp -a" on the client shows the server. > And can you both ping and ssh both directions? client -> server and server -> > client? yes, both ping and ssh work fine. Is there some other port I need to open to get this to work? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list |
| All times are GMT. The time now is 11:04 AM. |
VBulletin, Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.