Updatitis

[jackthedoc 12]

Suffering from an acute case of pre-Christmas "update" everything, I replaced my D-Link Covr 2200/1200 mesh network with a new Wi-Fi 6 enabled D-Link Eagle mesh.

My current Emby server resides on a window 11 machine with several HDDs (attached to it via USB) holding my libraries.

Up until the mesh replacement, I could stream my Emby library to the relevant Emby app on my "Chromecast with Google TV 4K" / "Apple TV 4K" / "Intel i7 NUC" (running Windows 11) all attached to my smart TV via HDMI and I could stream the content to standalone devices such as my iPad Pro.

The fact that all my video services stream as well post-upgrade as they did pre-upgrade suggests that the mesh Wi-Fi routers are not causing my inability to stream Emby content, but that the problem lies somewhere in the Emby apps' inability to access the server.

Is this assumption correct? If it is (or even if it's not) how do I overcome this?

I bet this question has been asked before, but I don't have the vocabulary necessary to create a search string to look for these answers "on site".

Thanks for reading and Happy New Year to all

John Norris
(Australia)
 

[ebr 16185]

15 hours ago, jackthedoc said:

The fact that all my video services stream as well post-upgrade as they did pre-upgrade suggests that the mesh Wi-Fi routers are not causing my inability to stream Emby content, but that the problem lies somewhere in the Emby apps' inability to access the server.

Hi.  Yes and no... it does sound like your apps cannot reach your server but that very well may be due to settings in your new network setup.

Start simple - bring up a web browser on a machine/phone on your local network but not the one running the server.  Can you access it?

The first thing I would confirm is that Windows did not mark your network as "Public" when you updated it.  Make sure it is marked as "Private".

[jackthedoc 12]

Thanks for that. I examined the problem a bit more analytically over the last few days, and I feel that the issue must lie somewhere in the D-Link mesh wi-fi's sanctum sanctorum.  The D-Link units have created a home network in which every wi-fi-enabled device can access the internet on its own behalf (streaming apps on my Apple TV 4K, my Chromecast with Google 4K TV, my Intel i7 NUC can import the required data and play videos) but communication between the hardware devices has been blocked.  I can no longer print from my wi-fi enabled laptops to my wi-fi linked colour laser printer; I cannot access the Emby server - located on my desktop PC - using the appropriate Emby apps on my Apple TV 4K, my Google TV 4K, my Windows 11 NUC etc.  My iPhone can no longer communicate with my BluOS Node 130 music streamer.

So there must be a setting within the mesh network that is acting like a firewall, preventing device to device communication.

So I suppose I'll have to get in line and try to contact the D-Link Help Desk for further information, as it does not seem that my current issue is an Emby malfunction per se.

Regards and a Happy New Year to you

 

John Norris

[ebr 16185]

Please let us know what you find.

Happy New Year.

[Q-Droid 989]

That sounds like wifi isolation - treating all wireless devices as if they were guests or connected to a guest network. 

Look for isolation related settings. 

 

[ebr 16185]

6 hours ago, Q-Droid said:

Look for isolation related settings.

Like this, did you check it?

On 12/27/2022 at 9:16 AM, ebr said:

The first thing I would confirm is that Windows did not mark your network as "Public"

 

[jackthedoc 12]

According to your instructions, I set it to "private" network even though "public" is recommended by windows... correct?

Still can't stream from the server to any of the installed Emby apps (iPad Pro, Intel i7 NUC or either the Chromecast with Google TV or Apple TV 4K).

I'm becoming more and more convinced that there is a glitch in the Mesh network set up, somewhere; but I just can't identify where this might be.  I am "waiting" for a call from a more senior D-Link technician to work through this issue, but I am not very optimistic.  I am strongly tempted to stick a pin in all 4 Eagle Pro units to return them to factory defaults and start all over again with the network wizard.

Aaaaghhhhh

[ebr 16185]

1 minute ago, jackthedoc said:

I set it to "private" network

So, it was set to a public network?

2 minutes ago, jackthedoc said:

even though "public" is recommended by windows... correct?

No, not for a network in your home.  Your firewall has two different "modes".  One for a private network (assumed to be in your home where you know exactly who is connected to it) and one for a public one (assumed to be at Starbucks where everyone can connect).  If the network was set to Public then just about everything would be blocked by the firewall.

[Happy2Play 9782]

If no LAN device can connect to Emby it could be Firewall rules.  What are you firewall rules for Emby?

You could shut down Emby, delete all Emby firewall rules, open the Emby system.xml and change <IsPortAuthorized> to false, and start Emby to reauthorize Emby.

 

But yes there is a change it could be your Mesh network.

[Q-Droid 989]

1 hour ago, ebr said:

Like this, did you check it?

 

I meant at the new mesh router/system since non-Windows devices were also not able to connect other non-Windows devices. But yes, as a new network the Windows mode is also very relevant.

 

 

[jackthedoc 12]

To ebr: Thanks, yes I did set it to private from public network.  Windows does confuse me, sometimes.  It clearly says "preferred" for public network even on my desktop. Am unlikely to drag it along to the local "subway" or "mcdonalds" to do a few word-processing chores.  It may be teaching one's grandmother to suck eggs at times, but perhaps consideration should be given to the intelligent, albeit IT inexperienced, user when it comes to things like default settings. Concrete examples rarely go astray.

And to happy2play thanks, also.  A recreation from scratch of firewall rules would also be an attractive option.

So much to do, so little time to do it.

[Luke 42080]

@jackthedoc were you able to resolve this?

[jackthedoc 12]

I purchased a new (non D-Link) router and a companion (same manufacturer) mesh network system to replace my "upgraded" D-Link set up; followed the steps as outlined in the iOS app and ... Bob's your uncle. Everything that is capable of being connected to the internet is now connected, and all the devices in my "intranet" talk to each other.  Ofttimes we blame the wrong thing for our problems and forget the aphorism KISS.

Thanks for your interest, however, and keep up the good work at the Emby end of the equation.

Regards from DownUnder,

John Norris