Blame it all on the firewall!

[Kevin Hodle]

It may be that his ISP is filtering the ports for its entire address
pool.. He could try scanning some IP's adjacent to his to see if they
give the same results.
 
Kevin Hodle
CCNA, Network+, A+
Alexander Open Systems
Network Operations Center
(913)-307-2367
kevinh at aos5.com

-----Original Message-----
From: Matt Luettgen [mailto:matt at tccassociates.net] 
Sent: Friday, April 04, 2003 9:52 AM
To: kclug at kclug.org
Subject: Re: Blame it all on the firewall!

I know what they are, I'm wondering why smoothwall doesnt have them
closed instead of filtered

On Fri, 04 Apr 2003 09:22:32 -0600
Jason Clinton <jasonclinton at kcpipeband.org> wrote:

> Matt Luettgen wrote:
> > I was doing some port forwarding last night with smoothwall and when

> > I was done I had someone nmap me from the outside world, everything 
> > looked normal but two ports which concern me because of the windows 
> > boxes on the network.
> > 
> > 31337/tcp  filtered    Elite                   
> > 54320/tcp  filtered    bo2k    
> > 
> > Any ideas of why Smoothwall wouldnt be blocking these?
> 
> The second one is Back Orifice 2000. Back in my script kiddie days, 
> this handy little tool would allow you to completely control a remote 
> computer. It's quite dated, now.
> 
> I don't know about the first one. I assume both of these are to block
> standard trojan traffic.
> 
> --
> Jason Clinton
> I don't believe in witty sigs.
>