Please scan my server for closed port 80

[BrandonSi]

Long story short, I moved my web server from behind my cable router to behind the cable modem. I bought an extra IP address so now from my cable modem I run a crossover cable into a hub, and then plug my router and my web server into the hub on different ports. My router picks up 1 IP from comcast, my web server the other. For whatever reason I can't get my webserver to come up. I can ssh into it, and I can telnet into port 80 and get the standard apache error output, but it just won't come up with a browser. I'm wondering if this is a comcast problem, so if someone could please scan my webserver I would appreciate it. The domain is megapartyman.com, and that should resolve (via no-ip.com's dynamic dns service) to 12.249.112.171.

The only ports that should be open are 22 (ssh) and 80 (httpd).

I've verified that httpd is listening on port 80, and I've updated my virtual host entries to reflect the new IP address from comcast.

Let me know what you come up with.

Thanks in advance.

Brandon

[serz]

root@darkstar:~# nmap 12.249.112.171

Starting nmap 3.48 ( http://www.insecure.org/nmap/ ) at 2003-11-03 22:20 ART
Interesting ports on 12-249-112-171.client.attbi.com (12.249.112.171):
(The 1642 ports scanned but not shown below are in state: closed)
PORT STATE SERVICE
21/tcp open ftp
22/tcp open ssh
80/tcp open http
111/tcp open rpcbind
135/tcp filtered msrpc
136/tcp filtered profile
137/tcp filtered netbios-ns
138/tcp filtered netbios-dgm
139/tcp filtered netbios-ssn
443/tcp open https
445/tcp filtered microsoft-ds
1024/tcp open kdm
1080/tcp filtered socks
3306/tcp open mysql
27374/tcp filtered subseven

Nmap run completed -- 1 IP address (1 host up) scanned in 35.467 seconds

[BrandonSi]

perfect, thanks.

[Gertrude]

Has this server ever worked on port 80 with this ISP where people could connect to it from the internet?

I am pretty sure Comcast is one of the many ISPs that has filtered port 80 traffic to prevent its users from running web servers.

[Gertrude]

I'm not 100% sure on them filtering that port, but I did find this at one of those dynamic DNS/port redirecting services..


Does your ISP block port 80 and prevent you from hosting a website? If your ISP is AT&T cable, Comcast or Verizon then chances are that port 80 access to your computer is blocked.

[serz]

Then you will have to run it on another port.

[BrandonSi]

Originally posted by Gertrude
Has this server ever worked on port 80 with this ISP where people could connect to it from the internet?

I am pretty sure Comcast is one of the many ISPs that has filtered port 80 traffic to prevent its users from running web servers.

It worked when I had it behind my router and I had port 80 forwarded to the internal lan IP address... so that would lead me to believe 80 isn't blocked..?

[BrandonSi]

Nevermind guys, it's up and running now! Thanks :)