retrace all the steps
look at the exports list
look at perms at the mount point itself. (is it still mounted ?)
did you make the mounts permanently in /etc/fstab?
I restarted both client and host and everything looks ok. I checked the settings and they are good.
Everything is working again. Maybe the DiskStation needed some time…?
The permissions of the guest and the permissions of the NFS settings, do they need to be the same? All logins to the shares are mapped to the guest account as mentioned yesterday.
Synology usually applies NFS permission changes immediately and doesn’t need a restart.
If the client was buffering anything then restarting it would have effected the most change.
Blockquote
ChuckPaTeam Member
On my LAN, because all machines are mine, I use the wildcard * host IP specification.
It makes life easier. “Set & Forget”
I do the same on my Synology box - use the * wildcard for Hostname or IP, but I constantly get a warning from the Synology Security audit saying that is a vulnerability. All of the hosts on my LAN are my own, so it shouldn’t be a problem, but yesterday I tried to clean it up by limiting the address.
I first input the IP address of my server (192.168.1.60) - when I did that my Plex server was unable to play any of my videos. I then tried to include the whole LAN subnet by using 192.168.1.60/255.255.255.0 but that didn’t work either.
Any Idea what I am doing wrong here? Thanks!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
