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

  • Remove From My Forums

locked

NFS — ошибка 53 при монтировании шары

  • Вопрос

  • Здравствуйте.

    Есть сервер 2008 R2, добавил роль nfs, открываю cmd, пишу mount \172.16.х.химя_папки O:

    Выдаёт — Ошибка сети 53.

    Папка открыта на  NAS Qnap. С ПК под Вин10, делаю тоже самое, подключается и работает, на серверной ОС — нет.

    Куда копать, как решить?

Ответы

  • Всем спасибо, вопрос решен. Проблема была с натом, сделали правило для внутренних адресов.

    • Предложено в качестве ответа

      15 января 2021 г. 10:15

    • Помечено в качестве ответа
      Иван ПродановMicrosoft contingent staff
      15 января 2021 г. 10:46

Источник

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?

Источник

  • #1

I have been looking for a resolution to this issue, but I haven’t come up with much. I used the guide posted on the following site to setup the NFS client on Windows 10:

https://graspingtech.com/mount-nfs-share-windows-10/

I get it all setup, but it never works. I always get a ’53’ error saying that the network path was not found. However it is correct. I have the same NFS share mounted in Ubuntu, and it works fine. It just doesn’t work in Windows. I am not sure what would cause the issue.

Here is my NFS config:

server IP is 192.168.0.24
NFS Share Path is /mnt/Tower
The only option I have enabled is ‘All Directories’
I have ‘Mapall User’ and ‘Mapall Group’ set to a specific user and group that exists on FreeNAS.

On the Windows machine I have installed the NFS client feature and the uid/gid setup in the registry for the user from FreeNAS for the Anonymous GID/UID setting. I have rebooted multiple times since setting that value.

The command I am using in Windows to map the drive is:

mount -o nolock anon \192.168.0.24mntTTower X:

No matter what I do I get «Network Error — 53»

I have tried disabling my firewall on my Windows machine and I get the same error.

As I stated at the beginning, the exact same NFS share is able to be mounted from Ubuntu just fine, so I think it has to be something on Windows, but I am not sure what else to try.

Any assistance would be appreciated. Let me know if there is any info that you need to assist with coming up with a fix.

Thanks in advance!

  • #3

mount -o nolock anon \192.168.0.24mntTTower X:

Just for fun, put the path in quotes or try it without the space (TowerX).

  • #4

I tried quotes and that resulted in the same error. I tried removing the space, but that just resulted in an error saying that i had to provide a drive letter «X:» to be mapped.

  • #5

There is an extra «T» after mnt so it ends up being mntTTower

Maybe a typo but could be a problem as well if you are copy/pasting. It’s simple to look over and could be an issue. Also in the adapter properties make sure that NFS is checked and move it up in the list to the top above the Microsoft Networks.

  • #6

I tried quotes and that resulted in the same error. I tried removing the space, but that just resulted in an error saying that i had to provide a drive letter «X:» to be mapped.

Doh, I see.

  • #7

@nightshade00013 I made the modifications to the network adapter, but it had no effect. Also, the extra «T» was a typo. Still not sure what is causing it to not work like it should.

Mirfster

Mirfster

Doesn’t know what he’s talking about


  • #8

What do you get when you simply use?:

Mount \192.168.0.24mntTower X:

Mirfster

Mirfster

Doesn’t know what he’s talking about


  • #10

@Mirfster , I get the same error when I simplify the command. Also, I did adjust the provider order, but that didn’t have any effect.

Mirfster

Mirfster

Doesn’t know what he’s talking about


  • #11

@Mirfster , I get the same error when I simplify the command. Also, I did adjust the provider order, but that didn’t have any effect.

In all honesty, I truly do not know if a non-enterprise version of Windows does properly support NFS. Not calling the author of the article a liar, just that with MS things tends to change a lot under the hood and what may have worked for v1607, may not hold true for v1703, v1709, etc…

If you have access to an Enterprise version of Windows or a Server Version (2008 R2 should suffice); then maybe try that on a test machine to see if you can connect.

On a side note, is there a driving reason that NFS is needed/required? Just curious…

  • #12

I have tried it from Server 2016 Datacenter Edition and I get the same error.

I am just trying to get everyone moved over to one share type and the users that I have using SMB/CIFS are the most problematic.

Mirfster

Mirfster

Doesn’t know what he’s talking about


  • #13

Hmm, I don’t recall having much of an issue in the past. However, I am running FreeNAS v9.10…

I do have a system that I could try some stuff on, but it is ~2 weeks into seeding a huge backup to CrashPlan and I really really don’t want to mess with it until its done.

BTW, did you ever mention the version you are running?

Источник

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)

Источник

Skip to content

Hi everyone

If you find yourself with such error when you try to map a network drive in NFS;

Network Error – 53

Type ‘NET HELPMSG 53’ for more information

Please know that some tips exist to diagnose the error.

1- Make sure the NFS client is installed on the Windows 10.

2 – Make sure to use that registry fix if the mapping is on a restricted port;

HKLMSoftwareMicrosoftClientforNFSCurrentVersionDefault

UseReservedPorts := 0 (or 1) – DWORD32

3 – Make sure to use that registry fix to match the mapping GID/UID;

HKLMSoftwareMicrosoftClientforNFSCurrentVersionDefault

AnonymousGid := XXXX (usually 1001)

AnonymousUid := XXXX (usually 1001)

4 – In the linux server, make sure the /etc/exports is setting the insecure option.

NFS server has an option of working in insecure mode (Allowing higher incoming port numbers). Windows NFS client often uses higher port numbers. You can enable this option by adding an option to the share
Example: /share *(insecure,rw) ¹

As you can see it’s generic tips and of course disabling each firewall can’t hurt to diagnose 🙂

Источник

Понравилась статья? Поделить с друзьями:
  • Nfs underground ошибка speed exe
  • Nfs underground 2 ошибка установки win 10
  • Nfs underground 2 ошибка please insert disc 2
  • Nfs undercover ошибка установки
  • Nfs shift 2 ошибка 0xc0000142