Ideal Point Of Sale IdealPoint Of Sale Support
← Support

Two PCs can't open each other's shared folders or printers

After the Windows 11 24H2 update, a PC often can no longer open another PC's shared folder or shared printer, even one that worked before. Windows says it can't reach \\POS1, or that security policies block unauthenticated guest access.

Windows 11 24H2 turned two protections on: it refuses guest logons (opening a share without a password), and it requires every connection to be signed, which a guest logon can't do. A network that Windows calls Public blocks sharing as well.

One script makes the networks Private and turns those two protections off.

You need:

Run it on both PCs: the one that shares the folder or printer, and the one that opens it.

Use it on the venue's own network only. It turns off two Windows protections for file and printer sharing, so it does not belong on a laptop that also joins public Wi-Fi.

The script

One zip with one file: Win11_network_sharing_fix.bat.

  1. 1Extract the zip on the PC

    Download the zip on the PC, or copy it over. Right-click it and choose Extract All…, then use the extracted folder: the script does not run from inside the zip.

  2. 2Run the script

    Double-click Win11_network_sharing_fix.bat and answer Yes when Windows asks for administrator rights. If Windows first warns about a file from the internet, choose Run (or More info → Run anyway).

    In a window that stays open, the script:

    • makes every network the PC is connected to Private;
    • allows guest logons;
    • stops requiring signing, both when this PC opens another PC's share and when other PCs open this one's;
    • shows the result.
    Making the connected networks Private (Public blocks file and printer sharing)...
    Allowing guest logons (shares opened without a password)...
    Not requiring SMB signing when this PC connects to others (a guest logon can't sign)...
    Not requiring SMB signing when others connect to this PC's shared folder or printer...
    
    Result - every line should start with OK:
       OK  network Network 2 (Ethernet): Private
       OK  guest logons allowed: True
       OK  signing required, this PC to others: False
       OK  signing required, others to this PC: False
    
    A new router can make the network Public again - then run this again.
    Press any key to continue . . .

    A full run. Every line of the result should start with OK. Press any key to close the window.

  3. 3Repeat on the other PC

    Do the same on the other PC. Running the script again on a PC that is already done changes nothing.

  4. 4Open the share

    On the PC that opens the share, type \\ and the other PC's name in File Explorer's address bar, for example \\POS1, or its IP address, such as \\192.168.1.10. File Explorer's Network list can take a while to show other PCs, so don't rely on it.

    If a mapped drive or a shared printer still shows an error, restart that PC.

If something goes wrong

Turning the protections back on

When the PCs no longer share anything, open PowerShell as administrator (right-click Start → Terminal (Admin), or Windows PowerShell (Admin) on Windows 10) and run:

Set-SmbClientConfiguration -EnableInsecureGuestLogons $false -Force
Set-SmbClientConfiguration -RequireSecuritySignature $true -Force
Set-SmbServerConfiguration -RequireSecuritySignature $true -Force

Shares that need a guest logon stop opening again. The network can stay Private: that is right for the venue's own network.

Without the script: by hand

Open PowerShell as administrator (right-click Start → Terminal (Admin)) and run these four lines, on both PCs:

Get-NetConnectionProfile | Set-NetConnectionProfile -NetworkCategory Private
Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force
Set-SmbClientConfiguration -RequireSecuritySignature $false -Force
Set-SmbServerConfiguration -RequireSecuritySignature $false -Force