Submit a ticketCall us

Welcome to the NEW Success Center. Search all resources (documentation, videos, training, knowledge base articles) or browse resources by product. If you are unable to find what you are looking for, please contact us at customersuccess@solarwinds.com

 

 

 

 

Home > Success Center > ipMonitor > Connection issues with HTTP-based monitors

Connection issues with HTTP-based monitors

Table of contents

The first thing that needs to be discussed is the difference between the various HTTP based monitors within ipMonitor.

-HTTP: This Monitor simply connects to the “IP Address/Domain Name” specified within the Monitor, requests root (“/”) and disconnects.

-HTML/ASP: This Monitor connects to the “IP Address/Domain Name” specified within the Monitor, requests the specified “URL”, can verify for a specific string of text within the response and disconnects.

-HTTPS: This Monitors does the same thing as the HTML/ASP Monitor, however, it does it over SSL.

-HTTP User Experience: This Monitor connects to the “IP Address/Domain Name” specified within the Monitor, requests the specified “URL” and calculates a checksum on the file received. All subsequent tests will compare the checksum with the original checksum gathered. If the checksums are different, the Monitor will fail. This Monitor SHOULD NOT be used for dynamic pages such as ASP and CGI.


In order to troubleshoot connection errors being returned by these Monitors, perform the following:

1. Gather the “IP Address / Domain Name”, “TCP Port” and “URL” values from the failing Monitor.

2. On the ipMonitor system, open a CMD window and type the following command and hit Enter:

telnet [IP Address/Domain Name] [TCP Port]

3. Once you are connected to the web site, issue the following commands pressing Enter after each one:

-For the HTTP Monitor:

GET / HTTP/1.0
Host: [IP Address/Domain Name]

-For the HTML/ASP Monitor and the HTTP User Experience Monitor:

GET /[URL] HTTP/1.0
Host: [IP Address/Domain Name]

Within the response, ensure the HTTP status code returned is between 200 and 399. If the Monitor is configured to look for text, ensure that you can see the searched text within the response.

Another way to troubleshoot connection errors is to use the Debug feature. Here’s how:

1. Click on the Monitor name to open the "Edit Monitor" window.
2. Append "debug" to the end of the URL displayed in the browser, then hit enter.

3. A "debug" button should appear in the top grey menu. Click on this button and view the communication records between the ipMonitor system and the web site.

 

Install Telnet on Windows

To install Telnet on Windows please use the link below:

https://technet.microsoft.com/en-us/...(v=ws.10).aspx

Last modified
19:33, 22 Jun 2016

Tags

Classifications

Public