Connection inside different local network

[nico_paparazzo 0]

Hello, 

My issue is that I can't connect Emby app to my server when I am on different local network. 

My network architecture is the following one : 

 External world -> B-Box -> Router asus -> NAS

x.x.x.x -> 192.168.1.1 -> 192.168.50.1 -> 192.168.50.x

Actually, I have my NAS is a local network 192.168.50.x given by my Asus router.

Everything is working fine when I try to acces from external world to the Emby app.

Everything is working fine when I try to acces from 192.168.50.x network.

Impossible to perform a connection when I am connected on the network 192.168.1.x

I am running Emby on a Synology NAS with the last available Emby version 4.8.8.0 from package center.

I have tried from a chromecast and from a samsung tablet but it does not work.

Do you have any idea ? maybe a parameter to set.

[Clackdor 109]

This sounds like a networking issue and not necessarily an emby issue.

From your description it sounds like you have a double NAT situation. The only way devices on the outermost 192.168.1.x network can be aware of the devices in the innermost 192.168.50.x network is to setup static routes or access your server via a domain name/hostname and have a local DNS entry set to point to the 192.168.1.x address assigned to the wan of the innermost router.

The ideal approach would be to get away from double NAT altogether and either have everything on the same router/subnet or only have a single router handling multiple different subnets by using VLAN's if your router and switches support it. 

[nico_paparazzo 0]

Hi Clackdor, 

I think too to a network issue but as I am not an expert on it, I prefer to ask  

Actually the first router (bbox) is in DMZ. 

Don't know if this can help. 

I have set a domain name/ hostname and I can access it from external world with issue. 

But from 192.168.1.x to the 192.168.50.x does not work, I try with the IP and domain name but same result.

Any idea ? 

 

[Clackdor 109]

4 hours ago, nico_paparazzo said:

I have set a domain name/ hostname and I can access it from external world with issue. 

But from 192.168.1.x to the 192.168.50.x does not work, I try with the IP and domain name but same result.

Like I said above, in order for this to work you would have to have a local DNS server in the 192.168.1.x network that resolves to whatever 192.168.1.x address the innermost router is getting as it's wan connection. Alternatively you can try directly connecting to that address as it should work that way as well.

None of this is really ideal from a usability standpoint and you'd be much better off simplifying your networks so that everything can talk to each other properly.

[nico_paparazzo 0]

I will look for the DNS server and come back to you

[Lessaj 467]

Your upstream network doesn't know how to direct traffic to your downstream network. You basically need to add a static route for 192.168.50.0/24 to be routed via 192.168.50.1 on your BBox, otherwise your Asus router needs to act more like a switch/wireless access point and let the B-Box handle DHCP.

Might need a firewall rule on the Asus router even with the static route too.

Edited December 30, 2024 by Lessaj