Default it only does the Well-known and priveleged 0-1023.
> -----Original Message-----
> From: Ron DuFresne [mailto:[EMAIL PROTECTED]]
> Sent: Monday, March 05, 2001 2:37 PM
> To: Mark Watts
> Cc: Firewalls-Digest (E-mail)
> Subject: Re: Open ports, scans and netstat...
>
>
>
> nmap should not beable to find anything you are not listening
> on for the
> outside <internet>. Those other port entries, well, beside
> logging and
> localhost gunk, should be only connections you iniciated, and are
most
> likely open only to the inside, else a full nmap scan would see
them.
> Remember, nmap, unless told, does not scan all 65,000+ ports a
system
> 'might' be listening on, I forget the default port range.
>
> Thanks,
>
> Ron DuFresne
>
>
> On Mon, 5 Mar 2001, Mark Watts wrote:
>
> > Hi all,
> >
> > I've just run an nmap scan against an (my) NT w/s box...
> >
> > nmap comes back with ports 137,137,1028 and 1030 open.
> >
> > However, netstat -a reveals a bunch more ports which are in
> a listening
> > state.
> >
> > Any ideas why nmap isn't picking these up?
> >
> > I'm not running any f/w software (and yes, I am sure i'm
> scanning the
> > right box :) )
> >
> > Cheers,
> >
> > Mark Watts.
> > -
> > [To unsubscribe, send mail to [EMAIL PROTECTED] with
> > "unsubscribe firewalls" in the body of the message.]
> >
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> "Cutting the space budget really restores my faith in humanity. It
> eliminates dreams, goals, and ideals and lets us get straight to the
> business of hate, debauchery, and self-annihilation." -- Johnny Hart
> ***testing, only testing, and damn good at it too!***
>
> OK, so you're a Ph.D. Just don't touch anything.
>
> -
> [To unsubscribe, send mail to [EMAIL PROTECTED] with
> "unsubscribe firewalls" in the body of the message.]
>
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
