EditTools
This page contains several helpful tools, utilities and other third-party products that we utilize internally to test, diagnose, etc.
Please note that these tools are from third-parties and are provided here as-is (in other words, *not supported* by us). If any questions/support is required for these tools, please contact the respective parties.
EditMicrosoft .NET
EditChecker
To verify if you have .NET installed...
EditRepair
This tool detects and tries to fix some frequently occurring issues with the setup of Microsoft .NET Framework or with updates to the Microsoft .NET Framework.
EditNetwork
EditNETSTAT
To check machine for what TCP/IP "activity" is happening, you can use the NETSTAT command-line tool included with Windows. This does require an "admin" command prompt.
C:\> netstat -abn
EditTRACERT
To review what is between your machine and our servers, you can use the TRACERT command-line tool included with Windows.
C:\> tracert traf.com
EditPortQry 2.0
A command-line utility that you can use to help troubleshoot TCP/IP connectivity issues. 80 and 2433 are the ports RT needs to use.
These files need to be extracted before use. Once extracted, open a command line to where these files are located and execute a command similar to:
C:\> portqry.exe -n (server) -e 80 -p TCP
C:\> portqry.exe -n (server) -e 2433 -p TCP
Replacing (server) with either a server name or ip address.
The result should be "LISTENING"; if it is not, "something" is "blocking" the connection.
EditWMI Test
To test access permissions, we've created a simple test program.
Execute this utility by using the command window; it's output should be the name of the computer, name of the user and the name of the operating system.
C:\> ComputerInfo
EditUtilities
EditStepvoice Recorder
In order to record both the microphone (input) and speaker (output) devices into a single audio file (mp3), we use the following open-source (free) utility.
EditComponents
EditAdditional Info
In rare circumstances, there may be a situation where, for example, a firewall could be blocking access to our web services. For diagnostic purposes, the full address to these services are:
You can use a web browser to verify connection to these service locations. Please note that these services API's are not for public usage and, as such, are considered "unsupported".