Re: problem using ports other than 161/162

Perhaps I should try TCP.
I just changed the server to listen on tcp, how do I test it with 
snmpwalk via tcp?

snmpwalk doesn't connect to TCP, even locally, and I don't see an option 
for that in the man page.

Thanks,
Daniel

Wes Hardaker wrote:
>>>>>> On Wed, 03 Sep 2008 17:18:40 -0600, Daniel Gibby <[email protected]> said:
>>>>>>             
>
> DG> This also works and gives same info:
> DG> snmpwalk -Os -c public -v 1 localhost:10161 system
> DG> sysName.0 = STRING: mymachine.com
>
> If that works and:
>
> DG> But, I still can't snmp walk from the remote network...
> DG> snmpwalk -Os -c public -v 1 MY_REMOTE_IP:10161 system
> DG> Timeout: No Response from MY_REMOTE_IP:10161
>
> That doesn't then the ISP is likely blocking incoming packets (and nmap
> can get confused by that).
>
> You could try TCP instead, or TCP through an ssh tunnel.
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/

_______________________________________________
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