Remote Access Intermittent

[Luke 42078]

How are the lan ip addresses different then?

[dalezjc 14]

Same IP, different port, but I have Plex turned off while running Emby.

[Happy2Play 9780]

1 hour ago, dalezjc said:

Same IP, different port, but I have Plex turned off while running Emby.

But ports are forwarded to different IP address so they can't really be the same machine.  Unless there are multiple virtual machineson the same host.

Edited December 7, 2022 by Happy2Play

[Luke 42078]

@dalezjc yea that's what I'm curious about. If Plex and Emby are on the same machine, then those port assignments should be forwarding to the same local ip address, right?

I think one of those ip addresses is probably wrong. What does the server dashboard show as your local LAN ip address?

[rbjtech 5284]

On 05/12/2022 at 18:57, rbjtech said:

if your emby server is 10.0.0.136 - then that should be ok.
Plex is on 10.0.0.83 - either a different machine or different IP yes ?

 

..and this is exactly why I queried it a few days ago - and had confirmation it was a different IP/different host.

@dalezjc IF you are running Plex and Emby on the SAME machine - and it has a SINGLE IP address (10.0.0.83) - then you simply need to change the router forward to point to this address as well - but using the emby Port - 8096.

However - if this machine has multiple IP addresses (maybe you have multiple NIC's) - then you can also FORCE Emby to use the 10.0.0.136 address by adding that in the network section.  THEN the router forwarding can stay the same (to the .136 address). 

In this example (my own), in the Local IP address box - I force emby to bind to 192.168.30.100 - as my own host has multiple LAN interfaces.  I also force other VLAN's to be classed as 'local' but you will probably not have to touch the LAN networks box - leave it blank.

An ipconfig /all will show all the IP's and interfaces in use or netsh interface show interface will give a cleaner view.

Edited December 8, 2022 by rbjtech

[rbjtech 5284]

10 hours ago, Happy2Play said:

But ports are forwarded to different IP address so they can't really be the same machine.  Unless there are multiple virtual machineson the same host.

They can if the host has multiple LAN interfaces - you don't need a VM just to have multiple IP's on the same hardware ..

Mine are either trunk VLAN's or on separate untagged VLAN's - but you can have IP's on the same subnet - but it does cause potential priority and routing problems as shown here.   You can either set the interface 'priority' in the windows settings - or just force bindings on the host.

But we need clarity on what interfaces the user has before advising further ..  

Edited December 8, 2022 by rbjtech