Installing TCP Latency Test Client

Home - Client Software (zip) - Client Installation - Compiling Client - Trace Latency Tool - Site Terms of Use

In addition to the .NET framework, you need the MySQL ODBC client and the ODBC .NET Data Provider from:

MySQL Connector/ODBC 3.51 Downloads
ODBC .NET Data Provider

Microsoft Data Access Components (MDAC) version 2.6 is required, and 2.7 is recommended. Version 2.8 SP1 works, and is available here.

Install the awd.exe file available here, and install using the .NET installutil:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>cd C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>installutil c:\awd\awd.exe
Microsoft (R) .NET Framework Installation utility Version 1.1.4322.573
Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.


Running a transacted installation.

Beginning the Install phase of the installation.
See the contents of the log file for the c:\awd\awd.exe assembly's progress.
The file is located at c:\awd\awd.InstallLog.
Installing assembly 'c:\awd\awd.exe'.
Affected parameters are:
   assemblypath = c:\awd\awd.exe
   logfile = c:\awd\awd.InstallLog
Installing service awds...
Service awds has been successfully installed.
Creating EventLog source awds in log Application...

The Install phase completed successfully, and the Commit phase is beginning.
See the contents of the log file for the c:\awd\awd.exe assembly's progress.
The file is located at c:\awd\awd.InstallLog.
Committing assembly 'c:\awd\awd.exe'.
Affected parameters are:
   assemblypath = c:\awd\awd.exe
   logfile = c:\awd\awd.InstallLog

The Commit phase completed successfully.

The transacted install has completed.

C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322>

Add an entry in \windows\system32\drivers\etc\hosts for arewedownhost. Example:

10.50.100.1	arewedownhost

Set up a MySQL database called arewedown, with a table stats with this structure:

mysql> describe stats
    -> ;
+-----------+-----------+------+-----+-------------------+-------+
| Field     | Type      | Null | Key | Default           | Extra |
+-----------+-----------+------+-----+-------------------+-------+
| timeentry | timestamp | YES  |     | CURRENT_TIMESTAMP |       |
| host      | char(50)  | YES  |     | NULL              |       |
| time      | int(10)   | YES  |     | NULL              |       |
+-----------+-----------+------+-----+-------------------+-------+
3 rows in set (0.00 sec)

Create a user are, with access to the arewedown database. The password is embedded in the application; however, since this is basically just inserting records with the user info at 30 second intervals, there isn't a huge security worry here. I would suggest that you limit the users that connect:

mysql> grant all privileges on arewedown.* to are@'10.50.100.0/255.255.255.0'
 identified by 'arepass';
Query OK, 0 rows affected (0.06 sec)

mysql> flush privileges; Query OK, 0 rows affected (0.00 sec)
mysql>

The updated database will look something like this:

| 2005-08-05 12:06:11 | are@10.50.100.112 |  100 |
| 2005-08-05 12:06:11 | are@10.50.100.112 |  101 |
| 2005-08-05 12:06:37 | are@10.50.100.2   |  100 |
| 2005-08-05 12:06:37 | are@10.50.100.2   |  101 |
| 2005-08-05 12:06:41 | are@10.50.100.112 |  100 |
| 2005-08-05 12:06:41 | are@10.50.100.112 |  101 |
| 2005-08-05 12:07:07 | are@10.50.100.2   |  100 |
| 2005-08-05 12:07:07 | are@10.50.100.2   |  101 |

The idea is that the delay between the 100 and 101 entries will vary when there are problems. Of course, if a host stops inserting records, there are bigger problems.

I have tested this on XP, Windows 2000 Professional, and Windows Server 2003.