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

Skip to content

• #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:

How to Mount an NFS Share Using a Windows 10 Machine

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

Doesn’t know what he’s talking about

• #8

What do you get when you simply use?:

Mount \192.168.0.24mntTower X:

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

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

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?

«Ошибка сети — 53» при попытке смонтировать общий ресурс NFS в клиенте Windows Server 2008

CentOS | Windows 2008

У меня на сервере CentOS 5.5 работает nfsd. На стороне Windows я использую Windows Server 2008 R2 Enterprise. У меня включена роль сервера «Файловые службы» и включены как Клиент для NFS, так и Сервер для NFS.

Я могу успешно подключиться / смонтировать общий ресурс NOS CentOS из других систем Linux, но у меня возникают ошибки при подключении к нему из Windows. Когда я пытаюсь подключиться, я получаю следующее:

(IP и имя общего ресурса были изменены, чтобы защитить невинных :-))

• Я проверил низкоуровневое сетевое соединение между клиентом Windows и сервером NFS с помощью telnet (для NFS на TCP / 2049), поэтому я знаю, что порт открыт. Я также подтвердил, что входящие и исходящие порты брандмауэра присутствуют и включены.
• Я столкнулся с Техническая заметка Microsoft , в которой предлагается изменить« Порядок поставщиков », чтобы« Сеть NFS »была выше других элементов, таких как Сеть Microsoft Windows. Я изменил это и перезапустил клиент NFS — не повезло.
• Я подтвердил, что общая папка на сервере NFS доступна для чтения / записи всем (777)
• Я пробовал другие варианты команды монтирования, такие как: mount 10.10.10.10:/share/ z: и mount 10.10.10.10:/share z: и mount -o anon mtype=hard 10.10.10.10:/share * Не повезло.
• Что касается вывода команды, я попытался набрать NET HELPMSG 53 , но это мне мало что говорит. Просто «Сетевой путь не найден».

Я заблудился, как приступить к устранению неполадок. Есть идеи?

1 ответ

У меня та же проблема, и я нашел сообщение здесь , в котором говорится:

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)

You can also try installing Windows services for UNIX package which contains a nfs client. You can try to connect the nfs server using this utility and cross check again. You can download the package from the following link http://www.microsoft.com/downloads/e. displayLang=en

Я изменил / etc / exports в соответствии с ним (добавив небезопасную опцию), и он работает. Надеюсь, это поможет.

Windows nfs mount error 53

Вопрос

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:

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

• 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?

Windows nfs mount error 53

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Answered by:

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:

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

• 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?

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 \ data N: , I keep getting this error:

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:

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

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:

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).

5 Answers 5

On the Linux part — make sure your NFS Server Configuration is correct:

• nfs-utils and nfs-utils-lib should be installed
• rpcbind, nfs-server, nfs-lock, nfs-idmap should be enabled

rpcbind, nfs-server, nfs-lock, nfs-idmap should be started

Choose the directories you want to share

get the IP address of your Windows 10 NFS client

edit the exports file (etc/exports) and add the user you will use to it: /home/user 192.168.1.2(rw,sync,root_squash,all_squash,anonuid=1001,anongid=1001) — note: the IDs are the ones obtained previously

restart the service with systemctl restart nfs-server

get the proper ports with rpcinfo -p

add them to the firewall

On the windows part:

• make sure you installed Client for NFS
• you now need to match the UID and GID that pulled earlier (1001 in the linux part example) on both the Server and the Client
• regedit to HKEY_LOCAL_MACHINESOFTWAREMicrosoftClientForNFSCurrentVersionDefault
• You will need to make two new DWORD (32-bit) entries by right clicking inside the Default key. They should be named “AnonymousGid” and “AnonymousUid”. They should both have a decimal value matching your user’s GID and UID that you got earlier (1001 in the example)

restart NFS service on the Windows 10 Client side by using :

nfsadmin client HOSTNAME config casesensitive=yes

nfsadmin client HOSTNAME stop

nfsadmin client HOSTNAME start

finally, make your mount: mount -o anon 192.168.1.3homestorage X:

silverbullettruck2001

Junior Member

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:

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.