PingGraph 3.0.0.7

Released February 28, 2013


Table of Contents

Introduction
Ordering
Pricing
Registration Benefits
System Requirements
Troubleshooting
FAQ
Change History


Introduction

PingGraph is a graphical networking tool that monitors and displays network connectivity and bandwidth over time. As you might guess from its name, the application graphs "ping" times in an easy-to-understand format, allowing you to identify connectivity problems rapidly. It also graphs available bandwidth, indicating roughly how fast you can push data between your system and the specified host system. It is able to send email alerts when ping times become too slow, or when connectivity is lost to the remote system.


Ordering

Buy Now through esellerate.com  Buy it now!

All online credit card orders are processed quickly and securely through RegNet, a well established and reliable order fulfillment partner. Emailed purchase orders and queries may be sent to jolsen@infixtechnologies.com. Orders using paper purchase orders may be sent to us at our mailing address:

Infix Technologies
6877 W Tracy Loop Rd
Herriman, UT 84065-3884
USA

When you register your software, a license ID will be delivered to you via email with instructions for activating PingGraph. Entering this ID in the dialog shown at startup will unlock the full feature set of PingGraph.


Pricing

Licenses are needed for each system from which you will run PingGraph. Prices shown are in US dollars.

Licenses Cost each
1 $39
2-5 $24
6+ $15


Registration Benefits

There are several great benefits to registering PingGraph. The unregistered version is designed to allow you to evaluate the product before you spend your hard earned money.

  1. First, the saved history for each site is expanded from 3600 entries, and allows for a configurable history up to a million pings.
  2. Second, you will not see the "Registration" box pop up each time the application is run.
  3. Third, you will be able to log data to a comma delimeted data file continuously with file size limited only by your hard drive.
  4. Registration will also help us spend more development time on updates and additional tools to make your life easier.

System Requirements

PingGraph requires version 4.0 or newer of the .NET framework runtime environment. This framework may be installed on Windows 98 and newer operating systems, and anything from Vista onward is likely to have it pre-installed. Depending on the operating system version, you may need additional updates installed.

Not all computers have the proper runtime environment installed by default. The latest version can be downloaded directly from Microsoft Corporation here or here, where you can also find information on specific system requirements.


Troubleshooting

If PingGraph triggers Denial of Service flags in your firewall.

Some firewalls trap any ICMP packet over 1024 bytes in size. Each packet typically has about 42 bytes of extra baggage, so any setting over about 980 bytes can trigger these firewalls. The maximum size of the ping packets (not counting the extra wrapper bytes) can be set per host name.

If PingGraph crashes at startup.

You probably do not have a current version of the .NET runtime. Download the latest version from Microsoft as described in the System Requirements.

Even with the .NET runtime it crashes.

Please email whatever information you can get from the crash notification, and we will work to resolve the problem.

I get nothing but vertical red bars (timeouts) on my graphs when testing a remote system.

You could have a firewall blocking pings between you and the specified host. You can verify if this is the case by seeing if you can reach the hostname "localhost" which tests connectivity to your own system. If you can reach your local system, then the problem is pings bing blocked somewhere along the way. If you need to test a remote system through a firewall, you will need to contact your network administrators and have them open up port 7 which is used for pings.

It crashes, or pops up a dialog with a big technical message.

Please email the text of this message to us, and we can work to resolve the problem quickly for you. The most common dialog is likely to be from trying to send a connectivity warning email when there is no access to an SMTP server.

It takes a long time to start up.

If you are on a network using a proxy that requires authentication, the automatic update check will take a few seconds before deciding it cannot check with the PingGraph home web site. You can ask the admin running your network to set the proxy to allow connections to http://www.infixtechnologies.com/ without requiring authentication, or you can browse there on your own to check for updates from time to time.
 

FAQ

Q. What values are good for maximum ping sizes?

A. It is good to use the default values, with 16 for a minimum and 768 for a maximum. Only the maximum can be adjusted to test throughput at varying packet sizes. You should be aware though that larger packets will be broken apart (fragmented) into multiple physical packets, with more overhead. Keeping the maximum packet size under about 1200 bytes will usually keep them from fragmenting.

Q. What are those vertical red lines?

A. Those are reports of dropped packets. If you get nothing but red lines, you can verify that nothing is getting through from a command prompt by typing "ping <your host name>" to see if it reports connectivity.

Q. Is there any built-in help?

A. Yes. Press the F1 key and PingGraph will display context sensitive help for some parts of the application. Change focus by either clicking on elements of the interface, or by using the Tab key, then press F1.

Q. Why should I register? What benefits do I get?

A. See the listed Registration Benefits.

Q. What do I use when entering a host name?

