Can connect via internet but not locally over WiFi

[jackmail]

Problem Description: Everything seems to be working with my setup, but for some reason when I turn ON WiFi on my Android phone I cannot connect anymore. I tried referencing the local computer's nat ip directly, with port and without to no avail. When WiFi is turned off I connect via internet no problem. Weird- in general I face the opposite issue...
Troubleshooting Steps: I can connect via a browser to the local IP http://192.168.0.100:4040 no problem. I tried using the internet URL which works on GMS, different combinations of names and ports but Test Connection never works. I'm using Kaspersky AV and Internet Security but I turned it off and it didn't fix the local issue.
Playback Application and version: not really important. Haven't got there yet
Subsonic Version: 4.8 (build 3434) – April 17, 2013
Server Version: jetty-6.1.x, java 1.7.0_25, Windows XP (102.7 MB / 130.4 MB)
Hardware Platform: Windows XP
Java Memory Limit: 91MB
Problem Filename: N/A
Output from ffmpeg -i: N/A
Last ten log file lines:


[12/22/13 9:15:47 PM PST] INFO DaoHelper Checking database schema.
[12/22/13 9:15:48 PM PST] INFO DaoHelper Done checking database schema.
[12/22/13 9:15:48 PM PST] INFO PlayerDao Deleted 3 player(s) that haven't been used after Wed Oct 23 21:15:48 PDT 2013
[12/22/13 9:15:49 PM PST] INFO MediaScannerService Automatic media library scanning scheduled to run every 1 day(s), starting at Mon Dec 23 01:00:00 PST 2013
[12/22/13 9:15:49 PM PST] INFO PodcastService Automatic Podcast update scheduled to run every 24 hour(s), starting at Sun Dec 22 21:20:49 PST 2013
[12/22/13 9:16:00 PM PST] INFO PlayerDao Created player 3.
[12/22/13 9:16:00 PM PST] INFO VersionService Resolved local Subsonic version to: 4.8
[12/22/13 9:16:00 PM PST] INFO VersionService Resolved latest Subsonic final version to: 4.8
[12/22/13 9:16:00 PM PST] INFO VersionService Resolved latest Subsonic beta version to: 4.9.beta3
[12/22/13 9:18:03 PM PST] INFO NetworkService Successfully forwarding port 4040.
[12/22/13 9:20:49 PM PST] INFO PodcastService Starting scheduled Podcast refresh.
[12/22/13 9:20:49 PM PST] INFO PodcastService Completed scheduled Podcast refresh.
[12/22/13 9:23:33 PM PST] INFO PlayerDao Created player 4.
[12/22/13 10:18:06 PM PST] INFO NetworkService Successfully forwarding port 4040.

[alphawave7]

Before doing anything else, it helps to delete all the settings for 'Home' server in the Android app, and start again. Use your server IP:port, and double-check your login details. As long as your phone enters the same subnet as the server, you should connect.

[jackmail]

Thanks for the help.

I deleted everything and started over. No joy...

Can't figure what I am doing wrong...

[jackmail]

Tried to verify the open port from my Android device and it can see the port is open:

--- Dec 22, 2013 11:40:20 PM
--- IP (wlan0) fe80::1e99:4cff:feac:f4f0%wlan0
--- IP (wlan0) 192.168.0.109

Check ports on 192.168.0.100

Port 4040 : open

[jackmail]

Also, if I put the wrong password it tells me the password is wrong instead of the "Connection failure" error so it is definitely hitting the server

[jackmail]

Bump

[ytechie]

Also, if I put the wrong password it tells me the password is wrong instead of the "Connection failure" error so it is definitely hitting the server

Now I am intrigued.

Just to double check, have you configured your Android device to connect to the private IP address and port of the Subsonic server as opposed to the public NATed IP address and port? (This is a troubleshooting step and should only work when connected to the local network.)

[jackmail]

have you configured your Android device to connect to the private IP address and port of the Subsonic server as opposed to the public NATed IP address and port?

Not sure. Sorry my lack of knowledge. How do I distinguish between the two?

Thanks for taking the time to help.

[ytechie]

The private addresses are in the range 192.168.0.0/16, 172.16.0.0/12, and 10.0.0.0/8 (RFC1918). These are the addresses handed out via DHCP to machines on your LAN.

The public address is the publicly routable IP address, sometimes known as your WAN address. This address is what everything gets NATed to.

Does this help?

With pleasure,
Yosef

[jackmail]

That's what I thought. Thx.

I can never connect using the private address. When using the public address i can only connect if i turn wifi off. Never with wifi on.

[ytechie]

You should be able to connect with the private address when connected to the WiFi.

However, if you are connected to the WiFi and you try to access the Subsonic server using the external address, your router may not loop the traffic back to the inside. Remember that if you use the outside address, NAT needs to translate the addresses to properly reach the server. If you send a packet from the inside to the outside address, the router needs to translate the packet, and send it back into the network. Some routers do this, others don't. Mine will do the translation only if the inside and outside ports are the same; if it needs to turn port 4040 on the outside into port 80 on the inside, NAT will only work from the outside, forcing me to either use the local address when connected to WiFi, or turn the WiFi off.

You mentioned that you can not connect to the server using the local address and port. Let's check that out.
Can you verify the local address and port?

In your first post you mentioned that the address is 192.168.0.100:4040. Try using that on your phone when connected to the WiFi.

[jackmail]

On my browser using wifi i can hit http://192.168.0.100:4040 and get the website no problem on the mobile device or on any networked computer

[ytechie]

So the only issue is when using the external IP address while connected to the WiFi?

[alphawave7]

http://en.wikipedia.org/wiki/Network_ad ... T_loopback

Even I have to read this one slowly to fully understand it, take your time. I solve this by having a 'Home' server entry (192.168.x.x:4040) and an 'Away' server (my subsonic.org addy).

Welcome back Yosef..6 months is a long time for a ytechie fix.

[jackmail]

Nope. Using wifi on the internal Nat address doesn't work either.

In summary: using wifi I can't connect internally or externally using the application. Using the browser I can connect no problem.

With LTE I can connect via public address using the app or the browser.