> I can run all commands from my local machine, but from remote machine,
> the port 161 is not discoverable. I know, this is more of linux (xinetd)
> mgmt. question - was wondering, if anyone knew, what I need to anable to
> allow others to be able to access this port?
>From the FAQ:
Requests always seem to timeout, and don't give me anything back. Why?
----------------------------------------------------------------------
There are a number of possible causes of this.
The most likely are the agent access control settings (who is allowed
access by the agent itself), or firewall/packet filtering settings
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A fuller list of possible causes (with indications of how to check
for each) is as follows:
- are the requests arriving, or being blocked (e.g. by a firewall)?
(Restart the agent using 'snmpd -f -Le -d'
and see if it shows the incoming packet dumps)
My guess is that you're most likely running 'iptables' (or similar)
and that this is blocking external access to port 161.
If not, then try working through the full checklist from that FAQ entry.
> I tried introducing a new service called snmp without specifying a port
> (as /etc/services) states that snmp should run on port 161 - but that did
> not help after starting xinetd!!!! :(
Please note that 'snmpd' is run as a standalone daemon, and is *not*
typically under the control of xinetd.
Dave
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
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
