<html><body><div style="font-family: Arial; font-size: 12pt; color: #000000"><div>That's a *really* good point Andrew, & something that I hadn't tried, so thank you. I just attempted a connection (using netcat) from the Linux server that's on the same network as the monitoring server to UDP port 2049 (which is NFS) - that attempt succeeded, so it seems that the network routing is probably OK.<br></div><div><br></div><div>Thanks again,<br></div><div><br></div><div>T.<br></div><hr id="zwchr"><div style="color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Andrew Diederich" <andrewdied@gmail.com><br><b>To: </b>"CLUE's mailing list" <clue@cluedenver.org><br><b>Sent: </b>Wednesday, July 15, 2015 2:02:25 PM<br><b>Subject: </b>Re: [clue] (Slightly OT) - This SNMP issue has me baffled<br><div><br></div><div dir="ltr">Have you verified you can get to other network daemons on the target box from the source box? I've run into issues where network routes weren't actually set up on the servers in the way they should have been, and testing another network daemon can help indicate that. UDP or TCP should route the same, though a UDP test is a better one in this case, I think.<br><div class="gmail_extra"><br></div><div class="gmail_extra">-- <br clear="all"><div><div class="gmail_signature">Andrew Diederich<br><a href="mailto:andrewdied@gmail.com" target="_blank">andrewdied@gmail.com</a><br data-mce-bogus="1"></div></div></div></div>
<br>_______________________________________________<br>clue mailing list: clue@cluedenver.org<br>For information, account preferences, or to unsubscribe see:<br>http://cluedenver.org/mailman/listinfo/clue</div><div><br></div></div></body></html>