Server setup went fine but can't connect from EVO

[baskie]

Yes your right, I have the flavors backwards. When I changed the /etc/default/subsonic when restarting the service it would change the file back to default settings. Then I did find / -name "subsonic" -ls to find all the files on the server that subsonic used. I found the /usr/bin/subsonic and changed the port at the very top of the file to 80. At that point i restarted the service and gave it 30 seconds or so for everything to get back in sync and then tried to connect with my phone and everything work great at that point. What it looks like to me is the android app is staticly set to look on port 80 but the server out of the box is set to run on 4040. Just make sure you have the ports on your router/firewall open

[werewolves]

Yeah, I edited /usr/bin/subsonic, but no dice. I even went in and manually forwarded by ports (even though it tells me in that automatic port forwarding was successful).

I still get "Status: ****.subsonic.org is registered, but could not connect to it. (ConnectTimeoutException)", and I can't connect from the EVO.

[baskie]

Just wondering... have you tried to ping your domain from subsonic to see if its pointing to your IP address? Maybe their servers are running a little slow on updating its dns and its not pointing to you yet. Just another though

[werewolves]

Well, when I ping, it comes back from 97.74.125.134. That's definitely not my machine. Hmmmm.

[baskie]

is that your external ip from your ISP not your local network?

[Headcase_Fargone]

I'm running Subsonic server on Ubuntu 10.04 and the Android app on my Evo and it's working just fine. Sounds like you guys are having issues with your port forwarding. I saw someone mentioned automatic port forwarding but I don't think I'd trust that.

Just manually forward port 4040 on your router and point it to the internal network IP of the Ubuntu box.

Also, the server address in the Android app needs to include the :4040 at the end.

[werewolves]

baskie: no, that's not my external address, it should be 172 something.

headcase: I'll give it a try, maybe that's the magic combo...

[werewolves]

Holy sheep, it works! Thanks for all the help!

For the record, the winning combo was the default port 4040 on the server end, manual port forwarding on my router, and no port following the server entry on my EVO.

So far, my only remaining concern is that I get a fair amount of stutters in the streaming. Are there any settings that can mitigate that?

Thanks again

[werewolves]

Here's another odd issue. I can connect fine from 3G, but from 4G it won't connect.

Anyone know if Sprint is blocking more 4G ports or something?