https://live.paloaltonetworks.com/t5/general-topics/nessus-scan-of-fw2-failed-credentials-were-no-provided-for/m-p/573678#M115334 <P>Hi&nbsp;<a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/154651073">@MichStrickland</a>&nbsp;,</P> <P>&nbsp;</P> <P>I would check FW1 administrators and verify the Nessus scanner account is present and update the credentials to what is expected on the other firewalls.&nbsp;</P> Fri, 19 Jan 2024 19:53:52 GMT JayGolf 2024-01-19T19:53:52Z https://live.paloaltonetworks.com/t5/general-topics/nessus-scan-of-fw2-failed-credentials-were-no-provided-for/m-p/573353#M115296 <P>When performing a NESSUS scan of FW1, errors return:</P> <P>Remote host was not identified as a known device or operating system and the execution of "uname -a" failed.</P> <P>&nbsp;</P> <P>NESSUS returned the following error:</P> <P>Enter old password:</P> <P>&nbsp;</P> <P>This NESSUS scan works on three other FWs successfully</P> <P>Plugin:&nbsp; ssh_get_info.nasl (#12634)</P> <P>Plugin:&nbsp; no_local_checks_credentials.nasl (#110723)</P> <P>&nbsp;</P> <P>The credentials have been validated within the scan policy... and works on three other FWs.</P> Wed, 17 Jan 2024 18:39:43 GMT https://live.paloaltonetworks.com/t5/general-topics/nessus-scan-of-fw2-failed-credentials-were-no-provided-for/m-p/573353#M115296 MichStrickland 2024-01-17T18:39:43Z https://live.paloaltonetworks.com/t5/general-topics/nessus-scan-of-fw2-failed-credentials-were-no-provided-for/m-p/573678#M115334 <P>Hi&nbsp;<a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/154651073">@MichStrickland</a>&nbsp;,</P> <P>&nbsp;</P> <P>I would check FW1 administrators and verify the Nessus scanner account is present and update the credentials to what is expected on the other firewalls.&nbsp;</P> Fri, 19 Jan 2024 19:53:52 GMT https://live.paloaltonetworks.com/t5/general-topics/nessus-scan-of-fw2-failed-credentials-were-no-provided-for/m-p/573678#M115334 JayGolf 2024-01-19T19:53:52Z