Listing wrong local IP address

[roberthleeii 61]

My server is listing the wrong local IP address, and this is stopping me from being able to use MB connect to login when I am at home. What ever IP address it is listing works from my computer as well as the one right one, but only the right one works from other devices around in my house. Any help fixing this would be much appreciated.

[JeremyFr79 228]

are you running multiple active NIC's on your server machine?  If so check the binding order for your NICs, or you can also uncheck "automatic metric" under the advanced settings for each NIC and assign the correct order manually.

[Chomicz 2]

Mine's showing the right internal IP but the wrong external, anyone know of a fix for the latest server version 3.0.5621.4?

[Luke 42080]

Mine's showing the right internal IP but the wrong external, anyone know of a fix for the latest server version 3.0.5621.4?

 

there's no problem or fix. maybe your external ip changed and it hasn't reacted yet. sometimes in some setups this is an inexact science. you can always go to advanced -> hosting and fill in the external address yourself

[techywarrior 689]

I don't know if this is the problem that any of you are having but since IPv4 addresses are running out and ISPs aren't able to request enough new ones to fill their need they have resorted to creating an "internal network" that encompasses a node, neighborhood, city, etc.

 

In the simplest terms this acts like how your internal network is setup. In your internal network your router is assigned a real IP address and gives all your computers/devices a special IP address for internal use (192.168.x.x or 10.x.x.x etc.). When you are on the internet all your devices/computers have the IP address of the router and it uses NAT to send the right data to the right device.

 

Well, the ISP is doing the same. They can't afford to give each router an IP address so they assign a real IP address to "router" that your street/block/etc. connects to. That "router" then assigns your router a special IP the ISP is using for internal use and the rest of the logic follows like above.

 

The problem however is that the IP that your router gets IS NOT the IP that is used on the internet by your computer/device anymore so you can't connect to your server. Not only that but because there is double NAT going on it's very difficult to connect to computers inside your network as you never know what port the data is going to come in on from the ISP's NAT (so your port forwarding fails).

 

 

 

This may not be what your problem is right now (hopefully your problem is much simpler) but it is something that ISPs are starting to do and I feel in the future this is going to become a much bigger issue not just for Emby but anyone trying to connect to servers at home. IPv6 will solve this problem but we are still a long way from all the ISPs using IPv6, assigning blocks to users, and having users internal networks all setup properly for it.

[Chomicz 2]

there's no problem or fix. maybe your external ip changed and it hasn't reacted yet. sometimes in some setups this is an inexact science. you can always go to advanced -> hosting and fill in the external address yourself

All fixed cheers for this.  Just looked at my router logs and my external IP changed about the same time as the update.  Clearly I put 2+2 and got 5.  Nonetheless Emby not updating its external IP for 3 days is strange.  Then again, if I understood the above post I think that explains the problem I was having.

[techywarrior 689]

All fixed cheers for this.  Just looked at my router logs and my external IP changed about the same time as the update.  Clearly I put 2+2 and got 5.  Nonetheless Emby not updating its external IP for 3 days is strange.  Then again, if I understood the above post I think that explains the problem I was having.

No, I think you are lucky and didn't have the issue I described. I'm pretty sure if you did then you wouldn't be able to make Emby work remotely without help from your ISP or more.