Awesome! It's always a good day when you can solve a networking problem in less than 10 emails :)
On Wed, Dec 18, 2019 at 12:36 PM John Jason Jordan <[email protected]> wrote: > On Wed, 18 Dec 2019 12:18:14 -0800 > Ben Koenig <[email protected]> dijo: > > >You are correct at a high-level. The exact cause of denial is still a > >mystery. > > > >Basically this is all going to be handled by your synology NFS > >settings. You will have a few options that are relevant > >- path you are exporting > >- network you export to > >- hosts you export to > > > >So basically, just confirm that /volume1/Synology (case sensitive) is > >being shared to the 192.168.1.* subnet, that all hosts are allowed to > >mount and that any user is allowed to mount it. Also double check that > >/volume1/Synology/ actually exists. I know you said the path is > >correct, but it only takes a few seconds to double/triple check. > > Hooray, Success! > > I entered 192.168.1.115 in a browser window, which took me to the > Synology login screen. Luckily, it remembered my username and password, > and I logged in. It took a while poking around all the settings, but > finally I found the page where permission was given to my old computer. > I added the new computer to the list, et voilà! The manual mount > command now works. > > Thanks for the advice! > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
