Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Testing SNMP port connection using telnet

Testing SNMP port connection using telnet

Updated September 21, 2017

Overview

This article explains why using telnet to test the SNMP port connection will not work and how to test the connection in the correct way.

Environment

  • Orion Platform, all versions

Cause 

The telnet to SNMP port (e.g. 161 or 2055) will not work due to the fact that it uses a one-way/no-response UDP protocol.

In order for telnet to work, it needs a 2-way/query-response protocol such as TCP.

Resolution

To test the SNMP port connection you will need to use a Microsoft tool called PortQry.

It will show you if the port is listening and more depending on the command you will use.

The tool is widely available and if you need more information about it, see "Description of the Portqry.exe command-line utility" (© 2017 Microsoft, available at www.microsoft.com, obtained on September 21, 2017.).

 

 

Last modified

Tags

Classifications

Public