Scan issue after upgrading to the latest version (v12.5.1.1)

[apogacsas]

We've upgraded our Lansweeper to the latest version (v12.5.1.1) and faced there are more scanning issue with 
"Object OID could not be retrieved. for OID 1.3.6.1.2.1.1.2.0".

This issue is appered on the RHEL VM scan also. SNMP scan should not be running there because scanning with SSH credential was successful. It was working fine before the upgrade.

It seems the scanning with global SNMP runs every time or something has changed in the new version.

Please check why try to scan the assets with global SNMP when the scanning was already successful with other credential.

Thx.

[blackmoonwolf]

I, too, am having issues with scanning due to:

Object OID could not be retrieved. for OID 1.3.6.1.2.1.1.2.0

Oddly, it seems that my Juniper network gear is not affected. But most everything else in my Assets list is. It all started immediately following the v12.5.1.1 update.

[Mister_Nobody]

I think it's new banner for old check:

https://community.lansweeper.com/t5/troubleshooting-scanning-issues/troubleshoot-snmp-scanning-issue...

Make sure SNMP on the device responds to a read request on OID 1.3.6.1.2.1.1.2.0. This is a system OID that should exist on SNMP-enabled devices. Lansweeper tries to read this OID first. If no response is given, it is assumed SNMP is disabled or not working and Lansweeper skips SNMP scanning.

[apogacsas]

Hi,

Thx for link, I know this troubleshooting for scanning issue with SNMP.

But the my problem is that why Lansweeper try to scan my RHEL asset with SNMP if there was successful scan via SSH? With previous Lansweeper version there was not any problem with scanning and my RHEL asset scan was successful. With new version I got SNMP scan issue.

[Mister_Nobody]

Ignore it or create support case.