NFS Automount Stopped Working - System Error: Connection refused

Hi,

With the help of this thread, I got connecting to our NAS over NFS working perfectly.

Direct NAS Reading & Writing - How?

But on Saturday I found out it had stopped working. For no apparent reason, not straight after an update either I don’t think.

When I manually try to mount --verbose:

mount 192.168.100.14:/IHL /mnt/IHL --verbose
mount: no type was given - I’ll assume nfs because of the colon
mount.nfs: timeout set for Tue Jul 6 14:48:32 2010
mount.nfs: text-based options: ‘addr=192.168.100.14’
mount.nfs: Unable to connect to 192.168.100.14:111, errno 111 (Connection refused)

mount.nfs: mount to NFS server ‘192.168.100.14:/IHL’ failed: System Error: Connection refused

Corresponding fstab line that used to work just fine.

192.168.100.14:/IHL /mnt/IHL nfs auto 0 0

For now, I can drop back to Samba but this is a PITA as I can’t open OpenOffice documents and write to them directly on the NAS. The fact smb://192.168.100.14/IHL works proves networking wise we’re cool too.

There is no firewall between this PC and the NAS, the NAS is instructed to allow my PC’s LAN IP full access. OpenSuse’s software firewall has been told to allow NFS Client too.

Why would this setup break out of nowhere?

How can I debug this best? I see nothing relevant in /var/log/messages

How can I get it to work again? A hopeful reboot didn’t do its usual wonders…

Thanks!

Perhaps I should add there’s nothing in /etc/exports - I’ve never needed to access that file to get things going. Also let me add the NAS is working just fine from other machines and from this machine through Samba.

I just now also tried the Yast GUI NFS Client and it also fails to mount these shares.

Well… A reboot of the NAS did resolve this… Note to self: always reboot everything before troubleshooting.

On 2010-07-06 13:56 GMT susemuse wrote:

> > mount.nfs: mount to NFS server ‘192.168.100.14:/IHL’ failed: System
> > Error: Connection refused

> There is no firewall between this PC and the NAS, the NAS is
> instructed to allow my PC’s LAN IP full access. OpenSuse’s software
> firewall has been told to allow NFS Client too.
>
> Why would this setup break out of nowhere?

It has happened to me sometimes. A restart of the nfs server and/or
client and/or firewall solves it. It seems the firewall (server
side, I think) doesn’t learn well the port it has to open for the
connection, and it fails (the port is not fixed, it is negotiated for
each client).

> How can I debug this best? I see nothing relevant in /var/log/messages

Perhaps in the firewal log (server side).

> How can I get it to work again? A hopeful reboot didn’t do its usual
> wonders…

I see you got it working later with a server reboot.


Cheers / Saludos,

Carlos E. R.
(from 11.2 x86_64 “Emerald” GM (Minas Tirith))