port forwarding solutions sharing

[HighlandRanger]

Cannot connect to my IP from outside LAN...

I went to the IP that IPChicken shows

This is so frustrating.

[grant420]

My subsonic server at home is on port 6000. Though subsonic works from my droid phone, I cannot hit my public IP on port 6000 (via command line "telnet IP ADDRESS 6000") here at my office, probably due to outgoing firewall restrictions.

So, are you sure it's not working? Or, are you trying to connect to it from your (properly configured) smartphone via the subsonic app and it still doesn't work?

[HighlandRanger]

I cant hit it with a computer outside of my LAN... computer, smartphone, etc... nothing.

[grant420]

Then surely your issue is that you don't have port forwarding set up, or if you have that set up than maybe your pc that hosts subsonic had its IP changed.

What you need to do is connect to your home LAN - not wifi - router (probably has internally-accessible IP of 192.168.0.1, or 10.0.0.1), and go to the advanced > port forwarding section (or something similar) and set it up so that all TCP & UDP requests coming from the outside on port 8080 (only set this up for this single port) point to the internal IP of your subsonic server. I assume you have set up the PC that hosts subsonic with a static IP, right?

Grant

[HighlandRanger]

I did that already . Yes, it's static, and yes TCP & UDP port 8080 point to the Server Static Internal IP.

[grant420]

Here is what my Centurylink (formerly Qwest) router's port forwarding entries look like:
https://www.dropbox.com/sh/27ri2hatkxyn42j/y3x5ImevRe

[grant420]

I did that already . Yes, it's static, and yes TCP & UDP port 8080 point to the Server Static Internal IP.

Just for shits and giggles, have you tried disabling your Windows Firewall completely and trying it from the outside again, just as a quick test?

Also, also as a quick test, what about disabling your router's firewall and trying it?

It sounds like you've got everything set up correctly...argh, this is frustrating!

One other option: try a different port.

[HighlandRanger]

Haha... I already disabled the Firewall on both, and tried a few different ports. But I will try some others just because. Arghhh.

[grant420]

One other thing, it's definitely your setup: I just tried the http://canyouseeme.org test on my port 6000, and it came back A-OK. Not that this is new info...

[HighlandRanger]

I've tried 8080, 8081, 6000... nothing works. This is pissing me off! Why would it just all of sudden stop working!!!

[grant420]

Hmm, could be a bad router. Or, your ISP is suddenly blocking a huge chunk of ports. Who is your ISP??

[HighlandRanger]

COX is my ISP

[grant420]

Might be time to use them for help:
http://ww2.cox.com/residential/sandiego ... articleId={af165c80-644a-11df-ccef-000000000000}

[GJ51]

Changing the external ip address from your ISP won't prevent being able to connect to Subsonic after you hit the save button on the Settings/Network page. When you hit save, that's what SS does, it transmits the external ip:portnumber and your "easy-to-remember servername" that you entered to subsonic.org so that the redirection can take place on the subsonic.org server.

If you hit save and you get the mesg that the name was saved but it could not connect, then that's what's happened - you transmitted the easy to remember name, your ISP assigned external ip address and the port number that Subsonic is listening on at the host machine. The response is telling you that it has that information, but when it tries to make the connection, the path is blocked and it is not getting a response from your sever. When this happens, you can test to see if the port is open by going to canyouseeme.org and entering the port number and you will see that indeed, from the internet, the port does not respond and the communication path is blocked.

If you cab reach the server from another machine or device from within the network, tha's a good thing, it means that the firewall on the host machine is open and Subsonic isworking properly. The only obstacle for connecting from outside has to be the router and the port forwarding rule. Check to see that the port is being forwarded to the proper INTERNAL ip address. Modify if neccessary and test again with canyouseeme.org. Once the port is responding you are good to go.

Sometimes a router needs a reboot in order for any rule changes to work.

Make sure you don't use 80 or 443 for the port numbers.


HTH

[grant420]

Changing the external ip address from your ISP won't prevent being able to connect to Subsonic after you hit the save button on the Settings/Network page. When you hit save, that's what SS does, it transmits the external ip:portnumber and your "easy-to-remember servername" that you entered to subsonic.org so that the redirection can take place on the subsonic.org server.

If you hit save and you get the mesg that the name was saved but it could not connect, then that's what's happened - you transmitted the easy to remember name, your ISP assigned external ip address and the port number that Subsonic is listening on at the host machine. The response is telling you that it has that information, but when it tries to make the connection, the path is blocked and it is not getting a response from your sever. When this happens, you can test to see if the port is open by going to canyouseeme.org and entering the port number and you will see that indeed, from the internet, the port does not respond and the communication path is blocked.

If you cab reach the server from another machine or device from within the network, tha's a good thing, it means that the firewall on the host machine is open and Subsonic isworking properly. The only obstacle for connecting from outside has to be the router and the port forwarding rule. Check to see that the port is being forwarded to the proper INTERNAL ip address. Modify if neccessary and test again with canyouseeme.org. Once the port is responding you are good to go.

Sometimes a router needs a reboot in order for any rule changes to work.

Make sure you don't use 80 or 443 for the port numbers.


HTH

Gary, if you had read the posts above you would see that we have already verified internal connectivity, and have even used canyouseeme.org to verify that the port is being blocked somehow from the outside.