Search the Community

I am trying to get a handle on the differences between Plex and Emby. I have been using Plex for sometime and am considering switching to Emby. What I am trying to confirm is whether a remote Emby client can access my home server when it is behind a double NAT scenario. My server is behind my router (which is obviously using NAT). But, in my case, my network service provide also uses NAT in front of my router (WAN side of my router) or rather the router they provide me to connect to their Internet service. Because this is the case they have one router somewhere in their network that represents a number of their clients (me included) with one public IP. I obviously have no access to that router. So adding port forwarding is not an option. An interesting thing with Plex is that when you make a connection to my server by logging into the company Plex server (plex.tv) with a web browser or a Plex app that these apps can access my server even though it is behind this double NAT scenario. The only way this can work is that the plex.tv server has the client port number my server uses to access my account on plex.tv and relays that info to the client app that is trying to make a connection. Then the client app attempts a direct connect using that client port number or relays through the plex.tv server. I assume that Emby server does not offer such a feature. Because so far I cannot make this work. When I log into Emby Connect it shows my server but when I click on it it fails the connection. So, I am assuming all the Emby Connect is doing is a translation from a name to an IP address (similar to the way DNS works). Incidentally, TV's running the Plex app are unable to connect (just like Emby apps). I am assuming that is because the Plex TV apps (or Emby apps) try to make a direct connection to the server at it's known server port number (and are unable to make a connection using the client port number as in the Plex case). Does this all make sense and am I right in my analysis?