Two Computers Beside Each Other Could Not Connect. The Fix Was One Setting Nobody Told Me About.

 

Image for illustration only

Error code: 0x800704f8

You can't access this shared folder because your organization's security policies block unauthenticated guest access. These policies help protect your PC from unsafe or malicious devices on the network.

"Kuys Mark I can’t connect to the shared folder!"

There is a specific kind of frustration in IT support that I call the "physically close, digitally lost" problem.

Two computers. Same room. Same floor. Same LAN. Literally sitting beside each other on the same desk in the Finance Department.

And they cannot see each other on the network.

This happened to me last week. Unit-1 could not connect to Unit-2. I stood there looking at two computers separated by maybe half a meter of office space, and one of them was acting like the other did not exist.

The Part That Made No Sense

The first thing I did was the obvious check. Cables. Switch. IP addresses. All fine.

Then I tested connectivity from my own desktop unit. Unit-1 could connect to my unit. Unit-2 could also connect to my unit. Both machines were talking to me just fine.

But Unit-1 and Unit-2 — two computers sitting right beside each other — could not talk to each other.

In IT terms, this is the equivalent of two officemates who can both talk to you normally, but somehow cannot talk to each other even though they are literally sharing an armrest.

My first instinct was to run the standard checks. Firewall settings. Network sharing. Workgroup names. Everything looked correct on paper. The network path existed. The permissions appeared open. And yet — nothing.

I sat with it for a while. (whhhaaaat iiisssss happennninngggg!)

Then I remembered YOUTUBE! 😂

Guest logon policies in Windows. A setting that quietly blocks certain types of network access between machines — not because of a firewall, not because of wrong IP configuration, but because of a security policy that Windows enables by default and almost nobody talks about.

The Fix: Local Group Policy Editor

Here is exactly what I did, step by step — because if this happens to you, I want you to find this post and fix it in ten minutes instead of spending an afternoon confused.

Step 1: On the affected computer (Unit-1 in my case), press Windows Key + R, type gpedit.msc and hit Enter. This opens the Local Group Policy Editor.

Step 2: Navigate through the left panel: (see photo)

Computer Configuration

→ Administrative Templates→ Network→ Lanman Workstation

Step 3: On the right side of the screen, scroll down through the settings list and look for "Enable insecure guest logons".

Step 4: Double-click it. A settings window opens. By default it is set to Not Configured or Disabled.

Step 5: Click the Enabled radio button. Then click Apply. Then OK.

Step 6: Restart the computer.

That is it.

After the restart — Unit-1 could see Unit-2. Full access. Problem solved.

Why This Happens

The setting exists because Windows, starting from Windows 10 version 1709 onward, began blocking guest access to shared network folders by default as a security measure. The logic from Microsoft's side is reasonable — unauthenticated guest connections to network shares are a potential security vulnerability.

The problem is that in a small office environment — especially a government office where computers are on the same trusted LAN and shared folders are used constantly for internal documents — this default security block creates more friction than protection. Unit-1 and Unit-2 are not talking to the internet. They are talking to each other across half a meter of office desk.

The fix of enabling insecure guest logons essentially tells Windows: "I understand the risk, and in this specific trusted network environment, allow guest-level access between machines."

For enterprise networks with sensitive data, you would want to evaluate this carefully. For a small government office LAN where the Finance team needs to access shared folders on the unit beside them — it is the practical solution.

The Lesson I Keep Learning

Every time I solve a problem like this, the lesson is the same.

The issue is almost never what it looks like on the surface. Two computers that cannot connect despite being physically adjacent is not a cable problem. It is not a switch problem. It is not an IP problem. It is a policy problem — a single setting somewhere in a configuration menu that Windows enabled quietly in an update and nobody announced to the people managing small office networks.

The frustrating part is not the fix. The fix, once you find it, takes five minutes. The frustrating part is the time spent looking in the wrong places because the symptom points you in a completely different direction from the actual cause.

This is why I document things. Not just for other people — for myself. The next time this happens in another unit, in another department, I want to find my own blog post and remember exactly where the setting is.

That is also, honestly, why this blog exists. 😄

Before I Close This Tab

If you are an IT person — or the unofficial IT person in your office, which in Philippine government offices is sometimes just whoever owns a laptop — and you are staring at two computers that can see everything else on the network except each other:

Check the guest logon policy first. Before you reinstall anything. Before you call the network provider. Before you spend two hours checking configurations that are all already correct.

The path: gpedit.msc → Computer Configuration → Administrative Templates → Network → Lanman Workstation → Enable insecure guest logons → Enabled → Apply → OK → Restart.

Five minutes. One setting. Two computers that can finally talk to each other.

You are welcome. 

See photos below