On 20/12/06, Clement Hsu <[EMAIL PROTECTED]> wrote: > when I perform the command: > snmpgetnext -c public -v 2c 192.168.x.x sysORUpTime > > the result is > > Timeout : No Response from 192.168.x.x
Right - that definitely sounds like access control problems. > And when I execute snmpd -Lo -f -Dread-config > the result is belowed: > > registered debug token read-config, 1 > Warning: no access control information configured. > It's unlikely this agent can serve any useful purpose in this state. OK - apart from the wrong debug token (thanks Thomas), I actually meant that you should start the agent using the same options as usual - just with "-f -Lo -Dread_config" added. I'm pretty sure it's not looking for the snmpd.conf file in the place you expect. As Thomas indicates (and I'd tried to!), the debug token above will show you where the agent is *actually* looking - as well as what it finds there. Dave ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
