Page 1 of 1

Can stream via browser but cannot via isub

PostPosted: Thu Jan 06, 2011 3:01 am
by grnidb
Hello just finished configuring Subsonic 4.2 on Ubuntu 10.10. I am unable to stream to my iphone via isub 2.2.3. I get the following error:

Error
Either the subsonic URL is incorrect, the subsonic server is down, or you may be connected to Wifi but do not have access....
Error code 1:
Connection Failure

From the phone and PC I am able to browse to http://name.dysdns-ip.com:4040 via safari and login with the same address and credentials that I have populated in isub. Any possible tips or pointers would be appreciated.

Thanks

PostPosted: Thu Jan 06, 2011 3:44 am
by GJ51
Does it work on the demo server?

PostPosted: Thu Jan 06, 2011 4:46 am
by grnidb
Hi GJ51,

isub did work on the demo library.

PostPosted: Thu Jan 06, 2011 8:27 am
by GJ51
Therefore, somethiong about your network configuration is causing a problem, or your DNS address is not right. Identify your external IP address, then try to connect using that plus the port address.

e.g.

http://24.88.76.61:4040

Change the example to your IP address issued to you by your ISP then add the port number you assigned to Subsonic and try to connect through iSub

PostPosted: Thu Jan 06, 2011 7:50 pm
by grnidb
Doh thanks Gary you made me go back in and double check my setting and it appears I forgot to set a static ip and my internal address changed after I tested it.

PostPosted: Thu Jan 06, 2011 9:15 pm
by GJ51
That's the reason I always tell everyone to set a fixed internal IP up high out of the way of DHCP. I've even seen some routers assign two different computers the same internal IP occasionally. If you set everything in stone maunually it really helps cut down the number of times you end up chasing your tail on the same issue.

PostPosted: Thu Jan 06, 2011 10:46 pm
by alphawave7
GJ51 wrote:That's the reason I always tell everyone to set a fixed internal IP up high out of the way of DHCP. I've even seen some routers assign two different computers the same internal IP occasionally. If you set everything in stone maunually it really helps cut down the number of times you end up chasing your tail on the same issue.


Furthermore, if everyone learned how to manually assign IP's to their lan/wlan's, it would put networking gurus out of business overnight. DHCP and it's issues keeps them employed! :p Seriously though..most folks only have a half-dozen devices or so...why not map it out and configure it yourself? Then you'll always have an accurate map of every device's IP, in a static state. Remote/telnet/ssh into any device at whim. 8)

PostPosted: Thu Jan 06, 2011 11:58 pm
by GJ51
And it ain't like the home network is gonna get smaller and simpler over the next few years. The fact that there are over 5,000 members on this forum has to tell you something about where the home networ is heading. Anyone who can figure it out now, will be ahead of the curve.