/build/static/layout/Breadcrumb_cap_w.png

Discovering printers using SNMPv3?

Has anyone had any luck discovering and provisioning printers using SNMPv3? We are able to discover and provision successfully with v1/v2. We are also able to discover the same devices using SNMPv3 in other applications like HP Web Jetadmin and Ricoh Device Manager. But when we try the same devices and setting in KACE the SNMP Test fails on the discovery.

1 Comment   [ + ] Show comment
  • I'm having the same issue, I have 2 HP Copiers in two locations, SNMP 1/2 disabled, SNMP 3 configured identically. Neither can be contacted via SNMPv3.

    I've got ESXi hosts working via SNMPv3, but not HP Copier/Printers... - tycho566 5 years ago
    • the best way would to contact the HP support, if SNMPv3 works well with other products it seems the SNMPv3 implementation is problematic - Nico_K 5 years ago

Answers (2)

Answer Summary:
Posted by: Nico_K 5 years ago
Red Belt
1
this is not a problem, the printer who speak v3 work well. Unfortunately most of my printers don't speak v3.
Posted by: abeckloff 5 years ago
White Belt
0

Top Answer

I ended up opening a Service Request with Quest Support. If the device requires a Context Name like all of our HP printers KACE is not able to discover it using SNMPv3 since there is no field for the Context Name when setting up the Credential in KACE.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