→ 🚀What's New? Explore Lansweeper's Fall 2024 Updates! Fall Launch Blog !

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to force a scan to use another scan protocol?

How do we force a scan to use a different scan protocol? For example: If you have SNMP-compatible devices, but they get falsely flagged as Linux machines when SSH is open. 

View Entire Topic
Riley
Lansweeper Tech Support
Solution

It is currently not possible to force a specific protocol for a scan. However, you can influence this by mapping your credentials in a specific order. Additionally, you might want to split up your IP scanning targets into smaller IP ranges to fine-tune your credential mappings.

For your example specifically:

  • If an asset is not scanned with SNMP while being SNMP-compatible, it could be that your SNMP credentials don't give correct or complete results. Here are some troubleshooting tips: Troubleshoot SNMP scanning issues
  • If port 22 is open on the device, Lansweeper will try to scan it through SSH. If you'd like to prevent IP Ranges from being scanned via SSH, you can enable the No SSH option for the IP Range in question. Make sure that this IP range does not contain any assets that need to be scanned through SSH (Unix or Mac computers). If certain assets within a range do need SSH to be used, you can split the range into smaller ranges to enable/disable the option more granularly. So, in summary, if an asset is scanned with SSH, but you do not want this, consider using the No SSH option on your IP scanning targets: Scanning with an IP Range scanning target

 

Ask a Question