This email is more for the lists archive than anything. I just like to leave good documentation behind.

The symptom was that I could not do local scans on the target Linux System. My log files (/var/log/secure) were showing:
  Did not receive identification string from [NessusServerIP]

When I used an ssh password (not recomended, but I tried it anyway), my /var/log/secure actually said:
  Did not receive identification string from [NessusServerIP]
  Accepted password for nessus from [NessusServerIP]

But both my Nessus reports were saying:
"It was not possible to log into the remote host. Nessus report the following error:
   [public key authentication failed | password authentication failed]"

The issue turned out to be a DNS one. Putting a DNS entry in the /etc/hosts file on the target computer solved the issue.

I noticed the issue when I ran a ssh from the Linux box itself and it took a number of seconds to connect
   ssh [EMAIL PROTECTED]

In my test environment, there were no active DNS servers, so my clients were unable to properly resolve DNS.

Environment:
I was using MS Virtual PC, and both my Linux boxes were "virtual"
   I was scanning Fedora Core 1
   Nessus was being hosted on a Fedora Core 5 server
I used both the WinXP Nessus client, and the Linux Nessus client. Neither worked until I put the /etc/hosts entry in, and then both of them worked.


Thanks all you who helped me track this one down.

   - Tim
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to