Network problem when connecting from within my local network

[lemayp]

Hello everybody,

I am currently facing a problem contacting my local subsonic server from the apps or from the browser when the contact is being done from within my local network, but now when I contact it from outside my network.

For instance, lets assume the following facts to help understanding:

My server url is : mysite.subsonic.org (not true name)
My IP : 173.2.3.4 (not true)
The subsonic is running on machine with local ip of : 192.168.100.2

Here is what is WORKING:

Contacting subsonic using mysite.subsonic.org from the machine hosting the subsonic server. The ip adress is somehow change to an adress that look like 169.x.x.x.

Contacting subsonic using mysite.subsonic.org when done from a computer outside of the house (outside of my network)

contacting subsonic from an apps when the device running the apps is located outside of my network.

Contacting subsonic using the ip provided by my ISP (http://173.2.3.4:8080) when the device attempting to connect is located outside of the local network

Contacting subsonic from another computer located in the house/same network using the local ip address assign to the server (192.168.100.2:8080)


Here is what is not working

Attempting to connect to mysite.subsonic.org from another computer in my house. The computer also receive an ip of 169.x.x.x instead of the real 192.168.100.2 and is not able to connect.

Attempting to connect using any subsonic apps running on phones connected to my network (they all try to connect to mysite.subsonic.org).

Attempting to connect to subsonic server using the IP provided by ISP: (173.2.3.4:8080) from a device connected on my network.


So it looks like any devices connected locally to my network are not able to connect to subsonic if the router is involved. I think this occurs when an optimization is attempted somehow to convert the external IP by a local one, and the local one is not properly set to (192.168.100.2) but instead to (169.x.x.x).

I don't know who could have generated such ip adress of (169.x.x.x) and why.

Anyone could be able to help?

[gurutech]

The 169.254.x.x IP address is assigned automatically by Windows (or other OS) when it can't obtain an actual IP address.

The first thing you can do is hardcode an IP address within your 192.168.x.x scope, and if that doesn't work, then you may have a network card or router problem (or whatever device assigns your IP addresses.

[GJ51]

Your router isn't giving the server a valid ip address inside the network.

The ip adress is somehow change to an adress that look like 169.x.x.x.

Indicates that the server is generating a fallback ip on it's own and not getting the ip address from the router.

You can go into the adapter settings and manually input the ip address or try to find out why DHCP isn't getting an address to the server.

[lemayp]

Thanks to your reply, I have found something but not yet know how to resolve the situation.

The subsonic server is using a static IP address reserved inside of the router. This is working well as I can see the ip of the machine properly with ipconfig, as well as on the router when checking the connected device. The problem is "elsewhere"...

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::dd8e:72f:adc2:6fe2%11
IPv4 Address. . . . . . . . . . . : 192.168.1.102 <-----------------This is good
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

I am using VMWare on this machine for other things than Subsonic. The ipstat command show me the following regarding the VMWare Network adapter:

Ethernet adapter VMware Network Adapter VMnet8:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::ddc1:932d:3bae:63da%20
Autoconfiguration IPv4 Address. . : 169.254.99.218
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :


The IP address that we see here (169.254.99.218) is exactly the same as being used when the connection is optimized to use the local network instead of passing by the web (mysite.subsonic.org).

Anyone knows who/what components perform the optimization, i.e. detect that the subsonic server is running on a local network area and switch to it? Any way to disable the optimization OR force it to use the 192.x.x.x address instead of the 169.x.x.x one? I wouldn't mind hardcode the ip 192.x.x.x inside of subsonic since it is already a static address elsewhere.

Thanks.

[lemayp]

Problem resolved... As you have suggested it, the IP value 169.x.x.x was being used by VMWare network adapter because it was set to use a "static" IP that was not valid for the current network. Not sure why it was like that, but I have changed it to obtains its IP address automatically and that resolved the whole situation.

Thanks for the great feedback and help.