Notification

Icon
Error

Context in SNMPv3 scanning

Posted: Friday, May 27, 2016 1:32:27 PM(UTC)
techreg

techreg

Member Original PosterPosts: 14
4
Like
Hello,

Would it be possible in a future version to include the specification of the context when dealing with SNMPv3 credentials? Some devices support SNMPv3, but not using the default context used in SMPv3 scanning. For instance, some OKI printers answers to SNMV3 requests only when the "v3context" context is specified.

As it is right now, when I need to query those devices I am forced to use the insecure SNMPv1 protocol.

Also, when no privacy (encryption) is needed, the UI still pretend to have the encryption field filled in.

Thanks,

A.
KyleCascade
#1KyleCascade Member Posts: 8  
posted: 8/19/2016 12:07:58 AM(UTC)
We are running into the same issue with the HP printers. Context needs to be Jetdirect but there is no way to specify this in Lansweeper.
IT Service Desk
#2IT Service Desk Member Posts: 2  
posted: 5/10/2019 1:32:14 PM(UTC)
This is a requirement in our organization, we must use SNMPv3 with "Context", we really need Lansweeper to keep up with security requirements.

Active Discussions

Lansweeper Firefox 67.0.3 zero-day vulnerability
by  B Claeys   Go to last post Go to first unread
Last post: Today at 3:13:30 PM(UTC)
Lansweeper BlueKeep Vulnerability
by  heybobby1  
Go to last post Go to first unread
Last post: Today at 3:02:34 PM(UTC)
Lansweeper VLC Player CVE-2019-5439
by  Esben.D   Go to last post Go to first unread
Last post: Yesterday at 9:19:29 AM(UTC)
Lansweeper Enabled/Disabled Local/AD Admin accounts
by  vqT4cDoP9iXyMZwoDUWU  
Go to last post Go to first unread
Last post: 6/17/2019 9:12:30 PM(UTC)
Lansweeper code in posts
by  AZHockeyNut   Go to last post Go to first unread
Last post: 6/14/2019 4:39:46 PM(UTC)
Lansweeper Adding more info to asset report
by  RC62N   Go to last post Go to first unread
Last post: 6/13/2019 9:46:31 PM(UTC)
Report Center Top 5 Average RAM Usage
by  Esben.D  
Go to last post Go to first unread
Last post: 6/13/2019 1:15:31 PM(UTC)