On 22/01/2024 09:50, Ralph Corderoy wrote:
Hi Tim,

I have checked through all the relevant network settings on the NAS
and they are reporting the correct IP and Gateway Address.
The NAS may have the equivalent of /etc/exports which can limit the IP
addresses which can mount.

$ mount /media/nas
mount.nfs: access denied by server while mounting
192.168.18.150:/volume1/Data
What is the IP address of the Linux machine?  It is a 192.168.18/24?
‘ip a’ will show the address of each network interface.

‘showmount -e 192.168.18.150’ may be a useful test as well as
‘rpcinfo 192.168.18.150’.

Thank you both for you suggestions

Here the results from a couple of tests

mit@NX1:~$ showmount -e
clnt_create: RPC: Program not registered



mit@NX1:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 3c:97:0e:a2:0f:e8 brd ff:ff:ff:ff:ff:ff
    inet 192.168.18.34/24 brd 192.168.18.255 scope global dynamic noprefixroute enp0s25
       valid_lft 43835sec preferred_lft 43835sec
    inet6 2a0e:cb01:8c:7400:3ed0:59ac:9748:6714/64 scope global dynamic noprefixroute
       valid_lft 477sec preferred_lft 477sec
    inet6 fe80::9e5b:2313:8e2c:e6e/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: wwan0: <BROADCAST,MULTICAST,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 42:ac:92:51:9b:6b brd ff:ff:ff:ff:ff:ff
4: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 6c:88:14:a0:3d:d8 brd ff:ff:ff:ff:ff:ff

Now I can ssh onto the the NAS  (using Putty for linux), I can login but thats as far as I get. SSH is supposed to allow the basic commands like ls, but when I try I get nothing from command it just return the promtp. I have logged is an a normal user and an admin but that makes not difference, also tried sudo in ssh but again made not difference.

I did get this from my laptop

mit@NX1:~$ showmount -e
clnt_create: RPC: Program not registered

and this for the ssh terminal

admin@diskstation:~$ showmount -e
/Volume1/Data 192.168.1.1/24

Is this the /etc/exports we were are looking for?

Finally

it@NX1:~$ rpcinfo 192.168.18.150
   program version netid     address                service    owner
    100000    4    tcp6      ::.0.111               portmapper superuser
    100000    3    tcp6      ::.0.111               portmapper superuser
    100000    4    udp6      ::.0.111               portmapper superuser
    100000    3    udp6      ::.0.111               portmapper superuser
    100000    4    tcp       0.0.0.0.0.111          portmapper superuser
    100000    3    tcp       0.0.0.0.0.111          portmapper superuser
    100000    2    tcp       0.0.0.0.0.111          portmapper superuser
    100000    4    udp       0.0.0.0.0.111          portmapper superuser
    100000    3    udp       0.0.0.0.0.111          portmapper superuser
    100000    2    udp       0.0.0.0.0.111          portmapper superuser
    100000    4    local     /var/run/rpcbind.sock  portmapper superuser
    100000    3    local     /var/run/rpcbind.sock  portmapper superuser
    100005    1    udp       0.0.0.0.3.124          mountd superuser
    100005    1    tcp       0.0.0.0.3.124          mountd superuser
    100005    1    udp6      ::.3.124               mountd superuser
    100005    1    tcp6      ::.3.124               mountd superuser
    100005    2    udp       0.0.0.0.3.124          mountd superuser
    100005    2    tcp       0.0.0.0.3.124          mountd superuser
    100005    2    udp6      ::.3.124               mountd superuser
    100005    2    tcp6      ::.3.124               mountd superuser
    100005    3    udp       0.0.0.0.3.124          mountd superuser
    100005    3    tcp       0.0.0.0.3.124          mountd superuser
    100005    3    udp6      ::.3.124               mountd superuser
    100005    3    tcp6      ::.3.124               mountd superuser
    100003    2    tcp       0.0.0.0.8.1            nfs superuser
    100003    3    tcp       0.0.0.0.8.1            nfs superuser
    100003    4    tcp       0.0.0.0.8.1            nfs superuser
    100003    2    udp       0.0.0.0.8.1            nfs superuser
    100003    3    udp       0.0.0.0.8.1            nfs superuser
    100003    2    tcp6      ::.8.1                 nfs superuser
    100003    3    tcp6      ::.8.1                 nfs superuser
    100003    4    tcp6      ::.8.1                 nfs superuser
    100003    2    udp6      ::.8.1                 nfs superuser
    100003    3    udp6      ::.8.1                 nfs superuser
    100021    1    udp       0.0.0.0.173.221        nlockmgr superuser
    100021    3    udp       0.0.0.0.173.221        nlockmgr superuser
    100021    4    udp       0.0.0.0.173.221        nlockmgr superuser
    100021    1    tcp       0.0.0.0.212.121        nlockmgr superuser
    100021    3    tcp       0.0.0.0.212.121        nlockmgr superuser
    100021    4    tcp       0.0.0.0.212.121        nlockmgr superuser
    100021    1    udp6      ::.173.249             nlockmgr superuser
    100021    3    udp6      ::.173.249             nlockmgr superuser
    100021    4    udp6      ::.173.249             nlockmgr superuser
    100021    1    tcp6      ::.136.35              nlockmgr superuser
    100021    3    tcp6      ::.136.35              nlockmgr superuser
    100021    4    tcp6      ::.136.35              nlockmgr superuser
    100024    1    udp       0.0.0.0.233.7          status superuser
    100024    1    tcp       0.0.0.0.130.229        status superuser
    100024    1    udp6      ::.197.142             status superuser
    100024    1    tcp6      ::.217.84              status superuser

I get a similar response if I run the command in the ssh terminal

Thanks in Advance

Tim H

Hope it makes sense to sombody






--
 Next meeting: Online, Jitsi, Tuesday, 2024-02-06 20:00
 Check to whom you are replying
 Meetings, mailing list, IRC, ...  http://dorset.lug.org.uk
 New thread, don't hijack:  mailto:dorset@mailman.lug.org.uk

Reply via email to