On 18/01/2008, Dan Miller (Kromos) <[EMAIL PROTECTED]> wrote: > However, while putting it in the correct place (/usr/local/share/snmp in my > case) has gotten rid of the warning message in snmpd.log, it hasn't affected > the communication problem that I'm experiencing. Hopefully somebody has > some ideas about that.
Can you please confirm exactly what the current problem is. Previously, given that the non-working system had overwritten the access control settings, then this would explain why your MIB module wasn't getting called. The agent checks the access permissions *before* trying to process the request, and will simply discard requests that don't have valid credentials. That's certainly what your previous message looked like. But if you've got a valid snmpd.conf file (complete with access control) and the agent is picking it up, then that ought to work. What exactly is in this file? What is the request(s) that you are sending, and what do you see? Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
