No connection NFS on Synology

netsaver

New Member
Dec 26, 2023
2
0
1
I am running a synology NAS on 192.168.0.100 with NFS activated.
Share "proxmox" has been set on synology with user rights R/W.
It is visible to * with NFSv4.1 active. (I have tried 3.0 before, same results)

The NFS Share can be found and accessed from local Mac computers.

Any help is appreciated.

nmap from within Proxmox PVE host can ping synology and will find that NFS service is active on synology:

Code:
root@pvel:~# nmap -v 192.168.0.100
Starting Nmap 7.93 ( https://nmap.org)
at 2023-12-26 15:00 CET
Initiating ARP Ping Scan at 15:00
Scanning 192.168.0.100 [1 port]
Completed ARP Ping
Scan at 15:00, 0.03s elapsed (1 total hosts)
Initiating Parallel DNS
resolution of 1 host. at 15:00
Completed Parallel DNS resolution of 1 host. at 15:00, 0.00s elapsed
Initiating SYN Stealth Scan at 15:00
Scanning DEATHSTAR.fritz.box (192.168.0.100) [1000 ports]
Discovered open port 1723/tcp on
192.168.0.100
Discovered open port 443/tcp on 192.168.0.100
Discovered open port 53/tcp on 192.168.0.100
Discovered open port 80/tcp on 192.168.0.100
Discovered open port 445/tcp on 192.168.0.100
Discovered open port 554/tcp on 192.168.0.100
Discovered open port 111/tcp on 192.168.0.100
Discovered open port 21/tcp on 192. 168.0.100
Discovered open port 139/tcp on 192. 168.0.100
Discovered open port 3261/tcp on 192. 168. 0.100
Discovered open port 1935/tcp on 192. 168. 0.100
Discovered open port 3260/tcp on 192. 168. 0. 100
Discovered open port 3493/tcp on 192. 168. 0.100
Discovered open port 548/tcp on 192.168.0.100
Discovered open port 873/tcp on 192.168.0.100
Discovered open port 4045/tep on 192.168.0.100
Discovered open port 5001/tcp on 192.168.0.100
Discovered open port 5000/tcp on 192.168.0.100
Discovered open port 8083/tcp on 192.168.0.100
Discovered open port 9999/tcp on 192.168.0.100
Discovered open port 2049/tcp on 192.168.0.100
Discovered open port 5566/tcp on 192.168.0.100
Discovered open port 8084/tcp on 192.168.0.100
Discovered open port 5357/tcp on 192.168.0.100
Completed SYN Stealth Scan at 15:00, 1.12s elapsed
(1000 total ports)
Nmap scan report for DEATHSTAR.fritz.box (192.168.0.100)
Host is up (0.00083s latency).
Not shown: 976 closed tcp ports (reset)
PORT STATE SERVICE
21/tcp open Etp
53/tcp open domain
80/tcp open http
111/tcp open rpcbind
139/tcp open netbios-ssn
443/tcp open https
445/tcp open microsoft-ds
548/tcp open afp
554/tcp open rtsp
873/tcp open rsync
1723/tcp open pptp
1935/tcp open rtmp
2049/tcp open nfs
3260/tcp open iscsi
3261/tcp open winshadow
3493/tcp open nut
4045/tcp open lockd
5000/tcp open upnp
5001/tep open commplex-link
5357/tcp open wsdapi
5566/tep open westec-connect
8083/tcp open us-srv
8084/tcp open websnp
9999/tep open abyss
MAC Address: 00:11:32:C5:EF:2E (Synology Incorporated)
Read data files from: /us/bin/../share/nmap
Nmap done: 1 IP address (1 host up) scanned
in 1.26 seconds
Raw packets sent: 1052 (46.272KB) Revd: 1018 (40.872KB)

However:

Code:
showmout -e 192.168.0.100
prc mount export: RPC: Unable to receive; errno = No route to host

and

Code:
rpcinfo -p 192.168.0.100
192.168.0.100: RPC: Remote system error - No route to host
 
Hi,

I would re-check the NFS configuration on the Synology NAS. And ensure that the export settings are correctly configured and that your Proxmox Node's IP address is either explicitly allowed or not restricted.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!