Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

"You can't access this shared folder because your organization's security policies block unauthenticated guest access"

Technical article
Troubleshooting

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

This message means the Windows SMB client refused to connect to a share as a guest. Microsoft's page says that since Windows 10 version 1709 and Windows Server 2019, SMB2 and SMB3 clients no longer allow guest account access to a remote server, and no longer fall back to the Guest account after invalid credentials are provided. The share is asking for a guest logon, so Windows blocks it. The block is the default in the editions listed in the table below; Microsoft's page says Windows 10 Home and Pro still allow guest authentication by default.

Microsoft's recommendation is to upgrade or replace the device that only supports guest authentication. It documents a registry value and a Group Policy setting that allow insecure guest logons, and says "We recommend that you don't enable insecure guest logons."

What the error means

One Microsoft page carries the message: the Windows 10 page "Can't access shared folders from File Explorer in Windows 10" has a section headed with the full text of the message, with the resolution "You can enable the guest access from your computer by using one of the following methods", a registry method and a Local Group Policy Editor method. The page "How to enable insecure guest logons in SMB2 and SMB3" does not print the message; it explains the default behaviour and the risks.

That page states that "guest credentials might still be required when connecting to a third-party device that doesn't support a username and password." It lists the default behaviour by version:

System Guest logon by default (Microsoft's page)
Windows 10 Enterprise, Pro for Workstations, Education Guest credentials can't be used to connect to a remote share, even if the remote server requests them
Windows 10 Home and Pro Guest authentication is still allowed by default
Windows Server 2019 Datacenter and Standard No longer allowed by default, even if the remote server requests it
Windows 11 Pro Insider Preview build 25267 and later builds Can't be used by default

The page also says that SMB signing is required by default for Windows 11, version 24H2, and Windows Server 2025, and later builds, "which results in compatibility issues with guest authentication if signing doesn't succeed." A guest logon does not support signing: "Guest logons don't support standard security features such as SMB signing and SMB encryption even if the SMB client is set to allow guest logons."

Likely causes

Cause What you see How to confirm
The share or device only offers guest access The message on connect; the device has no user accounts Ask the device owner whether it supports a user name and password
The Windows client blocks insecure guest logons (default) Event 31017 in the SMB client log Event Viewer, as below
Windows falls back to Guest after invalid credentials Credentials were typed but the server treats them as invalid Event 31017; Microsoft says clients no longer fall back to the Guest account after invalid credentials are provided
Signing required by default on a newer client Guest logon fails where signing is required (Windows 11 24H2, Server 2025) Microsoft's page: compatibility issues with guest authentication if signing doesn't succeed
The setting has already been enabled Event 31018 (a warning that an administrator enabled AllowInsecureGuestAuth) Registry or policy value, below

Prove the cause before changing anything

All of these only read.

  1. In Event Viewer, go to Applications and Service Logs\Microsoft\Windows\SMBClient\Security. Microsoft's page lists the events. Event 31017 (Level: Error, task category RejectedInsecureGuestAuth) reads: "Rejected an insecure guest logon. The machine attempted to connect to the server using an insecure guest logon. The server denied the connection. Ensure that the guest account is enabled on the server and configured to allow access from the network." Event 31018 means an administrator has enabled AllowInsecureGuestAuth. Event 31022 means an insecure guest logon was allowed. Microsoft's page names Windows 11, version 24H2 or later, and Windows Server 2025 for this auditing.
  2. Read the registry value on the client:
reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation" /v AllowInsecureGuestAuth

The Windows 10 page names this key and the value AllowInsecureGuestAuth, a DWORD (32-bit) value. A result with no AllowInsecureGuestAuth value means it has not been set under that policy key. Microsoft's page also documents a PowerShell method (Set-SmbClientConfiguration), and this query does not show a setting made that way. The reg query page documents /v valuename.

  1. Ask who owns the device. Microsoft's page recommends upgrading or replacing third-party software or devices that only support guest authentication, so the answer decides which fix to take.

Example (illustrative): at contoso.com.au, the laptop lt22 runs Windows 11, version 24H2, and a staff member opens \\10.0.20.50\scans, a share on an older network storage box that has no user accounts. Windows shows the guest-access message. Event 31017 is in the SMBClient Security log, and the reg query reports the value is not found. The default is blocking the guest logon, and the device only offers guest access.

Fix

The preferred fix is on the device side: upgrade or replace the third-party software or device that only supports guest authentication, which is Microsoft's recommendation. If that is not possible, Microsoft documents enabling insecure guest logons on the client. The same page warns that doing so permits "An attacker to deceive a user into connecting to a spoofed malicious server without producing credential errors or prompts", "Execution of malicious code such as ransomware through the guest logon", and exposure to adversary-in-the-middle attacks. It also says "Both SMB signing, and SMB encryption policies must be disabled in Group Policy in order to use guest logons. Doing so can potentially compromise the security of the client and leave users open to credential theft and relay attacks."

Microsoft's guest-logon page lists prerequisites for changing the setting: an account that is a member of the Administrators group or equivalent, and an SMB client on Windows 10 or later or Windows Server 2019 or later. For a domain-wide change it says to use Group Policy Management (gpmc.msc). It also documents a PowerShell method. The registry route lets you save and restore the old value exactly.

Before you change the setting, record what the earlier query returned: either the value is not found, or it shows a data value. That record decides the back-out.

reg query "HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation" /v AllowInsecureGuestAuth

Risk: the next command allows insecure guest logons on this client. Anyone on the network path can then present a spoofed server to the user without a credential prompt, and Microsoft's page says guest logons do not support SMB signing or encryption. Use it only for a device that cannot be replaced, and on as few clients as possible.

reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation" /v AllowInsecureGuestAuth /t REG_DWORD /d 1

The Windows 10 page says you must create the key if it doesn't exist; reg add creates it with the value. Microsoft's page documents the same setting through the Local Group Policy Editor at Computer Configuration, Administrative templates, Network, Lanman Workstation, "Enable insecure guest logons", set to Enabled.

To undo it: if your saved query reported that the value was not found, run the first command below. If it showed a data value, run the second with that value in place of the placeholder (its /f overwrites the value you set).

reg delete "HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation" /v AllowInsecureGuestAuth /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation" /v AllowInsecureGuestAuth /t REG_DWORD /d <value from the saved query> /f

Enter the decimal number (0 or 1) for the placeholder, not the hexadecimal form that reg query prints, such as 0x0.

The first command removes only the value; if the LanmanWorkstation key did not exist before, an empty key remains. Run neither back-out unless you have run the reg add above.

Confirm the fix

  • The share opens from File Explorer or from net use.
  • On a client that supports the auditing Microsoft describes, event 31018 appears in the SMBClient Security log (it records that AllowInsecureGuestAuth is enabled) and event 31022 appears when a guest logon is allowed.
  • The reg query shows AllowInsecureGuestAuth with the data you set.

What to watch afterwards

  • The warning events 31018 and 31022. Microsoft's page lists them as the audit trail for enabled guest logons. Microsoft's page says the SMB client needs Windows 11, version 24H2 or later, or Windows Server 2025, to turn on this auditing.
  • The device itself. Microsoft's page recommends replacing it, and lists a risk of ransomware execution through guest logons.
  • A signing failure on newer clients, which Microsoft's page says guest logons cannot satisfy.

Risks and limits

These commands have not been run or lab-tested.

Microsoft's pages describe client-side guest logon only. They say nothing about how to make a particular NAS or scanner accept user accounts. They also say that the registry key and the Group Policy setting are the documented means, but do not say what other policies in your estate may override them. The effect reaches every share that client connects to, not only the one you meant. Microsoft's guest-logon page is dated 2025-08-13, so check the current page before you rely on a version list.

Sources