|
Hi
Max,
the
communication between Nessusd and nessusWX is done by eth0 which is a host-only
interface. The scanning is done via eth1 which is bridged.
I
produced a type mismatch writing down the networks (I doublechecked that
;-). Actually I scanned 3 different /24 networks. Sorry for
that...
I
enabled all plugins but I will try and disable all of them.
thx
Alex
Strange,
I have the exact same configuration (except for
XP instead of 2K) and I don't have any problems doing large scans.
How do you communicate between your VMware host
and Virtual machine ? I personally always setup a dedicated "host adapter" on
eth1 and use that to communicate between NessusWX and nessusd. Nessusd uses
eth0 to do its scan.
According
to your IP addresses below, you're scanning the same network 3 times.
Shouldn't they be:
192.168.1.0/24
192.168.2.0/24
192.168.3.0/24
I put .0 here because that's the standard to
specify a mask. I'm not sure if nessus is flexible in this matter.
One last thing, what plugins do you have
enabled ? Could one of them stop you somewhere ? Do a test by disabling all
but a few plugins (no port scanners at this phase).
--
Max
Ott, Alexander wrote:
Hi all,
when I try to scan a subnetted network with 3 /24 subnets the scan stops
after 32 IPs. I use the latest Nessus on suse 8.0 in VMWare and NessusWX on
W2K.
Target:
192.168.1.1/24
192.168.1.2/24
192.168.1.3/24
Max simultaneous: 16
Sec checks per host: 10
enable plugin dep: yes
safe checks: yes
optimize test: yes
Resolve unknown services: yes
Remove finished hosts from scan status view: yes
Port range: 1-65535
Port Scanners acitvated: nmap, Ping remote host, LaBrea, SNMP port Scan, SYN
Scan, tcp connect() scan
All Plugins to be tried.
I started this last night in order to be finished this morning.
I would be thankful for any suggestions
thx in advance
Alex
|
