Works/connects in Win7, but not in Ubuntu, same network...

[greenzee]

I've successfully setup Subsonic on my Win7 machine, and able to stream music to my Android phone and my Ipod Touch. Seems as though Subsonic or port forwarding kills my web connection on this machine for some reason, but that's a question for another day.

Because of this (slow web) I have also installed Subsonic on an Ubuntu 9.04 machine. It appears to successfully setup port forwarding to 4040 in the network settings, but when it attempts to contact my personal Subsonic.org server (I donated for permanent access) I get a "my user name.subsonic.org is registered, but could not connect to it. (ConnectTimeoutException).

I uninstalled Subsonic on my Win7 box, and reset my router, but still getting the above message on Ubuntu. Reinstalled to my Win7 machine, connected immediately.

I also changed the port from 4040 to port 80 on Ubuntu, as on my Win7 machine that works, but I get the same message as above.

Hoping someone can point me towards a solution, likely that I am missing an obvious setting in Ubuntu.

Thanks for any and all assistance!

[kermit22]

At first glance it sounds to me that your router's port forwarding is still trying to point to your windows 7 machine. Are you doing port forwarding manually or with uPnP?

[Kirk]

I concur with Kermit22.

Can you please try to connect to the Subsonic server(s) using their LAN IPs from inside your network, and tell us whether you are able to contact them or not?

To find your IP address on the LAN, open a terminal\command prompt...
In Windows: Run "ipconfig". Look for the Address of Local Area Connection.
In Linux: Run "ifconfig". Look for the Address of eth0.

Most home networks are in the 192.168.*.* IP range.

Cheers,
Kirk

[greenzee]

I concur with Kermit22.

Can you please try to connect to the Subsonic server(s) using their LAN IPs from inside your network, and tell us whether you are able to contact them or not?

To find your IP address on the LAN, open a terminal\command prompt...
In Windows: Run "ipconfig". Look for the Address of Local Area Connection.
In Linux: Run "ifconfig". Look for the Address of eth0.

Most home networks are in the 192.168.*.* IP range.

Cheers,
Kirk

I am using uPnP (I assume), allowing Subsonic to set this up for me, and it indicates "Status: Successfully 00forwarding port 4040" on my Ubuntu box.

My internal IP (eth0) is 192.168.1.104

I'm sorry, but I'm not sure what you mean by trying to connect to the Subsonic servers using their LAN IP's. If I attempt to browse to 192.168.1.104 internally I get nothing, if that is what you mean?

I see nothing in my router settings indicating port forwarding is even enabled for Subsonic. Shouldn't there be an entry I could delete in the router config?

Thank you for your help.

[Kirk]

Try browsing to http://192.168.1.104:4040/ internally before you mess with your router settings...

Cheers,
Kirk

[greenzee]

Try browsing to http://192.168.1.104:4040/ internally before you mess with your router settings...

Cheers,
Kirk

I am able to successfully browse to the above address internally and login to the Subsonic server.

Does this verify there is a router/port forwarding issue?

Thank you for your help!

[greenzee]

Try browsing to http://192.168.1.104:4040/ internally before you mess with your router settings...

Cheers,
Kirk

I am able to successfully browse to the above address internally and login to the Subsonic server.

Does this verify there is a router/port forwarding issue?

Thank you for your help!

Also, I'm not sure if this means anything, but I can log into my local server via 127.0.1.1:4040. I restored my router to default and noticed every setting that was deleted, including a Subsonic firewall rule that referenced 127.0.1.1.

That said, a little bit of searching the forum I see a lot about 127.0.0.1, but not 127.0.1.1. Is there something I need to change in a config or file to point to 127.0.0.1 instead?

[Kirk]

127.0.0.1 is always "the address of the computer you're sitting at". You should NEVER forward a port to 127.0.0.1 since that's the IP of the router that's doing the forwarding.

I'm not sure where 127.0.1.1 comes from. It could be a local IP but it probably isn't since your network runs on the 192 range.

Can you try manually forward port 4040 to 192.168.1.104?

Cheers,
Kirk

[greenzee]

127.0.0.1 is always "the address of the computer you're sitting at". You should NEVER forward a port to 127.0.0.1 since that's the IP of the router that's doing the forwarding.

I'm not sure where 127.0.1.1 comes from. It could be a local IP but it probably isn't since your network runs on the 192 range.

Can you try manually forward port 4040 to 192.168.1.104?

Cheers,
Kirk

I'm not sure where the 127.0.1.1 comes from either, it's weird. I can't even delete the entry in my Trendnet router (TEW432BRP) unless I reset it to defaults.

Oddly enough the manual port forwarding documentation I have found online indicates I can't port forward with this router unless I have a static IP. Even though I have a subsonic.org address, can I still have a dynamic IP locally (192.168.1.104)? I've noticed depending on what workstations I have on my network the IP of my Subsonic machine goes from 192.168.1.103 or .104.

Thanks for the help guys, I appreciate it, and I'm learning from it.

[mgrant]

Manually forwarding the port requires you to specify an internal IP address. So, if the computer's address is dynamic you'd need to manually update the forwarding rule every time it changed.

The 127.0.1.1 address comes from your hostfile. It probably looks something like this:

Code: Select all

127.0.0.1 localhost
127.0.1.1 <your_host.your_domain> <your_host>


In any case 127.x.x.x addresses are only useful to the local computer and are no good when it comes to accessing that computer from another.

It seems that subsonic does a lookup of the server's hostname and then resolves that to an IP address. It's this IP address that the subsonic.org virtual host will use in the redirect when it detects you are inside the network.

You might just want to edit the hostfile and replace the 127.0.1.1 with 192.168.1.104.

-mg

[mgrant]

Oh, and for some background on the reason for the 127.0.1.1 see this thread:

https://lists.ubuntu.com/archives/ubunt ... 20722.html

[Kirk]

Oh, and for some background on the reason for the 127.0.1.1 see this thread:

https://lists.ubuntu.com/archives/ubunt ... 20722.html

Odd... very odd...

I'm running 10.04 on my secondary desktop, I just looked in my /etc/hosts file and it's there too. WTF?

Cheers,
Kirk