Ping Works, but the New Windows Server Can't Open Other PCs' Shared Folders

November 2026

The symptom

You replaced the office server with a new Windows Server 2022. Now:

  • Every PC can open \\SERVER and reach the ERP folders. That part is fine.
  • From the server, \\PC1 (an older Windows 10 PC) does not open, or asks for a password that never works.
  • ping PC1 works. The firewall looks fine.

The direction that fails is server to PC. PC to server works, and that is why it is confusing.

Step 1: Prove it is not the network

Ping only shows that the cable works. Test the file-sharing port itself, from the server:

Test-NetConnection 192.168.1.50 -Port 445

Use the IP of the PC that fails. If it says TcpTestSucceeded : True, the network and the PC's firewall are fine, and the problem is how the server logs in. If it says False, the PC's firewall or its network profile is blocking sharing. Fix that first (see Step 4).

Step 2: Why Server 2022 refuses

A new Server 2022 is stricter than the older Windows that office PCs run. Out of the box it:

  1. Blocks insecure guest logons. Many office PCs share folders with no password ("Everyone"). When the server connects to such a PC, Windows tries a guest logon, and Server 2022 refuses it. PCs opening the server use a normal login, so that direction works.
  2. Requires SMB signing. Some older PCs or devices don't support it, and the connection is refused.
  3. May set the network to Public, which hides other PCs and turns off discovery.

Step 3: The fix

On the server, in PowerShell run as Administrator:

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force
Set-SmbClientConfiguration -RequireSecuritySignature $false -Force
Set-NetConnectionProfile -NetworkCategory Private
Enable-NetFirewallRule -DisplayGroup "Network Discovery"
Enable-NetFirewallRule -DisplayGroup "File and Printer Sharing"

No restart is needed. These are stored in the registry, so they survive a reboot. Now try \\PC1 again.

In the office we fixed, all three settings were changed together, so we can't say which one mattered. Most often it is the guest-logon setting. If you want to know, turn them back one at a time and test after each.

Step 4: If it still fails, read the error number

From the server, log in with the PC's own account:

net use \\PC1\IPC$ /user:PC1\username *

The * asks for the password. The error tells you what to look at:

Error Meaning What to check
53 or 67 Path not found The PC's firewall, its network profile, or File and Printer Sharing is off
5 or 1326 Wrong account or password Use the PC's own username. For a Microsoft-account login, use the email and online password, not the PIN
1219 A saved connection conflicts Run net use * /delete, then try again
1231 Network location not reachable Discovery is off on the PC, or the name is wrong. Try the IP

Is this setup safe?

On a closed office network, allowing guest logons and turning off signing is a common trade-off. It is weaker than a proper setup. The cleaner way is to turn on password-protected sharing on the PCs, share folders with a named user, and then undo the two changes:

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

Do that only after the PCs no longer depend on guest access, or the problem comes back.

Quick checklist for any new Server 2022

Network profile is Private, discovery and file sharing are on, and the guest and signing settings match what your oldest PC supports. See the new server checklist.

Related guides


← All troubleshooting guides