A. You can use either a numeric IP address like 192.168.0.1 for instance, or a host name such as www.yourfavoritehost.com which PingGraph will internally translate to an IP address. In addition, you can alter the name that is displayed in the graph by changing the "Show Name As" field. That way, you can label 192.168.0.1 as your DSL or Cable modem.

Q. Why can't I specify rapid ping rates?

A. Many systems would interpret high ping rates as a primitive attack on their system, typically called Denial of Service attack. We should all be good net citizens, so the application does not allow high data rates that could be offensive to unsuspecting hosts.

Q. Does PingGraph "call home" and report what I'm doing?

A. No. Spyware is evil. There are only three ways where PingGraph will ever contact a system not on your specified host ping list.

  1. When purchasing a license, which sends you to our commerce site.
  2. When visiting our home page.
  3. When checking for updates and messages, which reads an XML file from our site.

None of these cases ever report information about you or your computer past what regular web browsing reports.

Q. How much bandwidth does PingGraph consume?

A. It uses about 1200 bytes of traffic when it sends out its test pings. More frequent pings use more bandwidth, but the pings are infrequent enough that you should not notice that it is running, even on a slower modem connection.

Q. How much processor does PingGraph consume?

A. Less than 2% is common for something around a 1 GHz processor, but could be higher on slow systems, or when you have a large number of hosts listed. The Windows Task Manager will show you how much processor each application is using.

Q. Why did you use the .NET runtime? Downloading that huge runtime is a killer!

A. Development times for .NET applications are lower, so I can produce a higher quality application in less time, concentrating on feature request from customers rather than fighting with the development tools.

Q. What is the data format of the PingGraph logs?

A. Registered users can read their stored ping data as an XML file which lives in the system's shared applications directory, which is usually "C:\Documents and Settings\All Users\Application Data\Infix Technologies\PingGraph\" followed by the version number, such as "3.0.0.0". The file names in that directory is are the host names with an "xml" extension. This logged data will migrate forward to updated versions when you upgrade.

Q. How big to the log files get?

A. XML is not a very compact data format, but the ease of use makes up for it. Each entry within the log is between 100 and 200 bytes, so For each 1000 entries stored, it will take 100 to 200 KBytes. One good way to manage how much space you use is to slow the sample rate. If you only test a host once every 10 minutes, then 1000 entries will give you almost a week of historical data. The default setting for the data on a host is to keep it trimmed to a maximum of 20,000 entries. This length is configurable.

Q. Where are the log files stored?

A. A log file is saved for each hostname entered into the program. They are stored at in the windows application data folder, which is typically "C:\Documents and Settings\All Users\Application Data\Infix Technologies\PingGraph\3.0.0.*" for win XP.
The configuration file for the application is stored in a different location, also the default for app config data for windows, in "C:\Documents and Settings--USER_NAME--\Local Settings\Application Data\Infix_Technologies\PingGraph.exe--RANDOM_TAG--\3.0.0.7" where "RANDOM_TAG" changes based on the directory it is run from.

Q. Can you make PingGraph do <insert your favorite feature here>?

A. Drop us a line and we'll see if it fits with the design of the application. Most of the updates to PingGraph have been due to requests from users for new features. Even if the feature doesn't fit well, it could be a need that can be addressed with a new tool or utility.

Q. It didn't copy my old host data. How do I fix that?

A. The old host data is stored in "C:\Documents and Settings\All Users\Application Data\Infix Technologies\PingGraph\3.0.0.*" as noted above. You can copy the files from a previous version (Say, 3.0.0.2) to a newer version (like 3.0.0.5) in case you skipped a version. Starting with 3.0.0.4 it should automatically check back one version for data files. Data from a version before 3.0.0.0 is incompatible with the new vesion.

Change History (somewhat technical content)

3.0.0.7 (Feb 28, 2013)

3.0.0.6 (Feb 11, 2011)

3.0.0.5 (Oct 15, 2010)

3.0.0.4 (Sept 29, 2010)

3.0.0.3 (Sept 17, 2010)

3.0.0.2 (Aug 18, 2010)

3.0.0.1 (Aug 18, 2010)

3.0.0.0 (Aug 16, 2010)

2.0.1.15 (Dec 28, 2007)

2.0.1.14 (Dec 27, 2007)

2.0.1.13 (Dec 15, 2007)

2.0.1.12 (Mar 15, 2006)

2.0.1.11 (Dec 23, 2005)

2.0.1.10 (Oct 30, 2005)

2.0.1.9 (Apr 6, 2005)

2.0.1.8 (Feb 2, 2005)

2.0.1.7 (May 11, 2004)

2.0.1.6 (Mar 4, 2004)

2.0.1.5 (Feb 20, 2004)

2.0.1.4 (Feb 9, 2004)

2.0.1.3 (Jan 28, 2004)

2.0.1.2 (Jan 22, 2004)

2.0.1.1 (Jan 21, 2004)

2.0.1.0 (Jan 19, 2004)