On 02/22/03 11:58 AM, Aaron Burke sat at the `puter and typed: > > > On 02/22/03 07:03 PM, Cliff Sarginson sat at the `puter and typed: > > > > Hi, > > > > Well I can telnet to port 80 on your domain, but it times out in a > > > > browser. > > > > I don't get any greeting on the telnet, so...it's open, but > > nothing is > > > > responding to it .. (no web server I mean). > nmap on his IP address says otherwise. (notice "closed" not > "filtered") > > Interesting ports on pool-68-160-158-62.bos.east.verizon.net > (68.160.158.62): > (The 1547 ports scanned but not shown below are in state: filtered) > Port State Service > 21/tcp open ftp > 22/tcp open ssh > 25/tcp open smtp > 80/tcp closed http > 113/tcp closed auth > 143/tcp open imap2 > 443/tcp open https > 993/tcp open imaps > 27374/tcp closed subseven > > Notice that they are closed, a local firewall makes the ports > say "filtered" if they are turned off with a local firewall. > (SNIP)
I am resetting ports 113 and 27374 from my firewall, but not port 80. >From my work system, port 80 is shown as filtered by nmap. Other than that, everything above looks exactly right. Is it possible that port 80 is being reset elsewhere? What command line did you use? I used this: nmap -sT -P0 -O -v -oN ~/scan.txt -p 80 68.160.158.62 And got this: Port State Service 80/tcp filtered http Lou -- Louis LeBlanc [EMAIL PROTECTED] Fully Funded Hobbyist, KeySlapper Extrordinaire :) http://www.keyslapper.org ԿԬ Peter's Principle of Success: Get up one time more than you're knocked down. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
