Troubleshoot network credentials between devices on the same network

Hayes Margaret 0 Reputation points
2026-08-26T02:43:58.4166667+00:00

I can access a shared folder from a PC that is on another network and no credentials are requested, but when I try to access the same shared folder from a PC that is on the same network, it asks for network credentials and I don't know how to solve it. File and folder sharing is now enabled and password usage is disabled.

I look forward to your contributions. [moderator's note: moved from Microsoft 365 and Office | Install, redeem, activate | For business | Windows]

Windows for home | Windows 11 | Recovery and backup
0 comments No comments

2 answers

Sort by: Most helpful
  1. Vikki-T 11,975 Reputation points Microsoft External Staff Moderator
    2026-08-26T07:56:04.8166667+00:00

    Hi Hayes Margaret,

    The credential prompt may be controlled by the client PC’s SMB security settings, so turning off password-protected sharing on the host PC does not always prevent it.

    At this point, I recommend that you review and try the steps provided in the AI generated answer on your thread. That reply typically include the most relevant checks for this scenario. 

    Before we continue, could you confirm whether these are personal computers on a home network, or work devices managed by your organization? If they are managed work devices, network-sharing and SMB authentication policies may be controlled by your IT administrator.

    In the meantime, please try the following:

    • On the host PC, confirm that the folder grants the required access under both the Sharing and Security tabs.
    • On the affected PC, open Credential Manager > Windows Credentials and remove any saved credentials for the host PC.
    • Restart both PCs, then reconnect using the host computer’s name rather than its IP address.
    • If credentials are still requested, enter an existing account from the host PC in the format HostPCName\Username, along with that account’s password.

    Using a valid account from the host PC is preferable to enabling insecure guest access, as guest SMB connections may be blocked by newer Windows security settings. Thank you so much for your understanding. 


    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.

    Was this answer helpful?


  2. AI answer

    2026-08-26T02:44:15.01+00:00

    This usually happens because Windows treats access from the same network as an authenticated SMB connection and may block guest access or require valid credentials, even when password-protected sharing is turned off.

    Try these checks in order:

    1. Verify file sharing is enabled on the host PC.
      • Open Control Panel.
      • Go to Network and Sharing Center.
      • Select Change advanced sharing settings.
      • Turn on File and printer sharing.
      • Save changes.
    2. Verify password-protected sharing is configured as expected.
      • In Network and Sharing Center > Change advanced sharing settings.
      • Expand All Networks.
      • Under Password protected sharing, select Turn on password protected sharing if access should require a valid account on the host, or confirm the current setting if testing guest-style access.
    3. Check the shared folder permissions on the host PC.
      • Right-click the shared folder > Properties > Sharing > Advanced Sharing > Permissions.
      • Grant Everyone the required share permission.
      • Then open Security tab > Edit > Add > add Everyone and grant the required NTFS permission.
      • Access can fail if Share and NTFS permissions do not both allow the user.
    4. If the prompt appears because Windows is trying guest access, use valid credentials instead of guest access.
      • Current Windows behavior blocks unauthenticated guest access by default.
      • The recommended fix is to connect with valid credentials to the PC that hosts the share rather than relying on guest access.
    5. If the shared device only works with guest access, insecure guest logons can be enabled on the client as a temporary workaround.
      • Warning: this reduces security and is discouraged except on a trusted private network.
      • Registry Editor method:
        • Open Registry Editor.
        • Go to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation.
        • Create the key if it does not exist.
        • Create DWORD (32-bit) Value named AllowInsecureGuestAuth.
        • Set its value to 1.
      • Local Group Policy Editor method:
        • Run gpedit.msc.
        • Go to Computer Configuration > Administrative templates > Network > Lanman Workstation.
        • Open Enable insecure guest logons.
        • Set it to Enabled.
    6. If different credentials were already used to the same server, disconnect existing mappings first.
      • Windows does not allow multiple connections to the same server using different usernames at the same time.
      • A workaround is to connect by the server IP address or by a different DNS alias, which makes Windows treat it as a different server.
    7. If access is by IP address, try the server name instead.
      • When connecting by IP address or to a workgroup device, NTLM may be required and can be blocked.
      • Connecting by the server’s Kerberos-capable name is the preferred approach.

    If the goal is simple home or small-office sharing, the most reliable setup is:

    • enable file and printer sharing,
    • share the folder with the correct Share and Security permissions,
    • use a valid account on the host PC for access,
    • avoid guest access unless the security risk is acceptable.

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

    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.