Ping is one of the most basic tools for IT personnel to test the connection and speed of the connection between two systems or two addresses. This is a tool/process that is used on a daily basis when it comes to testing connections, time and distance as well as access. When working with AWS (Amazon Web Services) troubleshooting can be easy and fast. Following some basic guidelines and procedures makes working with any of the instances a painless process and when it comes to handling cases, it should make closing them just as fast as opening them.

Ping works much like a sonar or Echo-Location in the sense that it sends an ‘echo’ to a specified location and ‘listening’ for a return. No return means there is no access or this location does not exist. A return ‘echo’ provides information like where was the ‘echo’ from, how long did it take to get there, be received and sent back to the origin. You can also get a general idea if something is not as it should be when you finish the ping. Once the ping is completed, via input or just the basic four packet ping, you will see how many packets of information or how many “echoes” were sent to the specified location and how many were received and lost.

Ping is not tied to a set or series of ports as it is used to communicate with various IPs and ports. With that said, it is possible to allow and disallow pinging or inbound/outbound communication from a set of IPs or in general. In the case of one of my latest tickets, the client could not connect out to the IP address provided for their hosted solution. This was a simple resolution once the client was able to communicate with their IT/Security personnel. The IP for the specified instance/server was not allowed through their firewall. If an unknown connection/IP is not allowed through a Firewall or set of Security Policies, then there is no way for one to send packets of info or “echoes” to this specific location. This can change from company to company or even down to a security personnel’s wishes, goals or even beliefs.

Based on the last paragraph’s thoughts in mind, this can also fall back on how a hosting company sets up their servers or instances. This can also vary depending on the hosts choice of service or even their own goals, thoughts or beliefs. Based on research, AWS EC2 Instances/Servers do not allow the ability to Ping them by default. Granted, you can enable the ability to ping, it would require a lot of work to allow Pinging to any AWS EC2 instance. D-Tools utilizes EC2 for every Instance/Server for our Trial and Hosted solutions. It is an outstanding product (thus far) and it is understandable why so many of our Clients decide to use this service.

The best way to properly troubleshoot an AWS instance/Server when working with D-Tools is to first get an understanding of the issue. Does the Client get any sort of message when trying to connect? Can you connect to their server? When you attempt to access their Server, is it turned on? When in the Server, is the Server Manager and SQL Service running? These are just a few questions I ask myself when handling any kind of Server related issue. Majority of the time, the usual issue for the Clients involve either the SQL Service or Server Manager not being turned on.