Nfs ошибка сети 53

I have a CentOS 8 virtual machine (192.168.10.203) running nfs-server, and I'm trying to mount the share on my Windows 10 Pro x86_64 machine (192.168.10.10) I have installed the "Services for ...

I have a CentOS 8 virtual machine (192.168.10.203) running nfs-server, and I’m trying to mount the share on my Windows 10 Pro x86_64 machine (192.168.10.10) I have installed the «Services for NFS» Windows feature), but when I run mount \<nfs_server_IP>data N:, I keep getting this error:

Network Error — 53

Type ‘NET HELPMSG 53’ for more information.

The message for Network Error 53 is «The network path was not found» but I’m not sure what that means.

This is what my /etc/exports looks like on the CentOS machine:

/data 192.168.10.0/24(rw,sync,root_squash,insecure,anonuid=0,anongid=0)

I’ve also tried with the bare-minimum options:

/data 192.168.10.0/24(rw,sync)

Both the CentOS and Windows 10 machines can ping each other.

I can connect to the NFS server on port 2049

Output of rpcinfo -p localhost run on the NFS machine:

$ rpcinfo -p localhost
       program vers proto   port  service
        100000    4   tcp    111  portmapper
        100000    3   tcp    111  portmapper
        100000    2   tcp    111  portmapper
        100000    4   udp    111  portmapper
        100000    3   udp    111  portmapper
        100000    2   udp    111  portmapper
        100024    1   udp  39181  status
        100024    1   tcp  38357  status
        100005    1   udp  20048  mountd
        100005    1   tcp  20048  mountd  
        100005    2   udp  20048  mountd
        100005    2   tcp  20048  mountd
        100005    3   udp  20048  mountd
        100005    3   tcp  20048  mountd
        100003    3   tcp   2049  nfs
        100003    4   tcp   2049  nfs
        100227    3   tcp   2049  nfs_acl
        100021    1   udp  53482  nlockmgr
        100021    3   udp  53482  nlockmgr
        100021    4   udp  53482  nlockmgr
        100021    1   tcp  39197  nlockmgr
        100021    3   tcp  39197  nlockmgr
        100021    4   tcp  39197  nlockmgr

I have the insecure option in my /etc/exports per «Network Error — 53» while trying to mount NFS share in Windows Server 2008 client. Didn’t work.

I’ve tried disabling the firewalls on both hosts with no results (systemctl disable firewalld && iptables --flush on the CentOS machine, and disabling both Windows Defender Firewalls (public and private network firewalls).

Any ideas?

Источник

I have a CentOS 8 virtual machine (192.168.10.203) running nfs-server, and I’m trying to mount the share on my Windows 10 Pro x86_64 machine (192.168.10.10) I have installed the «Services for NFS» Windows feature), but when I run mount \<nfs_server_IP>data N:, I keep getting this error:

Network Error — 53

Type ‘NET HELPMSG 53’ for more information.

The message for Network Error 53 is «The network path was not found» but I’m not sure what that means.

This is what my /etc/exports looks like on the CentOS machine:

/data 192.168.10.0/24(rw,sync,root_squash,insecure,anonuid=0,anongid=0)

I’ve also tried with the bare-minimum options:

/data 192.168.10.0/24(rw,sync)

Both the CentOS and Windows 10 machines can ping each other.

I can connect to the NFS server on port 2049

Output of rpcinfo -p localhost run on the NFS machine:

$ rpcinfo -p localhost
       program vers proto   port  service
        100000    4   tcp    111  portmapper
        100000    3   tcp    111  portmapper
        100000    2   tcp    111  portmapper
        100000    4   udp    111  portmapper
        100000    3   udp    111  portmapper
        100000    2   udp    111  portmapper
        100024    1   udp  39181  status
        100024    1   tcp  38357  status
        100005    1   udp  20048  mountd
        100005    1   tcp  20048  mountd  
        100005    2   udp  20048  mountd
        100005    2   tcp  20048  mountd
        100005    3   udp  20048  mountd
        100005    3   tcp  20048  mountd
        100003    3   tcp   2049  nfs
        100003    4   tcp   2049  nfs
        100227    3   tcp   2049  nfs_acl
        100021    1   udp  53482  nlockmgr
        100021    3   udp  53482  nlockmgr
        100021    4   udp  53482  nlockmgr
        100021    1   tcp  39197  nlockmgr
        100021    3   tcp  39197  nlockmgr
        100021    4   tcp  39197  nlockmgr

I have the insecure option in my /etc/exports per «Network Error — 53» while trying to mount NFS share in Windows Server 2008 client. Didn’t work.

