On Fri Sep 15 2006 at 16:23, Joel Elwell wrote:
> After updating (uninstall old, clean install new) from Nessus 2.6
I suppose that you mean 2.2.6. And that you are using nessus_tcp_scanner.
> Safe checks were enabled and port scanning was enabled.
Which was the value of max_checks ("Number of checks to perform at the
same time")?
> This approach worked ok with (no NetWare abends) using our previous
> version of Nessus.
There have been several modifications in nessus_tcp_scanner since 2.2.6.
The most noticeable one is an improvement of scan time against
machines which implement RST rate limitation (mainly BSD). If Netware
uses such a trick, Nessus 2.2.8 or 3+ will be much more aggressive
against it. If not, the behaviour should be unchanged and maybe you'll
have to check your parameters (you may have changed some of them when
you switched from 2.x to 3.x)
> I have yet to find any pattern to pursue
Concerning Netware itself, I cannot help you. You are not the first
one to report such problems.
Meanwhile, you could try to reduce max_checks or even switch to Nessus
SYN scanner instead of the TCP scanner.
--
http://arboi.da.ru/ http://ma75.blogspot.com/
PGP key ID : 0x0BBABA91 - 0x1320924F0BBABA91
Fingerprint: 1048 B09B EEAF 20AA F645 2E1A 1320 924F 0BBA BA91
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
