Not sure 100%, but I think that "port range" settings are only for NMap... so, if you're running tcp connect scan instead, it's normal it will scan all ports instead of the range you specified... try changing settings to use NMap instead of tcp connect scan... they're separate plugins, I had them both selected for several scans and it slowed down my job a lot!
Hope this helps NA ----- Original Message ----- From: "Max Andersen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 09, 2003 8:05 AM Subject: Re: specifying ports to scan via the nessus GUI > On Wed, 2003-10-08 at 14:52, Max Andersen wrote: > > On Wed, 2003-10-08 at 14:47, Renaud Deraison wrote: > > > > > By any chance, did you enable the "Nmap" port scanner and in the Prefs > > > tab, set the option to "Fast scan (nmap-services)" ? > > > > I have 'User specified range' in the Prefs tab. > > > > In scan options in the 'port scanner' box it has the following > > checkboxes applied: > > > > Exclude toplevel domain wildcard host > > tcp connect() scan > > ping the remote host > > > > Max > > > > Does anyone have any suggestions? > > Max > >
