# Can't access NFS shares after update to ADM 5.1.3.RH72

**URL:** <https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247>\
**Category:** Archived Articles\
**Created:** [June 4, 2026, 11:18pm UTC](https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247 "2026-06-04T23:18:59Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![onkel](https://talk.asustor.com/letter_avatar_proxy/v4/letter/o/71e660/32.png) [@onkel](https://talk.asustor.com/u/onkel)\
**Post date:** [June 4, 2026, 11:18pm UTC](https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247/1 "2026-06-04T23:18:59Z")

</div>

As the title says. I’m on Linux Mint 22.3 and mount shares on my AS1104T via NFS and the prerequisite entries in fstab. Worked liked a charm until I run the recent update to ADM 5.1.3.RH72. My PC can still ping the NAS, but it doesn’t see any exported NFS shares:

```plaintext
showmount -e 192.168.1.3

```

produces an error:

```plaintext
clnt_create: RPC: Unable to receive

```

(couldn’t find much about that error message). I checked the NFS permissions on the NAS and nothing has changed from what I had set before. Any troubleshooting tips would be welcome.

---

<div class="post-metadata">

**Author:** ![onkel](https://talk.asustor.com/letter_avatar_proxy/v4/letter/o/71e660/32.png) [@onkel](https://talk.asustor.com/u/onkel)\
**Post date:** [June 5, 2026, 12:55am UTC](https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247/2 "2026-06-05T00:55:00Z")

</div>

Run rpcinfo on the PC:

```plaintext
rpcinfo -p 192.168.1.3 | grep nfs
192.168.1.3: RPC: Remote system error - Connection refused

```

Then I ssh’d into the NAS and run the following:

```plaintext
 showmount -a
clnt_create: RPC: Unable to receive

nfsstat -s
-sh: nfsstat: not found

cat /proc/mounts | grep nfs
nfsd /proc/fs/nfsd nfsd rw,relatime 0 0

```

Can’t make much sense of this, but seems like NFS is not running properly, although it’s clearly checked in the ‘Sevices’ pane; of the ADM GUI.

Also, I’m able to access SMB shares.

---

<div class="post-metadata">

**Author:** ![damien599901](https://talk.asustor.com/letter_avatar_proxy/v4/letter/d/59ef9b/32.png) [@damien599901](https://talk.asustor.com/u/damien599901)\
**Post date:** [June 5, 2026, 5:55pm UTC](https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247/3 "2026-06-05T17:55:35Z")

</div>

hi

on Linux

```plaintext
nc -zv 192.168.1.3 111

```

you can also try

```plaintext
rpcinfo -t 192.168.1.3 nfs

```

and

```plaintext
rpcinfo -u 192.168.1.3 nfs

```

on NAS via ssh

```plaintext
ps aux | grep rpc

```

and

```plaintext
ps aux | grep nfs

```

=\> do you see this  
rpcbind  
rpc.mountd  
rpc.statd  
nfsd

---

<div class="post-metadata">

**Author:** ![damien599901](https://talk.asustor.com/letter_avatar_proxy/v4/letter/d/59ef9b/32.png) [@damien599901](https://talk.asustor.com/u/damien599901)\
**Post date:** [June 5, 2026, 5:55pm UTC](https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247/4 "2026-06-05T17:55:42Z")

</div>

hi

on Linux

```plaintext
nc -zv 192.168.1.3 111

```

you can also try

```plaintext
rpcinfo -t 192.168.1.3 nfs

```

and

```plaintext
rpcinfo -u 192.168.1.3 nfs

```

on NAS via ssh

```plaintext
ps aux | grep rpc

```

and

```plaintext
ps aux | grep nfs

```

=\> do you see this  
rpcbind  
rpc.mountd  
rpc.statd  
nfsd

---

<div class="post-metadata">

**Author:** ![onkel](https://talk.asustor.com/letter_avatar_proxy/v4/letter/o/71e660/32.png) [@onkel](https://talk.asustor.com/u/onkel)\
**Post date:** [June 5, 2026, 8:51pm UTC](https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247/5 "2026-06-05T20:51:20Z")

</div>

Thanks for the reply. Here’s the output for all of those commands.

TCP failed to connect:

```plaintext
nc: connect to 192.168.1.3 port 111 (tcp) failed: Connection refused

```

No luck with RCP:

```plaintext
192.168.1.3: RPC: Remote system error - Connection refused

```

RPC processes:

```plaintext
   93 root 0:00 [rpc-1]
   94 root 0:00 [rpc-3]
 2137 root 0:00 [rpciod]
31457 Radon 0:00 grep rpc

```

NFS processes:

```plaintext
31571 Radon 0:00 grep nfs

```

It looks like, the necessary processes are running, but a connection can’t be established. The firewall on the NAS is not running, though.

---

<div class="post-metadata">

**Author:** ![onkel](https://talk.asustor.com/letter_avatar_proxy/v4/letter/o/71e660/32.png) [@onkel](https://talk.asustor.com/u/onkel)\
**Post date:** [June 8, 2026, 10:22am UTC](https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247/6 "2026-06-08T10:22:47Z")

</div>

It’s back working.  
Bad thing is, I have no idea why. NFS just started working again last night. A day earlier, I disabled and re-enabled NFS, but that should have taken nearly immediate effect. I’m a bit puzzled.

---

<div class="post-metadata">

**Author:** ![damien599901](https://talk.asustor.com/letter_avatar_proxy/v4/letter/d/59ef9b/32.png) [@damien599901](https://talk.asustor.com/u/damien599901)\
**Post date:** [June 8, 2026, 10:02pm UTC](https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247/7 "2026-06-08T22:02:51Z")

</div>

hi

I’m glad to read that. You could perhaps open a support ticket and attach the health record so they can check if there’s an underlying problem…

---

<div class="post-metadata">

**Author:** ![Revhead](https://talk.asustor.com/letter_avatar_proxy/v4/letter/r/7993a0/32.png) [@Revhead](https://talk.asustor.com/u/Revhead)\
**Post date:** [June 17, 2026, 9:32pm UTC](https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247/8 "2026-06-17T21:32:32Z")

</div>

~~[quote=onkel post\_id=61942 time=1780914167 user\_id=9719]~~  
It’s back working.  
  
Bad thing is, I have no idea why. NFS just started working again last night. A day earlier, I disabled and re-enabled NFS, but that should have taken nearly immediate effect. I’m a bit puzzled.  
[/quote]

I have had nothing but trouble with NFS shares.  
  
After every update I have to reconfigure the share permissions and, as you have discovered, it seems to take a period of time before they become accessible again.  
  
Now I back up system settings before updating ADM and the first thing I do after updating is to restore those settings. This seems to help.  
  
It’s so annoying. I’m thinking of switching to SMB instead . . .

---

<div class="post-metadata">

**Author:** ![damien599901](https://talk.asustor.com/letter_avatar_proxy/v4/letter/d/59ef9b/32.png) [@damien599901](https://talk.asustor.com/u/damien599901)\
**Post date:** [June 18, 2026, 5:52pm UTC](https://talk.asustor.com/t/cant-access-nfs-shares-after-update-to-adm-5-1-3-rh72/45247/9 "2026-06-18T17:52:26Z")

</div>

~~[quote=Revhead post\_id=62028 time=1781731952 user\_id=18236]~~  
~~[quote=onkel post\_id=61942 time=1780914167 user\_id=9719]~~  
It’s back working.  
  
Bad thing is, I have no idea why. NFS just started working again last night. A day earlier, I disabled and re-enabled NFS, but that should have taken nearly immediate effect. I’m a bit puzzled.  
[/quote]

I have had nothing but trouble with NFS shares.  
  
After every update I have to reconfigure the share permissions and, as you have discovered, it seems to take a period of time before they become accessible again.  
  
Now I back up system settings before updating ADM and the first thing I do after updating is to restore those settings. This seems to help.  
  
It’s so annoying. I’m thinking of switching to SMB instead . . .  
[/quote]

hi  
  
  
  
Since multiple users now appear to be experiencing similar symptoms, it may be worth opening a support ticket with ASUSTOR and attaching a Health Record so they can determine whether there is a regression affecting NFS services after certain ADM updates.  
  
  
  
Please keep us informed whether restoring the settings is required after every update or only with specific ADM versions.
