Is my ip blocking port 80

[debiandude]

Ive had my webserver up for a while, but for the past couple of days I couldn't connect to it at work, yet on my internal network it loads up. I think this could be because my ip is blocking port 80? Could someone do a port scan on me, the ports that should be open are 23, 80, 110, 8081, and 50 something I think (for email). Thanks.

[The King Ant]

Starting nmap V. 2.54BETA29 ( www.insecure.org/nmap/ (http://www.insecure.org/nmap/) )
Interesting ports on ool-18bcd94b.dyn.xxxxxxxxx.net (xxx.188.217.xxx):
(The 1541 ports scanned but not shown below are in state: filtered)
Port State Service
22/tcp open ssh
25/tcp open smtp
110/tcp open pop-3
113/tcp closed auth
1080/tcp closed socks
8081/tcp open blackice-icecap
8082/tcp open blackice-alerts

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

[debiandude]

Yup. Its true. I called up my isp, which was a bad ideam because hosting server is against the contract, and in fact because of that stupid worm thing red alert or whatever they are block all traffic to port 80 to their customers. So now I run it on 8080, but geeze, its non standard, no you all have to type technologyreview.org:8080 to get to my site. ARGH!!! It's all microsofts fault!!!

[The Whizzard]

Do you have your own DNS server? Or maybe you can use www.zoneedit.com (http://www.zoneedit.com), if you don't already.

What I'm saying is to make an alias called www. Have it point to http://your_domain.com:8080. This way when someone types in www.your_domain.com (http://www.your_domain.com), it automatically puts the :8080 at the end.

This is what I had to do whth my web site and it works very good. Of course you know, when you make this type of change, it can take several days for all the DNS servers to be updated.

That was the hardest part for me, waiting almost 3 days for everything to be updated.

[ 23 August 2001: Message edited by: The Whizzard ]

[ 23 August 2001: Message edited by: The Whizzard ]

[Harvey]

You're lucky, I can't even do 8080 anymore!

[element-x]

I wasn't sure if I should post another topic, but since this one is right on target with whats going on with my problem as well I thought I could ask here.


isp filtering port 80 (because of CodeRed)
I'm running my own DNS (Bind)
What I'm wanting to know is how exactly it would be possible to have clients be able to type www.domain.com (http://www.domain.com) and have it automagically goto www.domain.com:8080 (http://www.domain.com:8080) instead of to port 80.

I've already changed my httpd.conf to use port 8080, and used mod_rewrite to direct all requests to 'domain.com' to 'www.domain.com', so all I really need now is to find out how to get the initial request to get to 8080, instead of 80.


All help would be much appreciated.