Cannot map network drive. Share names for Unix not visible, nor for Win10 PCs. Receive error: An Extended Error has Occured.

Mike Watson 20 Reputation points
2026-05-24T20:10:18.0433333+00:00

When trying to map a network drive, I get an "An Extended Error has Occurred" or an invalid share name. I CAN access these shares from Win7 PCs and Ubuntu Linux. However, my new Win11 PC cannot. I've checked the share feature and all are ON. Windows 11 came with this new PC.

My data server is running Ubuntu 26.04. Other PCs are Win7Pro.

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
0 comments
Answer accepted by question author

AI answer

2026-05-24T20:10:30.25+00:00

The issue is typically caused by newer SMB/security defaults in Windows 11 that older/Unix SMB servers (or older Samba configs) don’t fully match. Because Windows 7 and Ubuntu can connect, focus on adjusting the Windows 11 SMB client and verifying basic name/path usage.

Use these steps on the Windows 11 PC:

  1. Test basic access and naming
    1. In File Explorer, try the UNC path directly: \\<Ubuntu-IP>\<share-name> instead of browsing the network.
    2. If the IP works but the server name does not, verify the exact computer name and DNS/hosts resolution. For example, if the server name changed (or Windows 11 sees a slightly different name), mapping by the wrong name will fail. A similar scenario is described where a dash and number were added to a computer name, breaking name-based access until corrected.
  2. Relax SMB client security to match older Samba On Windows 11, open PowerShell as Administrator and run: 
       Set-SmbClientConfiguration -RequireSecuritySignature $false
   Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" `
       -Name RequireSecureNegotiate -Value 0 -Force
    Then restart the Windows 11 PC and try mapping the share again with \\<Ubuntu-IP>\<share-name>. These settings disable mandatory SMB signing and “RequireSecureNegotiate”, which can block connections to older Samba/SMB 1.x/early 2.x servers and cause generic errors like “An extended error has occurred” or “invalid share name.”
  3. Verify share name and permissions
    1. Confirm the share name on the Ubuntu server is exactly what is being used in Windows 11. A typo or mismatch in the share name will cause errors similar to “invalid share name.”
    2. Ensure the account and password used in Windows 11 match a valid Samba user on the Ubuntu server.
  4. If mapping by name still fails but IP works
    1. Use the IP-based UNC path in the Map Network Drive wizard (e.g., \\192.168.1.10\data).
    2. Optionally fix name resolution (router/DNS/hosts) so \\servername\share resolves correctly.
  5. Map the drive
    1. Open File Explorer → This PC → More → Map network drive.
    2. Choose a drive letter.
    3. In Folder, enter \\<Ubuntu-IP>\<share-name>.
    4. Check “Reconnect at sign-in” and finish.

If these steps work, the problem was SMB security negotiation or name resolution on Windows 11, not the Ubuntu shares themselves.

References:

AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

2 people found this answer helpful.

4 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Mike Watson 20 Reputation points
    2026-06-05T20:14:44.04+00:00

    Changed the value to '1' as directed above. Still cannot see nor connect to Ubuntu 26.04 samba share, nor connect via IP address.

    Was this answer helpful?

    0 comments
  2. Peak Okello 0 Reputation points
    2026-06-05T19:52:50.3033333+00:00
    1. Confirm the share name on the Ubuntu server is exactly what is being used in Windows 11. A typo or mismatch in the share name will cause errors similar to “invalid share name.”
    2. Ensure the account and password used in Windows 11 match a valid Samba user on the Ubuntu server.
    3. If mapping by name still fails but IP works
      1. Use the IP-based UNC path in the Map Network Drive wizard (e.g., \\192.168.1.10\data).
        1. Optionally fix name resolution (router/DNS/hosts) so \\servername\share resolves correctly.
        2. Map the drive
          1. Open File Explorer → This PC → More → Map network drive.
            1. Choose a drive letter.
              1. In Folder, enter \\<Ubuntu-IP>\<share-name>.
                1. Check “Reconnect at sign-in” and finish.

    If these steps work, the problem was SMB security negotiation or name resolution on Windows 11, not the Ubuntu shares themselves.

    Was this answer helpful?

  3. Peak Okello 0 Reputation points
    2026-06-05T19:52:03.7466667+00:00

    One of the reason your Windows 11 PC cannot access the network shares could be because Microsoft disabled unauthenticated guest access by default to improve security. Your Ubuntu data server is likely allowing guest access without a password, which Windows 11 strictly blocks, resulting in that extended error message.

    Was this answer helpful?

    0 comments
  4. Scott Nguyen 2,050 Reputation points Independent Advisor
    2026-05-24T21:07:34.47+00:00

    Hello Mike Watson,

    One of the reason your Windows 11 PC cannot access the network shares could be because Microsoft disabled unauthenticated guest access by default to improve security. Your Ubuntu data server is likely allowing guest access without a password, which Windows 11 strictly blocks, resulting in that extended error message.

    I would suggest that you should allow these logons by opening the Registry Editor as an administrator and navigating to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters. Once you are in that location, find DWORD (32-bit) Value named AllowInsecureGuestAuth and change its value data to 1. Give your Windows 11 computer a quick restart, and you should be able to map those network drives normally.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.