by Vinod Gupt » Mon, 25 Feb 2002 14:03:44
Yes, portmap is running on local machine and nfsd on the remote.
In fact, I had installed RH7.2 on my local machine using bootnet
floppy via NFS exported remote_host:/dir a few minutes back.
What else need to be done on client side?
Thanks for help.
Vinod.
by Francis Litteri » Tue, 26 Feb 2002 11:55:39
> Yes, portmap is running on local machine and nfsd on the remote.
...
> In fact, I had installed RH7.2 on my local machine using bootnet
> floppy via NFS exported remote_host:/dir a few minutes back.
Try this on your NFS client machine:
ipchains -F output
ipchains -P output ACCEPT
or if you are using iptables:
iptables -F OUTPUT
iptables -P OUTPUT ACCEPT
--
Francis Litterio
by Robert Myer » Tue, 26 Feb 2002 23:31:54
> > I have added port 2049 (nfs) in the firewall rules in my RH7.2 box
> > but still while trying to mount -t nfs remote_host:/dir /mnt/nfs
> > fails with the error mount: RPC: Timed out
> > Yes, portmap is running on local machine and nfsd on the remote.
> ...
> > In fact, I had installed RH7.2 on my local machine using bootnet
> > floppy via NFS exported remote_host:/dir a few minutes back.
> It sounds like the firewall on the local machine is blocking outbound
> TCP traffic to your NFS server. You can try to open those ports in your
> OUTPUT chain, but you can never know the port number on which mountd is
> listening on the NFS server. It can change every time you boot the NFS
> server (actually, ever time you stop and start the NFS daemons).
> Try this on your NFS client machine:
> ipchains -F output
> ipchains -P output ACCEPT
> or if you are using iptables:
> iptables -F OUTPUT
> iptables -P OUTPUT ACCEPT
> --
One way to tell what's going on is to use "tcpdump -i eth0" to watch what's
going on ( assuming you have tcpdump installed on your machine; if not, it's
worth installing). If you get something like (can't remember the exact
wording) "Port xxxx" unreachable", it's probably because the firewall is
blocking the NFS data stream on input. One (and perhaps the only) way
around this is to tell the blocking machine to accept all input from one or
more machines, regardless of port number, which would mean adding a line to
the ipchains file like
-A -input -s another.ip.address -j ACCEPT
by Francis Litteri » Wed, 27 Feb 2002 02:55:45
>> > I have added port 2049 (nfs) in the firewall rules in my RH7.2 box
>> > but still while trying to mount -t nfs remote_host:/dir /mnt/nfs
>> > fails with the error mount: RPC: Timed out
>> > Yes, portmap is running on local machine and nfsd on the remote.
>> ...
>> > In fact, I had installed RH7.2 on my local machine using bootnet
>> > floppy via NFS exported remote_host:/dir a few minutes back.
>> It sounds like the firewall on the local machine is blocking outbound
>> TCP traffic to your NFS server.
> It's just as likely that the machine on the receiving
> end is blocking the input
so I think the NFS server is not blocking inbound NFS traffic.Quote:> In fact, I had installed RH7.2 on my local machine using bootnet floppy
> via NFS exported remote_host:/dir a few minutes back.
by Robert Mye » Wed, 27 Feb 2002 13:14:45
> > "Francis Litterio" wrote
> >> > I have added port 2049 (nfs) in the firewall rules in my RH7.2 box
> >> > but still while trying to mount -t nfs remote_host:/dir /mnt/nfs
> >> > fails with the error mount: RPC: Timed out
> >> > Yes, portmap is running on local machine and nfsd on the remote.
> ...
> >> > In fact, I had installed RH7.2 on my local machine using bootnet
> >> > floppy via NFS exported remote_host:/dir a few minutes back.
> >> It sounds like the firewall on the local machine is blocking outbound
> >> TCP traffic to your NFS server.
> > It's just as likely that the machine on the receiving
> > end is blocking the input
> Well, the OP said:
> > In fact, I had installed RH7.2 on my local machine using bootnet floppy
> > via NFS exported remote_host:/dir a few minutes back.
> so I think the NFS server is not blocking inbound NFS traffic.
I would have been clearer if I had said "the local machine" rather
than the "machine on the receiving end," since by that I meant the
local machine in the mode of receiving data from the NFS server. In
fact, with tcpdump, I watched my newly-installed OS send out an NFS
request from an arbitrary port, only to refuse the response from the
server on that same port.
Did you really think I meant the remote NFS server wasn't working?
by Francis Litteri » Thu, 28 Feb 2002 02:33:50
Vinod, Robert's suggestion is far better than mine. Sorry for any
confusion.
--
Francis Litterio
1. Can't mount linux NFS volume on Win95
3. NFS: can't mount TCPWare volume
6. Adaptec 3940 UW compatibility?
7. nfs mount problem: mount: can't get address for nfs-server.kauai
10. NFS mount won't mount at boot, but mount -a works fine.
11. 'mount 2nd volume' problem on backups
12. linux NFS server problem - can't ls in the NFS mounted directory.
13. nfs clients don't see other mounts under nfs export