|
Interesting…. I am using the Win based client, set up to ping
remote host and nmap (NASL wrapper) enabled and set to do a FIN scan. Configuring
plugins I have set the SMB credentials and watching the tests go through, I get
0% on port scans, but 100% on tests with no results to view…. Running nmap from a console connection to the
scanning server gives me the following…. [EMAIL PROTECTED] ~]# nmap -v -n -oN file.out
-P0 -sT -p 1-1024 -r 163.119.128.180 Starting nmap 3.81 (
http://www.insecure.org/nmap/ ) at 2005-08-24 16:26 BST Initiating Connect() Scan against
163.119.128.180 [1024 ports] at 16:26 Discovered open port 139/tcp on
163.119.128.180 Discovered open port 135/tcp on
163.119.128.180 Discovered open port 427/tcp on
163.119.128.180 Discovered open port 445/tcp on
163.119.128.180 The Connect() Scan took 0.03s to scan 1024
total ports. Host 163.119.128.180 appears to be up ...
good. Interesting ports on 163.119.128.180: caught SIGSEGV signal, cleaning up Aborted I presume that the aborted connection
means something is wrong??? Where can I check the nessus logs…. I can confirm that the machine is not
behind a firewall, I am scanning from within our company LAN, and Nessus has
rights to read the remote registry… Martin From: sanjeev sinha
[mailto:[EMAIL PROTECTED] Martin, Please try to scan using the following command (nmap) to see
what ports are discovered: nmap -v
-n -oN file.out -P0 -sT -p 1-1024 -r <ip address> A
question: is this ip address behind a firewall and if so, what is its
behavior with respect to syn scans that you are using? Also, you could
try FIN scan technique and observe the results. Sanjeev All work
and no play makes Jack a dull boy --- Jack Torrance, The Shining
|
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
