sodcalculator

10 Tech How-To

Access SMB Share When Windows Blocks Guest

Guide 10-8119 · Updated · Step by step

This guide fixes the Windows error where you cannot connect to a network SMB share because the server only allows guest access, but your Windows 10 or 11 PC blocks it by default. You will learn how to re-enable insecure guest logons safely, or alternatively how to set up proper credentials so you can access the share without weakening security.

What You’ll Need

  • Windows 10 or 11 PC
  • Administrator account on that PC
  • The network share’s name or IP address
  • If the share requires a username/password, those credentials

Step-by-Step

  1. Identify the exact error. Try connecting to the share by pressing Win + R, typing \\server\share (replace with your actual server and share name), and pressing Enter. Note the error message. If it mentions “guest access” or “insecure guest logons,” proceed with the steps below.
  2. Decide which fix to use. If the share is on a trusted local network (e.g., a NAS or old Windows machine) and you cannot set up a user account on it, you can re-enable guest logons. If you can create a dedicated user account on the server, do that instead—it’s more secure.
  3. Enable insecure guest logons (if needed).
    1. Press Win + R, type gpedit.msc (Windows Pro/Enterprise) or regedit (all editions), and press Enter.
    2. If using Group Policy Editor: Navigate to Computer Configuration → Administrative Templates → Network → Lanman Workstation. Double-click Enable insecure guest logons, set it to Enabled, click OK.
    3. If using Registry Editor (no gpedit): Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation. If the key doesn’t exist, create it. Create a DWORD (32-bit) named AllowInsecureGuestAuth and set its value to 1. Close the editor.
  4. Restart the workstation service. Open Command Prompt as administrator (right-click Start → Command Prompt (Admin)), type net stop workstation && net start workstation and press Enter. Or simply reboot the PC.
  5. Try connecting again. Press Win + R, type the share path, and press Enter. It should now connect without prompting for credentials.
  6. If you prefer credentials (more secure):
    1. On the server, create a local user account (e.g., on a NAS, in its admin panel; on a Windows PC, go to Computer Management → Local Users and Groups).
    2. On your Windows PC, open Credential Manager (search for it in Start).
    3. Click Add a Windows credential, enter the server’s IP or name, the username (use SERVERNAME\username format if needed), and the password. Save.
    4. Now try connecting again. Windows will use the saved credentials.

Common Mistakes

  • Editing the wrong registry key. The key must be under LanmanWorkstation, not LanmanServer. The latter controls your PC as a server, not as a client.
  • Not restarting the service. The change won’t take effect until the Workstation service restarts or you reboot.
  • Using gpedit on Home editions. Group Policy Editor is not available on Windows Home. Use the registry method instead.
  • Still getting a password prompt. If the server requires a valid user, enabling guest logons won’t help. You must supply correct credentials.

Tips

  • Only enable insecure guest logons on a trusted network (home or small office). Avoid doing this on public Wi-Fi.
  • After you’re done, consider disabling guest logons again to keep your PC secure.
  • If the share is on a NAS, check its settings for “guest access” or “anonymous”—some NAS devices have a separate toggle.
  • Use the IP address instead of a hostname if DNS resolution is problematic.

Troubleshooting

If you still can’t connect after enabling guest logons:

  • Check the server’s SMB settings. The server must also allow guest access. On Windows Server, this is in Computer Configuration → Administrative Templates → Network → Lanman Server → “Enable insecure guest logons” (same setting, but on the server).
  • Verify SMB protocol version. Old devices may use SMB1, which Windows 10/11 disables by default. You can enable it in Windows Features, but this is insecure—prefer updating the device firmware.
  • Firewall blocking. Ensure the server’s firewall allows SMB (port 445). Temporarily disable the firewall to test, then re-enable.
  • Network discovery. Turn on Network discovery in Control Panel → Network and Sharing Center → Advanced sharing settings.
  • Check the share path. Use the server’s IP: \\192.168.1.10\share instead of a hostname.

Frequently Asked Questions

Why does Windows block guest connections by default?

Microsoft disabled insecure guest logons to protect against malicious servers that could intercept credentials or serve malware. It’s a security hardening measure introduced in Windows 10 version 1709.

Is it safe to enable insecure guest logons?

Only on a trusted network. Guest logons send no credentials, but they also mean the server doesn’t authenticate you—anyone on the network could potentially access the share. Use it only for a short time or on a private home network.

I don’t have gpedit.msc, what do I do?

Use the registry editor method. It works on all editions of Windows 10/11.

Can I access the share without enabling guest logons?

Yes, if the server allows creating a local user account. Set up a user with a password on the server, then use those credentials on your PC (either by typing them when prompted or saving them in Credential Manager).

What if the server is a Linux NAS?

Most NAS devices (Synology, QNAP, etc.) have a setting for “guest access” or “anonymous” in their SMB configuration. Enable that, and also enable insecure guest logons on your Windows PC.

After enabling, I still get “Access denied.” What now?

Check the share’s permissions on the server. Even with guest access, the share must grant “Everyone” or “Guest” read/write permissions. Also ensure the server’s SMB service is running.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →