Our website has been down all weekend, and I believe it is because Comcast is blocking ports. I don't see anything internal going on. The webserver responds on both ports internally using its local IP address.
The website is www.gedae.com
I tried running nmap externally and it says those ports are filtered
nmap -Pn -p22,80 -A -T4 gedae.com
Starting Nmap 5.51 ( http://nmap.org ) at 2013-05-20 13:07 EDT
Nmap scan report for gedae.com (188.8.131.52)
Host is up.
rDNS record for 184.108.40.206: 75-146-233-17-Philadelphia.hfc.comcastbusiness.net
PORT STATE SERVICE VERSION
22/tcp filtered ssh
80/tcp filtered http
Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 2.30 seconds
We have another server with SSH access on a nonstandard port, and it works fine. It leads me to believe Comcast has disabled those ports for our account.
What can we do to restore this essential part of your service?
Welcome jim_steed. Thank you for the post. For static IP's all traffic is passed directly thru to the connected device. With the info provided in the post we are able to view your site using the IP and specifying port # 80.
As for port 22 using the gateway IP and port forwarding, 22 is used by the modem for remote administration on some models. You will have to use a non standard external port and it should work fine for ssh.
Oh, FFS. This would be really helpful information to have in the manual somewhere. I've been screwing around with various settings for an hour: DMZ passthru works perfectly (port 22 goes to my internal server, but so does every other port); but port forwarding on just port 22 doesn't work. If you configure forwarding for some external port other than 22, it works fine. Furrfu.