File explorer wont open with an azure file share drive mapped

Question

I recently setup the file share, the site to site and the point to site vpn access to get to file share. It works great on P2S VPN and S2S VPN, but the minute I am off the VPN and try and open file explorer, it opens, shows only home and doesnt respond. try to close and freezes and computer is pretty much unresponsive. attempt to CTL-ATL-DEL and end process and the computer is jacked. restart the file explorer using task manager, same thing. restart the PC off vpn and same behaviour.

Need help with this as this is an issue as I dont need a local cached version of the server, just want the file share in azure and be able to connect if at office and when at home for all users.

Answer 1

@Mark Hense Welcome to Microsoft Q&A Forum!

Based on the information provided, it seems that there might be an issue with the network configuration or connectivity when accessing the Azure File Share without a VPN connection. Here are a few suggestions to troubleshoot the problem:

Check network connectivity: Ensure that your computer has a stable internet connection when you're not connected to the VPN. Test accessing other websites or online services to verify that your internet connection is working properly.

DNS resolution: Check if your computer can resolve the DNS names of the Azure File Share and Azure resources correctly. Try pinging the storage account name and file share name to see if they resolve to the correct IP addresses.

Firewall or network restrictions: Check if there are any local firewalls or network restrictions on your computer or network that might be blocking access to the Azure File Share when not connected to the VPN. Temporarily disable any firewalls or security software and test accessing the file share again.

Cached credentials: If you had previously accessed the Azure File Share using VPN connectivity and provided credentials, the File Explorer might be trying to use those cached credentials when accessing the file share without the VPN. Clear any cached credentials related to the Azure File Share in the Windows Credential Manager and try accessing the file share again.

Update Azure Storage client library: Ensure that you have the latest version of the Azure Storage client library installed on your computer. Even though you're accessing the file share through File Explorer, updating the library might help resolve any compatibility issues.

Windows Updates: Make sure your operating system is up to date with the latest Windows updates. Updates often include bug fixes and improvements that can help resolve compatibility issues.

1. If the issue still persist : This may require a 1*1 investigation, so If you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support. In this case, could you send an email toAzCommunity[at]Microsoft[dot]com referencing this thread. Please mention "ATTN subm" in the subject field and subscription ID. Thank you for your cooperation on this matter and look forward to your reply.

Kindly let me know what your support request number is so that I can keep track of your case. If you run into any issues, feel free to let me know.

---

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Answer 2

It is end of July, 2024

SMB over QUICK is still not supported despite 3 years old promises.

Explorer still indefinitely freezing when you have Azure share that can not be accessed for some reason. It is even worse than typical 20 years old bug when it freezes when you move a file over disconnected driver accidentally.

Great work, Microsoft Azure team and Microsoft Explorer team!