Thomas has already pointed you in the direction of the most likely
cause of the timeout problem. I'd make just one further observation:
> snmpstatus localhost public
>
> snmpwalk -v 1 192.168.1.1 public
>
> snmpwalk -v 1 localhost public
>
> snmpwalk -v 2c localhost public
I suggest you get in the habit of using the '-c' command line option
to specify the community string, rather than the "positional parameter"
shown above.
I.e:
snmpstatus -c public localhost
snmpwalk -v 1 -c public 192.168.1.1
snmpwalk -v 1 -c public localhost
snmpwalk -v 2c -c public localhost
This makes no difference when using the v4 UCD client tools,
but if you ever come to upgrade to the v5 Net-SNMP suite,
then the command line client tools will no longer recognise the
form that you are currently using.
Dave
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
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
