Server connect issue since Win11 November patchday

[NakedPirate 6]

Beginning with updating Win11 on my machine yesterday, I can't connect to my server WITHOUT changing  the Windows firewall app setting for EMBY server to public.
It has nothing to do with the clients, routing or further circumstances. The whole profile is still set to "private", but "embyserver.exe" MUST be set to private and public, to connect from my LAN /24.
Nothing changed on the machine but KB890830+defender update, KB5045935 (net-fw) and the KB5046633 patch.

The background is yet still to be examined. The reason I write this topic is that I find myself wondering why I'm the only one with this problem as far as I can see.
Anyone else?

[Neminem 703]

Check your network settings it should be set to private.

Sometimes after windows update these settings are being defaulted to public.

[NakedPirate 6]

Thanx Neminem.
Yes, I have and had always a PRIVATE network in Windows settings.

Regardless of my network type, I had to change the win firewall to private+public to allow incoming connections (from my LAN!).
Until the yesterday patches the private rule for embyserver.exe always worked without changing it to public.

 

Edited November 14, 2024 by NakedPirate
I am Batman!

[Neminem 703]

Did you check that the update did not change your nic to public ?

[NakedPirate 6]

100%.
I even checked the registry keys for category and with powershell. Everything correct, no unidentified networks, every adapter "private".
Seems, I'm the only one. Weird. I will check, reset and analyze the next days..
Thanks very much.

Maybe, if it's not too much to ask, if somebody please can take a look in his firewall setting to confirm embyserver is running with only "private" checked, I'd appreciate it very much.
Because there's 2 possibilities: Patchday changed something OS/firewall related or I had the "public" setting for emby before and something on this patchday changed it to private only.
(Pictures in my post above). After all it's not really a big problem, I have no open or forwarded ports in my router, but maybe it helps somebody with the same problem later...
Thanks and bye!

[Neminem 703]

Guess that Emby will get a lot more support tickets about this issue, if a windows update / patch is causing it.

To be clear ?

Same Emby server version as before ?

Only os update ?

Any update to VPN software / Network drivers / Security software ... etc

Old sayng "Everything does not come, out of nothing"

[d00zah 140]

3 Windows 11 Pro machines updated this AM. 1 server (Version 4.8.10.0) / 2 clients (potential backup server hosts) all have both Public & Private access enabled (default?) in firewall(s). No connection issues detected.

EDIT: All Emby internet traffic directed thru PIA split tunnel. No change after disabling VPN.

Edited November 14, 2024 by d00zah

[NakedPirate 6]

I swear! Nothing. Only the 3 patches mention in my first post.
Btw, I forgot:
Win11/23H2
Emby V: 4.8.10.0 (since 10/01/24)

No 3rd party FW, updates or anything.

I got it it relatively quick.
1. Ping and every other connection to the machine worked flawlessly and fast.
2. Problem existed in whole network 192.x.x.x/24
3. Deactivating firewall worked
4. Checking network and firewall settings and setting firewall TCP and UDP for emby to public worked, regardless of network type "private".

But there were already enough others complaining here, if it was a general problem...quite sure, I'm an outlier.

[visproduction 210]

Possibly related?
https://www.wintips.org/fix-windows-11-24h2-cannot-access-network-shares-0x80070035/

[NakedPirate 6]

FYI. It hit me again on December Patchday.

No connection to emby server whatsoever after the KB on Tuesday.
Switching OFF Win firewall without effect.
I had to delete the whole emby entry in the firewall settings and to enter the rule completely new to make it work again.
Fresh Win11 without any other security software, HIPS or FW. It's getting weirder with every patchday....

Merry Christmas and Happy Holidays!

Edited December 12, 2024 by NakedPirate
I am Batman!