I try to connect a Raspberry Pi (*.187, bookworm, rpg) via nfs with a Synologic NAS (130) - without success so far.
When I mount from the client I get the following response:
$ sudo mount -vvv -o vers=3 -t nfs 192.168.66.130:/volume3/folderToShare /mnt/nfs130After hat I can see that the server pretends the shared folder is mounted - but this is not true.And when looking at the tcpdump I see that there is some interaction (not shown here) and at the end there seems to be some repeated request to port 2049 without any reply from the server. Strange: I even can not catch the same packets via tcpdump at the nfs-server side:What could be the reason for this strange behavior and what is wrong?
I have the impression that the mounting runs fine at the server side, but can not be finished because the calls from the client (to port 2049 of the server) are broken and therefor the mounted folder never appears in the client file system.
I am very thankful for hints and ideas about what I do wrong.
When I mount from the client I get the following response:
$ sudo mount -vvv -o vers=3 -t nfs 192.168.66.130:/volume3/folderToShare /mnt/nfs130
Code:
mount.nfs: timeout set for Sun Jun 1 22:07:54 2025mount.nfs: trying text-based options 'vers=3,addr=192.168.66.130'mount.nfs: prog 100003, trying vers=3, prot=6mount.nfs: trying 192.168.66.130 prog 100003 vers 3 prot TCP port 2049mount.nfs: prog 100005, trying vers=3, prot=17mount.nfs: trying 192.168.66.130 prog 100005 vers 3 prot UDP port 892mount.nfs: mount(2): Connection timed outmount.nfs: Connection timed outCode:
$ showmount -aAll mount points on nas:192.168.66.187:/volume3/folderToShareCode:
22:05:55.870199 IP 192.168.66.187.895 > 192.168.66.130.2049: Flags [S], seq 1502963231, win 64240, options [mss 1460,sackOK,TS val 1493570805 ecr 0,nop,wscale 7], length 022:05:56.894186 IP 192.168.66.187.895 > 192.168.66.130.2049: Flags [S], seq 1502963231, win 64240, options [mss 1460,sackOK,TS val 1493571829 ecr 0,nop,wscale 7], length 022:05:57.918186 IP 192.168.66.187.895 > 192.168.66.130.2049: Flags [S], seq 1502963231, win 64240, options [mss 1460,sackOK,TS val 1493572853 ecr 0,nop,wscale 7], length 022:05:58.942185 IP 192.168.66.187.895 > 192.168.66.130.2049: Flags [S], seq 1502963231, win 64240, options [mss 1460,sackOK,TS val 1493573877 ecr 0,nop,wscale 7], length 022:05:59.862277 ARP, Request who-has 192.168.66.187 tell 192.168.66.130, length 4622:05:59.966188 IP 192.168.66.187.895 > 192.168.66.130.2049: Flags [S], seq 1502963231, win 64240, options [mss 1460,sackOK,TS val 1493574901 ecr 0,nop,wscale 7], length 022:06:00.094177 ARP, Request who-has 192.168.66.130 tell 192.168.66.187, length 2822:06:01.982195 IP 192.168.66.187.895 > 192.168.66.130.2049: Flags [S], seq 1502963231, win 64240, options [mss 1460,sackOK,TS val 1493576917 ecr 0,nop,wscale 7], length 022:06:06.238181 IP 192.168.66.187.895 > 192.168.66.130.2049: Flags [S], seq 1502963231, win 64240, options [mss 1460,sackOK,TS val 1493581173 ecr 0,nop,wscale 7], length 022:06:14.430185 IP 192.168.66.187.895 > 192.168.66.130.2049: Flags [S], seq 1502963231, win 64240, options [mss 1460,sackOK,TS val 1493589365 ecr 0,nop,wscale 7], length 0I have the impression that the mounting runs fine at the server side, but can not be finished because the calls from the client (to port 2049 of the server) are broken and therefor the mounted folder never appears in the client file system.
I am very thankful for hints and ideas about what I do wrong.
Statistics: Posted by defi555 — Sun Jun 01, 2025 8:23 pm — Replies 0 — Views 26