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 Report - Request
by  nyra_mtobias   Go to last post Go to first unread
Last post: Yesterday at 8:05:31 PM(UTC)
Lansweeper Email to close ticket
by  wgonzalez_hope   Go to last post Go to first unread
Last post: Yesterday at 3:54:01 PM(UTC)
Lansweeper Mass update assets through csv
by  B.L.  
Go to last post Go to first unread
Last post: Yesterday at 3:30:21 PM(UTC)
Action Chrome History
by  csys   Go to last post Go to first unread
Last post: Yesterday at 2:14:21 PM(UTC)
Lansweeper Restrict the access to the knowledgebase
by  ABEAL  
Go to last post Go to first unread
Last post: Yesterday at 1:38:25 PM(UTC)
Lansweeper Software: Changes in the last 24 hours
by  alex_vi_42   Go to last post Go to first unread
Last post: Yesterday at 1:37:44 PM(UTC)
Lansweeper Wake on Lan Issues
by  Christophe  
Go to last post Go to first unread
Last post: Yesterday at 1:09:12 PM(UTC)