[olug] Cox blocking inbound TCP 2401?

[Jay Hannah]

On Mar 19, 2004, at 8:13 AM, Terry wrote:
> nmap -sT -p 2401 -P0 68.13.20.113
>
> Starting nmap 3.50 ( http://www.insecure.org/nmap/ )
> at 2004-03-19 08:12 CST
> Interesting ports on ip68-13-20-113.om.om.cox.net
> (68.13.20.113):
> PORT     STATE    SERVICE
> 2401/tcp filtered cvspserver

Ooo... Sweet. Must learn nmap.

man nmap

The  result  of  running nmap is usually a list of interesting ports on
the machine(s) being scanned (if any).  Nmap always  gives  the  port's
"well  known"  service name (if any), number, state, and protocol.  The
state is either 'open', 'filtered', or 'unfiltered'.  Open  means  that
the  target  machine  will accept() connections on that port.  Filtered
means that a firewall, filter, or other network  obstacle  is  covering
the port and preventing nmap from determining whether the port is open.
Unfiltered means that the port is known by nmap to  be  closed  and  no
firewall/filter  seems to be interfering with nmap's attempts to deter-
mine this.  Unfiltered ports are the common case  and  are  only  shown
when most of the scanned ports are in the filtered state.

So I guess either (1) Cox is blocking, or (2) I don't have my Linksys 
set up right? I don't know how the latter could be the case, it was 
working fine for months back when I was using it and I didn't touch the 
Linksys... Plus the Linksys config is so dead simple I don't know how I 
could botch it even if I wanted to...

I should call Cox?

Or move 2401 to port 240100? Maybe they don't mess with *really* high 
ports?

Thanks,

j