The Linux or macOS machines scanning completes with errors displayed. This article provides information on how to address these errors.
With the Linux and macOS scanning, it is common to see irrelevant Windows checks related errors.
When LanGuard starts a scan, it must determine the operating system. First, it tries to connect to the computer as if it were a Windows machine using standard Windows protocols (SMB/RPC). These attempts will fail and cause corresponding errors. Once these fail, LanGuard attempts to contact the machine over SSH, which is how it communicates with the Linux and macOS computers.
There might be genuine errors, of course, which are most of the time related to the missing requirements or incorrect credentials configuration.
- Check the Scan thread and make sure the problem is legitimate, like the "Authentication failed" error.
-->Failed to connect (53) The network path was not found.
Collecting Linux/Unix OS Information (SSH)...
**** If the failure occurs in this section is a legitimate failure ****
- Verify whether the distribution and version are supported and the requirements are met:
- If using an account other than the root, try scanning with the root account to ensure it is not a permissions problem as follows:
- In the LanGuard console Scan tab, click the Scan Options... and un-check the option to Use per computer credentials when available.
- Scan Target should be set to the IP Address of the target machine.
- Select Alternative credentials.
- Use root as the Username.
The "Use per computer credentials when available" setting will cause LanGuard to use the settings from the Dashboard > <Host_Name> properties > Credentials section.
- If the above settings fail, use Putty to connect to the target machine using the root account to verify that you can actually connect.
Once the legitimate errors root cause is identified and fixed, repeat the scan. If the issue persists, contact GFI LanGuard Support.