Windows 11 cannot access Windows XP shared drive anymore?

Question

Recently, a Windows 11 PC can no longer access a shared drive hosted on a Windows XP machine. The shared folder was accessible before, but now connection attempts fail.

Current environment:

• Windows XP machine used for legacy file sharing
• Windows 10 PCs on the same network can still access the Windows XP shared folder without issue
• SMB 1.0/CIFS Client has been enabled on Windows 11
• Direct access using \\IP_Address\ShareName still does not work

Possible cause may be related to recent Windows 11 security updates, authentication policy changes, guest access restrictions, or SMB compatibility with legacy Windows XP systems.

Looking for guidance or workaround to restore access from Windows 11 to Windows XP shared drive.

Answer 1

Windows 11 has tightened SMB and NTLM security compared to Windows XP–era defaults. Even with SMB 1.0 enabled, authentication from Windows 11 to an XP share can fail if:

• Network discovery / sharing services are not enabled
• Guest/anonymous access is blocked
• NTLM/LM compatibility is stricter on Windows 11 than what XP supports

From the available information, use these supported checks and workarounds:

1. Confirm basic file-sharing prerequisites on Windows 11

1.1. Make sure the Windows 11 PC and the XP machine are on the same network (same router/subnet).

1.2. On Windows 11, turn on network discovery and file sharing:

• Select Start → Settings.
• In Find a setting, type manage advanced sharing settings and open Manage advanced sharing settings.
• Under Private networks, turn on Network discovery and File and printer sharing.
• Under All Networks, turn off Password protected sharing (this is often required when XP is using guest/anonymous access).

1.3. Ensure sharing-related services are running and set to Automatic:

• Press Windows logo key + R, type services.msc, select OK.
• For each of these services, if not running, start it and set Startup type to Automatic:
  • Function Discovery Provider Host
  • Function Discovery Resource Publication
  • SSDP Discovery
  • UPnP Device Host

These steps align Windows 11’s sharing behavior with older systems and ensure the machine can see and talk to legacy SMB hosts.

2. Verify SMB 1.0 client and direct UNC access

2.1. Since SMB 1.0/CIFS Client is already enabled on Windows 11, verify direct UNC access using Command Prompt instead of File Explorer:

net use * \\<XP_IP_Address>\<ShareName>

If this returns an error, note the exact error code/message; it typically indicates an authentication or protocol-level block.

2.2. If the share is meant to be accessed without credentials, ensure that on Windows 11 password-protected sharing is disabled (step 1.2) so guest-style access is allowed.

3. Align authentication level with legacy server (pattern from similar NAS/legacy scenarios)

Windows 11 may require NTLMv2 or better, while XP may be using older LM/NTLM behavior. A known working pattern for legacy SMB devices (from a similar Windows 11 + NAS scenario) is:

• Configure the legacy server (here, Windows XP) to use at least NTLMv2 if possible.
• On Windows 11, set Network security: LAN Manager authentication level to an NTLMv2-compatible option.
• If Group Policy is not available, adjust the LmCompatibilityLevel registry value under: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa to a value that allows NTLMv2 (for example, 3 in the referenced scenario).

This combination restored access in a comparable case where Windows 11 could no longer authenticate to an older SMB server while Windows 10 still could.

4. General SMB/file-sharing troubleshooting on Windows 11

If access still fails after aligning SMB1 and NTLM settings, run through the broader Windows 11 file-sharing checks on the Windows 11 PC:

• Install all current Windows Updates.
• Confirm the Wi‑Fi/Ethernet network profile is set to Private.
• Re-verify network discovery and file/printer sharing are enabled and services are set to Automatic as in step 1.

These steps ensure that no additional sharing or firewall policy is blocking outbound SMB connections.

If, after these changes, Windows 10 can still access the XP share but Windows 11 cannot, the remaining difference is almost always in NTLM/LM policy or SMB1 hardening. Matching the LAN Manager authentication level and allowing NTLMv2 for that legacy host, as described above, is the key workaround.

---

References:

• Can't access shared folders from File Explorer in Windows 10
• File sharing over a network in Windows
• Access Denied when you access an SMB file share in Windows
• The System Cannot a domain controller to service the authentication request. Please try again later - Microsoft Q&A

Answer 2

Hi,

This should work.

Via

https://www.yourwindowsguide.com/2025/01/mapped-drives-not-working-windows-11.html

1. Open the Windows search bar and type “powershell”
2. Right-click on PowerShell and select “Run as administrator”
3. Execute the following commands:

`Set-SmbClientConfiguration -RequireSecuritySignature $false
Set-SmbClientConfiguration -EnableInsecureGuestLogons $true
`

These commands will disable the requirement for security signatures and enable insecure guest logons, which should resolve issues with accessing mapped drives, thereby fixing Mapped drives not working issue.

I’m eager to hear back and work together to find a solution.

A Windows MVP writes content on the above website, so it is safe. However, do watch out for the ads. It should translate into your Browser language automatically.