Azure Filesshare - System error 53 - Troubleshooting

Question

I am also having the same problem as mentioned here Azure Files - System error 53

Although I'm afraid the answers provided have not helped.

My current setup all in west europe

File Share
VM 1 Windows 2012 - Can connect to File Share
VM 2 Windows 2012 - Cannot connect to File Share

I've run PortQRY which confirms that port 445 is outgoing and working.

Although I am still receiving this error

This error occurred after a random shutdown, before which I could connect fine.

What other troubleshooting steps can I take to find out why this is not working?

Have you followed this article [Azure Files Troubleshooting][1] ? [1]: https://learn.microsoft.com/en-us/azure/storage/storage-troubleshoot-file-connection-problems#error53 — Mine Tanrinian Demir - MSFT, Apr 18 '17 at 17:51
According to your description, it seems that no issue on your network between VM and Fileshare, you had better check `regedist`. — Shui shengbao, Apr 19 '17 at 01:51
I ended up wiping the server and remaking it. I'm going to leave this question though encase others need any information from it. — Jack, Apr 19 '17 at 09:27

Shui shengbao · Answer 1 · 2017-04-19T02:50:12.930

According to your description, it seems that no issue is on your network between VM and Azure FileShare.

You could refer to Mine's link, please check Cause 3.

"System Error 53 or System error 87" can also be received if NTLMv1 communication is enabled on the client. Having NTLMv1 enabled creates a less-secure client. Therefore, communication will be blocked for Azure Files. To verify whether this is the cause of the error, verify that the following registry subkey is set to a value of 3:+ HKLM\SYSTEM\CurrentControlSet\Control\Lsa > LmCompatibilityLevel.

I also met a similar question with you, you could check the link. The solution is to modify the registry

Azure Filesshare - System error 53 - Troubleshooting

1 Answers1