SOLVED: Windows 11 on Wifi as a Server

[TheWanderingMage]

Server Version 10.11.11
I'll be talking about 3 computers
A - Windows 10 PC - Hardwired
B - Windows 11 PC - On Wifi (unregistered ATM an bypassing TPM and safeboot requirement)
C - Windows 10 Laptop - On Wifi

I setup computer A as a server with no problems.  B & C connect no issues.  I even have Tailscale setup and my daughters outside computer was able to connect.

A is my main computer which was most practical to get everything setup on and test, but I planned to eventually migrate.  So, I went to setup computer B as the permanent host.  I got all the settings/metadata setup and transfered from computer A, no problem.  I have jellyfin & tailscale on it.  So at this point A & B are both running their own servers which are up to date duplicates of eachother.

I know it may not be optimal to run on a wifi server, but it would be really impractical to rearrange things to hardwire it, I have a lot of bandwidth, and there won't be a lot of computers using this all the time or anything so I wanted to try.

I cannot figure out how to get computer C to read computer B server.  Computer A (hardwired) will connect fine but not B, so bascially wifi to wifi isn't working.  Haven't bothered trying with the Tailscale connection to B yet until I can get all my local devices to connect.

Computer B Jellyfin server is showing as a 127.x IP.  As I understand it that is a loopback address and I should use the 192.x address.  I attempted to put the 192.x into the "bind to local network address" and restart, but I can't seem to get computer C to connect, and computer A will still only connect using the 127.x IP.

Help would be appreciated, thank you!

[TheDreadPirate]

If you leave the "bind to local address" field blank Jellyfin will bind to all available interfaces.

Do you have AP Isolation turned on in your router's config?

[TheWanderingMage]

Thanks for the reply!

I'm going to consider this solved, I'm guessing your recommendation is what fixed it, but see details below.

Changing the AP Isolation setting on my Netgear AC1750 seems to have bricked the router. Factory reset was not effective, my only option was to do a long drawn out process to try and re-flash the firmware downloaded from their site. That seemed like more effort than it was worth. That router had been giving me software/firmware issues for a year or more now and I always hold my breath when I have to go in there and change anything. It was very iffy if I could even login to the router settings at all. Trying to reflash the firmware seemed like something I didn't have the heart to do.

If there were pictures available, as part of my solution I was going to show myself office spacing that router:P It is kind of garbage that changing 1 setting in a router is capable of soft locking it, almost like they wanted me to buy a new router, hmmm.... I will not be buying netgear routers going forward.

So... I updated to a TPLINK BE6100, hopefully they will be better than Netgear. I changed the IP isolation setting once it was up and running (BTW, this was a simple click and save on this router, and didn't require a whole reboot/reconfigure process like the netgear attempted and failed at).

I did have to go back in and set my network setting on the new target server back to private after connecting to the new wifi, but after that I was able to connect on both computer using the 192. IP address of the wifi server.

I believe that had I been able to successfully change the Netgear to AP Isolation it would have solved the issue, but I can't rule out that something else in the new router helped.

Thanks again for your assistance!