I’ve tried disabling the firewalls on both hosts with no results (systemctl disable firewalld && iptables --flush on the CentOS machine, and disabling both Windows Defender Firewalls (public and private network firewalls).

Any ideas?

Источник
  • Remove From My Forums

  • Question

  • CentOS | Windows 2008

    I’ve got a CentOS 5.5 server running nfsd. On the Windows side, I’m running Windows Server 2008 R2 Enterprise. I have the «Files Services» server role enabled and both Client for NFS and Server for NFS are on.

    I’m able to successfully connect/mount to the CentOS NFS share from other linux systems but am experiencing errors connecting to it from Windows. When I try to connect, I get the following: 

    C:Usersfooadmin>mount -o anon 10.10.10.10:/share/ z:
Network Error - 53

Type 'NET HELPMSG 53' for more information.

    (IP and share name have been changed to protect the innocent :-) )

    Additional information:

    • I’ve verified low-level network connectivity between the Windows client and the NFS server with telnet (to the NFS on TCP/2049) so I know the port is open. I’ve further confirmed that inbound and outbound firewall ports are present and enabled.
    • I came across a
      Microsoft tech note that suggested changing the «Provider Order» so «NFS Network» is above other items like Microsoft Windows Network. I changed this and restarted the NFS client — no luck.
    • I’ve confirmed that the share folder on the NFS server is readable/writable by all (777)
    • I’ve tried other variations of the mount command like: mount 10.10.10.10:/share/ z: and
      mount 10.10.10.10:/share z: and mount -o anon mtype=hard \10.10.10.10:/share * No luck.
    • As per the command output, I tried typing NET HELPMSG 53 but that doesn’t tell me much. Just «The network path was not found».

    I’m lost on how to proceed with troubleshooting. Any ideas?

Answers

    • Marked as answer by

      Tuesday, September 3, 2013 8:52 AM

Источник
  • Remove From My Forums

  • Question

  • CentOS | Windows 2008

    I’ve got a CentOS 5.5 server running nfsd. On the Windows side, I’m running Windows Server 2008 R2 Enterprise. I have the «Files Services» server role enabled and both Client for NFS and Server for NFS are on.

    I’m able to successfully connect/mount to the CentOS NFS share from other linux systems but am experiencing errors connecting to it from Windows. When I try to connect, I get the following: 

    C:Usersfooadmin>mount -o anon 10.10.10.10:/share/ z:
Network Error - 53

Type 'NET HELPMSG 53' for more information.

    (IP and share name have been changed to protect the innocent :-) )

    Additional information:

    • I’ve verified low-level network connectivity between the Windows client and the NFS server with telnet (to the NFS on TCP/2049) so I know the port is open. I’ve further confirmed that inbound and outbound firewall ports are present and enabled.
    • I came across a
      Microsoft tech note that suggested changing the «Provider Order» so «NFS Network» is above other items like Microsoft Windows Network. I changed this and restarted the NFS client — no luck.
    • I’ve confirmed that the share folder on the NFS server is readable/writable by all (777)
    • I’ve tried other variations of the mount command like: mount 10.10.10.10:/share/ z: and
      mount 10.10.10.10:/share z: and mount -o anon mtype=hard \10.10.10.10:/share * No luck.
    • As per the command output, I tried typing NET HELPMSG 53 but that doesn’t tell me much. Just «The network path was not found».

    I’m lost on how to proceed with troubleshooting. Any ideas?

Answers

    • Marked as answer by

      Tuesday, September 3, 2013 8:52 AM

Источник

Код: Выделить всё

% cat /etc/exports                                                                                         ~
# /etc/exports: the access control list for filesystems which may be exported
#               to NFS clients.  See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes       hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4        gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes  gss/krb5i(rw,sync,no_subtree_check)
#

/video  192.168.0.0/16(rw,root_squash,subtree_check,crossmnt)
% showmount -e localhost                                                                             
Export list for localhost:
/video 192.168.0.0/16

% nfsstat -s                                                                                          ~
Server rpc stats:
calls      badcalls   badauth    badclnt    xdrcall
4571165    0          0          0          0

Server nfs v3:
null         getattr      setattr      lookup       access       readlink
2         0% 8070      0% 0         0% 439       0% 2408      0% 0         0%
read         write        create       mkdir        symlink      mknod
4469992  97% 57711     1% 2         0% 0         0% 0         0% 0         0%
remove       rmdir        rename       link         readdir      readdirplus
30        0% 1         0% 0         0% 0         0% 0         0% 403       0%
fsstat       fsinfo       pathconf     commit
5         0% 2         0% 1         0% 32099     0%

на хосте (линукс) , на конором смонтирована эта шара

Код: Выделить всё

% nfsstat -c                                                                                  ~
Client rpc stats:
calls      retrans    authrefrsh
72440      0          0

Client nfs v3:
null         getattr      setattr      lookup       access       readlink
0         0% 219       0% 0         0% 42        0% 72        0% 0         0%
read         write        create       mkdir        symlink      mknod
72097    99% 0         0% 0         0% 0         0% 0         0% 0         0%
remove       rmdir        rename       link         readdir      readdirplus
0         0% 0         0% 0         0% 0         0% 0         0% 6         0%
fsstat       fsinfo       pathconf     commit
0         0% 2         0% 1         0% 0         0%

с сервером все впорядке, и с клиентами, которые с линуксом, тоже все в порядке

на винде монтирую так

ping с винды на starter тоже идет.

Кстати, я как-то неподумал, брандмауєр, встроеный в виндовс, как-то может помешать работе NFS ?

еще добавлю, не знаю нужно оно или нет, но пользователь rabitsa на сервере, который starter, существует

Код: Выделить всё

[% id rabitsa
uid=526(rabitsa) gid=600(rabica) groups=600(rabica)
Источник

Понравилась статья? Поделить с друзьями:
  • Nginx 502 bad gateway php fpm как исправить
  • Nfs underground 2 ошибка установки
  • Nginx 499 ошибка как исправить
  • Nfs underground 2 ошибка please insert disc 2
  • Nginx 499 error