Dumb question probably, but you obfuscated the network or address you were trying to scan in the message output below. Your edited output only shows three octets xxx.xxx.xxx - are you trying to scan a whole network and leaving off the last octet?
On Wed, 2003-06-18 at 09:34, royeda01 wrote: > just ran a nessus scan from command line: > the following was logged in the message file: > > [Wed Jun 18 09:10:15 2003][8739] connection from 127.0.0.1 > [Wed Jun 18 09:10:15 2003][11716] Client requested protocol version 101. > [Wed Jun 18 09:10:26 2003][11716] Installing IO thread id tracker. > [Wed Jun 18 09:10:33 2003][11716] successful login of xxxx from 127.0.0.1 > [Wed Jun 18 09:10:43 2003][11716] Redirecting debugging output to > /var/lib/nessus/nessusd.dump > [Wed Jun 18 09:10:44 2003][11716] user xxxx starts a new attack. Target(s) : > xxx.xxx.xxx, with max_threads = 15 > [Wed Jun 18 09:10:44 2003][11716] user xxxx : rejected attempt to scan xxx.xxx.xxx > [Wed Jun 18 09:10:44 2003][11716] user xxxx : test complete > [Wed Jun 18 09:10:44 2003][11716] user xxxx : Kept alive connection > [Wed Jun 18 09:10:44 2003][11716] End-of-data -- client has dropped the communication > > anyone know why its doing this? > theres nothing in the nessusd.dump -- ------------ James V. Fields
