Subsonic Forum

Hi everybody and thanks for taking the time reading about my issue.

I set up Subsonic in my Pc and forwarded the Port 4040 like it is adjusted in subsonic as well. The IP of the Pc subsonic runs on is static as well, let´s say 192.168.AAA.BBB
I checked my ip address via http://www.whatsmyip.org/ and http://whatismyipaddress.com/ - it´s like 9X.9x.XXX.XXX
I can now reach Subsonic from 2 other windows pc´s via 9X.9x.XXX.XXX:4040 OR 192.168.AAA.BBB:4040
from anroid Tablet with the app subsonic and also http://9X.9x.XXX.XXX:4040 OR 192.168.AAA.BBB:4040
from iPhone with the appSubStream http://9X.9x.XXX.XXX:4040 OR 192.168.AAA.BBB:4040 (first i thought it doesn´t work here but the app is just shit and works best with playlists)

In Subsonic I configured a easy-to-remeber address like 12345MyTest.subsonic.org and it says responded succesfully..
But if i put in that address in any of my clients it trys to connect to a totally different Ip than mine 9X.9x.XXX.XXX - it connects, or better trys to connect to an Ip of my HomeNetwork 192.168.XXX.XXX:4040 - this would work if it wouldn´t be the wrong IP. It should connect my to the Static IP 192.168.AAA.BBB or to my outside IP 9X.9x.XXX.XXX.

I renewed that easy-to-remeber address several times, but always the same failure.

Any Ideas why?


Thanks in advance.
Richard

Does it remain after a router reboot?

I just recognized that the IP which i get routed to via the easy address is the FIxed IP of my LAN in the same PC.
So it takes that instead of the wireless Lan Static IP to the Internet.

Known issue. For some reason when you are on the same local LAN, you cannot use the xxxxxxx.subsonic.org address - it will always resolve to the local IP of the computer you are on (not necessarily the server's IP).

The only way around it I have found is to use another DNS service, like DynDNS, or No-IP.com.

gurutech wrote:Known issue. For some reason when you are on the same local LAN, you cannot use the xxxxxxx.subsonic.org address - it will always resolve to the local IP of the computer you are on (not necessarily the server's IP).

The only way around it I have found is to use another DNS service, like DynDNS, or No-IP.com.

This works for me..I thought this was the infamous loopback problem caused by some routers. Once the server IP is fixed, both LAN and WAN access should succeed using the 'easy to remember' url, granted changes sometimes require a day or so to update the reg server. I guess I still don't understand OP's problem, and it may help to simply say WAN IP/Server IP/LAN client IP to keep it simple...