Mounting Directory - Connection Refused

Question

I am trying to mount a Directory from my server to my local machine. This is because I want to edit the directory and execute the files without having the manually push the files to the server after each edit.

I am using NFS and currently getting: 'Connection refused' when I try to mount from a machine on the same network.

My server ip is 192.168.0.12.
My local machine ip is 192.168.0.2. And in /etc/exports I have:

/mnt/export 192.168.0.0/24(rw,async,no_subtree_check)
/mnt/export *(rw)

where /mnt/export is the directory I want to mount and I have chmod 777 -r the directory

On my local machine I execute this command:

mount 192.168.0.12:/mnt/export /Desktop/tes

But get this error:

can't mount /mnt/export from 192.168.0.12 onto /Desktop/tes:
Connection refused

Does anyone have any idea to where I am going wrong?

Answer 1

You can test some of this from the client side. rpcinfo is useful to tell you if rpc calls are making it to the server processes, then you can check mountd specifically, and lastly, showmount will ask the server what volumes are exported:

$ rpcinfo -p nfsserv103 | cut -c30- | sort -u
 mountd
 nfs
 nlockmgr
 portmapper
 rquotad
 status

$ rpcinfo -u nfsserv103 mountd
program 100005 version 1 ready and waiting
program 100005 version 2 ready and waiting
program 100005 version 3 ready and waiting

$ showmount -e nfsserv103 
Export list for nfsserv103:
/                     10.221.253.101,10.221.252.101,10.221.253.100,10.221.252.100
/mnt_foo/bar         (everyone)

(note that "cut" in the first command was just to make the output more concise. you can drop off everything but the first command.)

Answer 2

I had this problem on a machine running a standard Ubuntu 14.04 install.

The connection refused message can be misleading: It turns out that all that was required was to install the nfs-common package.

Answer 3

A firewall is preventing the client from reaching the server. At this stage, you can't know whether NFS is configured properly (so it may well be): the client can't even see that there is an NFS server.

The most likely location for a firewall is the server. Check that it allows incoming connections on port 111 (rpc) and 2049 (nfs). On a Linux machine, run iptables -nvL as root to see the port blocking configuration.

If you don't know where the firewall is, you can locate it by running tcptraceroute 192.168.0.12 111 (or 2049, if it's the nfs port that's blocked). But given that the machines are in the same subnet, there's probably a direct connection, so it's the server (or, less likely, the client) that's blocking connections.

Oh, and don't chmod 777. That never solves anything, and usually breaks something. If the error isn't “permission denied”, the solution isn't chmod; and if the error is “permission denied”, the solution may be chmod but not 777.

Answer 4

execute this:

#on the server new

yum -y install nfs-utils

mkdir /var/mnt

chmod -R 755 /var/mnt

chown nfsnobody:nfsnobody /var/mnt

#edit vim /etc/exports

/var/mnt IP_OLD_SERVER(rw,sync,no_root_squash,no_all_squash)

#execute

systemctl restart nfs-server

systemctl restart rpcbind

systemctl restart nfs-lock

systemctl restart nfs-idmap

systemctl disable firewalld

#on the old server

yum -y install nfs-utils

mkdir -p /mnt/paste

#execute

systemctl restart nfs-server

systemctl restart rpcbind

systemctl restart nfs-lock

systemctl restart nfs-idmap

mount -t nfs IP_NEW_SERVER:/var/mnt /mnt/paste/

Answer 5

**Just give ✔️✔️✔️

Systemctl restart nfs-server

=This will restart the nfs-server not other nfs.

Not the ✖️✖️✖️ Systemctl restart nfs

Answer 6

Have a look into /etc/hosts on the server. Some systems (ubuntu) insert a silly entry for your chosen hostname, if dhcp was used during installation.

127.0.1.1   klaas.somewhere.de  klaas

Replace 127.0.1.1 with the real IP and restart the nfsserver.

Answer 7

This is what worked for me.

#server ip is 192.168.10.20
mkdir /home/servershare
mount -t nfs 192.168.10.20:/nfs/sharefolder /home/servershare -o nolock,rw