Problem mapping an xp network share from a windows 10 pc

Question

When we map a network share (from a Windows XP PC) on a newly installed Windows 10 PC (21H1) we have problems.
We enabled SMB1.0/CIFS Client and initially we could perform correctly the mapping and we correctly browse files on the network share.

But when we restart the Windows 10 PC then when we open explorer on the mapped drive, explorer keep remain freezed with the spinning circle and the only solution is to boot the machine.

The network share works correctly with other Windows 7 PC but the same problem happen to other new Windows 10 PC.
The share is mapped without user/password.

Please help us.

Answer 1

Hi,

Many thanks for your quick feedback.

After performing a lot of research, I found a workaround may suitable for your issue. Lots of people who has the same issue has been resolved their problem by this workaround, please follow the following detailed steps to set ProviderFlags to 1 (If you have a mapped drive with letter Z, then DriveLetter is Z):

Please navigate to the following Registry Key:

Computer\HKEY_CURRENT_USER\Network\Drive Letter

Create a REG_DWORD with name ProviderFlags and set the value to 1.

And then please restart your windows 10 device to check if the issue still existed.

Here are 2 similar threads discussed before for your reference:

windows 10 version 2004 mapped drive issue

Location is not available B:\ is not accessible

Best Regards,
Sunny

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Hi,

Welcome to Q&A platform.

1. Firstly, please help to confirm if Windows 10 and Windows XP clients can ping each other successfully?

2. On Windows 10 PC, please make sure that we have enabled network discovery and file and printer sharing.

3. Please run the following command in PowerShell to double confirm is the SMB1.0 was enabled on Win 10

Get-WindowsOptionalFeature –Online –FeatureName SMB1Protocol

4. Then if SMB 1.0 was enabled, please try the following steps on Win 10.

Open Local Group Policy Editor-->Security Settings-->Local Policies-->Security Options--> find Network Security: LAN Manager authentication level, right click it and select Properties-->select Send LM&NTLM - use NTLMv2 session security if negotiated--> click Apply and OK

5. The next step is please try to select Sent LM & NTLM responses in properties of Network Security: Lan Manager authentication level.

Best Regards,
Sunny

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Thanks SunnyQI,
tryed all your suggested steps, but didn't solve the problem.

Answer 4

Hi,

Many thanks for your feedback.

Please create a new DWORD value name of AllowInsecureGuestAuth and set its value data to 1 in the following registry key to see if the issue still existed.

HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters

Or I would suggest you could save the corresponded user name and password in Credential Manager to see if the issue can be resolved.

Best Regards,
Sunny

----------

If the Answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 5

Hi,
the problem still remail.
Our network share is mapped without username/password.