I use ssh all the time, try higher ports.
Some of the low ones will be blocked by ISPs, and I have not run into my device being unable to hit any port yet.
I have ssh (alternate port), and 2 RDP (alternative numbered) ports opened, along with remote managment ports for other things.
I show Verizon blocking incoming (might be the FiOS router):
Who is your ISP for your home net?
I would bet on Internet Provider (the wired), or firewall/router combo blocking it.
When you are on WiFi, you are just like being plugged into your LAN (most of the time on home routers/access points). When you come from the outside, it 1st gets blocked at your provider, then your router/firewall, in that order.
What you can try is open a random port, FW it, then do a tcping on the port with tcping from the outside (tcping is freeware), or you can use nmap from an outside Linux box to test. I would not use any standard ports to FW, as those get scanned for on the daily. Try something like 64123 1st, as that is probably not used for anything...and most port scanners start at the bottom like 1-995, and 64123 is a long way from that...
There is an easy way to test... find your router's outside IP. (If your router supports it... this does not work on some Netgear devices...))
Reference the WAN ip from internally (not the 192.168.x.y, or 10.x.y.z. Whatever your ISP gave your router, WAN addy as it is sometimes called) and see if you can hit it that way for testing on the WiFi. THEN test with WiFi disabled after you get the other to work. This would also test to see if the router is blocking... irrelevant is the ISP blocking until you turn WiFi off. This will test if the router itself is blocking.
Just a thought, as it wasn't mentioned... You ALSO have to Forward the ports from the router to the 192.168.x.y address internally. Most routers ARE a self-contained firewall and will block ALL ports, unless forwarded internally manually.
Sorry if I am not explaining this right: it definitely has nothing to do with my network at home because its when I am not at home and trying to access it across the cell network. When I am at home and connected to my network everything works fine (I can reach all the ports I need to). It is when trying to, for example, send email when I'm NOT at home that is the problem.
Right. If you are outside of your network (Cell data, work, or from a friend's house) and you want to access your home boxes for e-mail and ssh server for pulling e-mail externally (via the internet, from your home network, when you are not home).
Routers (with built in firewalls) will not allow outside traffic (from the Internet [everything but 192.168.*.*?]) traffic to hit computers on the inside (192.168.*.*?) network, this is the firewall part of mosts routers. Being a Firewall (your router has this built in, in most cases) "you have to explicitly allow certian ports to pass from the Internet (external traffic), to your home network (internal traffic)".
A simple way to look at it is:
Everything Inside your house: Lan, Wireless (WiFi), Etc is all INTERNAL to your network and is on the INSIDE the home network and the firewall ignores.
Everything Outside your house is External, or Internet traffic: including From your Work, and Cellular data, and from a friend's house, so the firewall blocks all this traffic, so that people on the Internet cannot access your computers/files.
1) In order for you to ssh into a Linux machine from the Internet, you have to poke holes in your router's firewall to allow this traffic.
2) In order for you to pull e-mail from your e-mail server at home, you need to poke a hole in the firewal to allow for this, also.
http://portforward.com/ might be of help.
Let's just start with ssh: Did you Open/Forward a Port on your router to allow for this to happen on your Router/Firewall yet?
I'm not sure that I follow. I have 3 racks of servers spread out in data centers across the country and I'm trying to ssh into them, not my home network.
Similarly I am trying to connect to one of my email servers at one of those data centers and send mail.
Of course those are firewalled as necessary, but these ports are open. As I mentioned I even swtiched ssh to run on port 995, which is purportedly one of the ports that is open.
That being said, on a whim, I tried changing my apn name from epc.tmobile.com to internet2.voicestream.com and now I can access everything. Though how long internet2.voicestream.com will be around, I do not know. Clearly it has something to do with how epc.tmobile.com APN is configured to block ports.
I am sorry. Since there was no reference to having done it before was mentioned, I thought you were a basic home user trying for the 1st time... to get to a Home server.
It may be that attacks from the APN triggered a reverse DNS lookup, and the offsite (company) firewall started blocking incoming that APN? I am not really sure how this all works on the cell side, glad to hear it is working for you.
No worries at all, I think that is what I was trying to say but we just had a different context. Your answer, if I were trying to connect to home network, was as thorough and thoughtful as I've seen - I tip my hat to you.
Also, FYI, these are my servers and I definitely don't have anything that would cause that blocking to happen. epc.trmobile.com seems to just not allow many of the ports to pass through it as internet2.voicestream.com does. How long internet2 will be around I could only guess at.
It also could be that something is "misconfigured" with my account which is causing epc.tmobile.com to fail. I've been using Sidekicks since the SK2 came out and my account has gone through a number of changes over the years. Maybe there is just a checkbox someone forgot to click, I dunno.
It would be interesting if anyone else reading this has a SK2 (or I presume any Samsung TMO device) if they are able to test the available of these ports going through epc.tmobile.com. The rep I spoke with at Tmobile said he gets a lot of questions about this sort of thing.