Mailing List Archive: Port scanner range problem

Port scanner range problem

Oct 17, 2008, 2:38 AM

Post #1 of 4 (2755 views)

Hi everyone,

I have a problem with the Nessus TCP scanner, especially with the port
range. I just want to scan a few ports (ie 21, 22, 80), so I've only checked
"Nessus TCP scanner", put 21,22,80 in "Port scanner range", and disable ALL
the plugins. But when I start the scan, I can see some packets whose
destinations are 123, 135, 445... Is the port scanner ranger really works ??

Re: Port scanner range problem [ In reply to ]

mikhail at nessus

Oct 17, 2008, 4:34 AM

Post #2 of 4 (2625 views)

Permalink

On Friday 17 October 2008 11:38:53 Sylvain Lapendry wrote:
> I have a problem with the Nessus TCP scanner, especially with the port
> range.

No you don't :)

> I just want to scan a few ports (ie 21, 22, 80), so I've only
> checked "Nessus TCP scanner", put 21,22,80 in "Port scanner range", and
> disable ALL the plugins. But when I start the scan, I can see some packets
> whose destinations are 123, 135, 445...

These packets are sent by the TCP ping function from ping_hosts.nasl

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

Re: Port scanner range problem [ In reply to ]

rgula at tenablesecurity

Oct 17, 2008, 5:33 AM

Post #3 of 4 (2638 views)

Permalink

Sylvain Lapendry wrote:
> Hi everyone,
>
> I have a problem with the Nessus TCP scanner, especially with the port
> range. I just want to scan a few ports (ie 21, 22, 80), so I've only checked
> "Nessus TCP scanner", put 21,22,80 in "Port scanner range", and disable ALL
> the plugins. But when I start the scan, I can see some packets whose
> destinations are 123, 135, 445... Is the port scanner ranger really works ??
>

Is the port scanner the only plugin you have enabled? It sounds like you might
have some other plugins working. You should also enabled the "consider unscanned
ports closed" setting.

Ron

_______________________________________________
Nessus mailing list
Nessus@list.nessus.org
http://mail.nessus.org/mailman/listinfo/nessus

Re: Port scanner range problem [ In reply to ]

sylvain.lapendry at gmail

Oct 17, 2008, 5:44 AM

Post #4 of 4 (2647 views)

Permalink

"Nessus TCP Scanner" is the only plugin checked, and "Consider unscanned
port closed" is enable, but I still have some packets whose destinations are
other ports than those in the "Port scanner range" field.

2008/10/17 Ron Gula <rgula@tenablesecurity.com>

> Sylvain Lapendry wrote:
> > Hi everyone,
> >
> > I have a problem with the Nessus TCP scanner, especially with the port
> > range. I just want to scan a few ports (ie 21, 22, 80), so I've only
> checked
> > "Nessus TCP scanner", put 21,22,80 in "Port scanner range", and disable
> ALL
> > the plugins. But when I start the scan, I can see some packets whose
> > destinations are 123, 135, 445... Is the port scanner ranger really works
> ??
> >
>
> Is the port scanner the only plugin you have enabled? It sounds like you
> might
> have some other plugins working. You should also enabled the "consider
> unscanned
> ports closed" setting.
>
> Ron
>
>