Share via

Network sharing issue being blamed on Insider Preview?

Anonymous
2024-02-12T03:13:48+00:00

I have two Windows11 Pro desktops connected via Ethernet to the same home network using exactly the same share settings, same firewall settings, etc. For whatever reason, PC A can see and access PC B's but not the other way around. In fact, PC A cannot be seen or accessed from PC B, not even using Remote desktop, which also has been activated on both. I log into both using my unique Windows ID & Pwd, though under 'Users' my IDs are different (one bears my full name and the other only 5 characters of my email address: 'ghern'.

When PC A does not appear in the 'Network' window using File Explorer on PC B I type in the URL: \PARALEGAL (network name of PC A) and I get a login screen. However, upon entering my correct credentials I get an error message telling me that 'my organization's security policies... blah... block unauthenticated guest access'. (I'm using my own personal Windows ID & Pwd. ???).

I have contacted MS Support who took control of PC A and did some troubleshooting. Upon being unable to detect what the problem was the scapegoat was the insider preview Dev edition Build 26052.ge_release.240202-1419 running on both PCs. I'm certain that is not the case. Any new 'beta' features are 'bells and whistles' added on but networking is at the core of any build and IS RARELY TOUCHED.
I have tried all the tips regarding sharing, permissions, etc, to no avail.
Any help will be greatly appreciated. Thanks!

Windows Insider program | Windows Insider preview | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-02-12T05:24:24+00:00

    There is another problem that has been going on for years and reported to Microsoft, but never got fixed.

    It can be intermittent or fail every time I open the Network and it may change after a Windows update.

    The symptoms are different and may be unrelated to your specific problem, but here is what I see:

    When I open the network, I can see all the other PCs connected but not my own.

    The only way to get it to show up is by restarting the service FDResPub.

    From command prompt (Run as Administrator).

    I issue the commands below to stop and then start the service, after that my PC shows up on the network correctly.

    The problem has been going on and off for years and MS never cared to fix it. 😝🤷‍♂️

    0 comments