@Dnyaneshwar Surywanshi Welcome to Microsoft Q&A Forum, Thank you for posting your query here!
Based on the Issue there could be several reason: If you map a drive to a network share, the mapped drive may be disconnected after a regular interval of inactivity, and Windows Explorer may display a red X on the icon of the mapped drive. However, if you try to access or browse the mapped drive, it reconnects quickly.
Mapped drive connection to network share may be lost
In Registry Editor, locate and then click the following registry subkey:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
- Right-click Configuration, click New and then click DWORD (32-bit) Value.
- Name the new registry entry as EnableLinkedConnections.
- Double-click the EnableLinkedConnections registry entry.
- In the Edit DWORD Value dialog box, type 1 in the Value data field, and then click OK.
Exit Registry Editor, and then restart the computer.
Additional information Step 2: If the issue still perists - Locate and then click the following key in the registry:
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters
- In the right pane, click the autodisconnect value, and then on the Edit menu, click Modify. If the autodisconnect value does not exist, follow these steps:
- On the Edit menu, point to New, and then click REG_DWORD.
- Type autodisconnect, and then press ENTER.
- On the Edit menu, click Modify. We tried to set the decimal value to -1 but it would not allow.
- Click Hexadecimal.
- In the Value data box, type ffffffff, and then click OK.
- We ran net config server /autodisconnect:-1 on a command prompt instance.
- Change the NTLM authentication level .Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\Network security: LAN Manager authentication level changed to “Send LM & NTLM - use NTLMv2 session security if negotiated”.
- We then confirmed the NTLM version in the registry was properly set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Also cross verify- NTLMv2: NTLM version 2 must be enabled to use Azure File Share:
If HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel is set to 3 4 or 5
You can set the NTLM level via GPO as detailed in this article
If the issue still persists, can you please across verify the details mentioned on this article.
Also provide the information mentioned below for future troubleshooting step:
- Is this a new deployment?
- What was the last change done before you started seeing this issue?
- Does the issue always happen, or is it sometimes possible to connect to the share?
I wish to engage with you offline for a closer look and provide a quick and specialized assistance,
Hope this helps!
Kindly let us know if the above helps or you need further assistance on this issue.
-----------------------------------------------------------------------------------------------------------------------------------------
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.