Cox Business Services Bandwidth Tests

The files in this archive should be unzipped to a single directory on a web server. Our testing has used Microsoft IIS 5.0 servers, but there are not any IIS-specific features in any of these web pages so they should run fine on any web server. For performance and security reasons you may want to disable any high-level scripting features on the server, the goal is to serve out bits as fast as the box can go.

Download Test - Automatic (DownloadTest.htm)

The automatic download test uses a series of large image files to determine the link speed.

Test Configuration

All of the data and images required for the automatic download test are already in the directory.

Results

Results are displayed in kilobits per second; the actual data size and test time are also shown. If the test did not run at least one second, the speed measure is not shown since the test did not run long enough for an accurate result. For the automatic test, this case should only occur if the largest available image can be downloaded in less than one second.

Download Test - Manual (DownXXXX.htm)

The manual download test uses a large web page filled with random data to determine the link speed.

Test Configuration

Each individual manual test consists of a separate file. Manual tests are provided for 50KB, 500KB, and 5000KB sizes, but others can be easily made. To make a new test file, copy the next smaller file and duplicate the random data blocks that are delimited by <-- --> until a file of the desired size is created. Then set the variable TotalKB to the size of the file you created.

Results

Results are displayed in kilobits per second; the actual data size and test time are also shown. If the test did not run at least one second, the speed measure is not shown since the test did not run long enough for an accurate result. For the automatic test, this case should only occur if the largest available image can be downloaded in less than one second.

Upload Test (UploadTest.htm)

The upload test uses the Connection Checker ActiveX control.

Test Configuration

  1. Install and configure the FTP service on the server. Anonymous access should be enabled. For best security we recommend that the FTP directories be put onto a separate partition, not the system partition.
  2. Create a /temp directory under the FTP root that will be used to upload test data. The /temp directory must be writable by the anonymous user, but the FTP root should not be. Set the permissions on /temp so that users can only create files, not directories.
  3. Create a scheduled task (cron job in Unix) that deletes all files and subdirectories in the /temp folder every 15 minutes. This avoids the buildup of temp files and prevents hackers from using the folder for storage.
  4. Edit UploadTest.htm to insert the DNS name or IP address of the FTP server configured above.
  5. Configuration is complete, load UploadTest.htm and try running a test.

Results

The test returns the upload speed results in kilobits per second. If the test encountered an error, an error code is returned as a negative number. Here is the meaning of the error codes:

-1 Unable to initialize the Internet functions. If you encounter this error please report it to Cox Business Services for further investigation.

-2 Could not open an FTP connection to the server. This usually occurs because a software or hardware firewall is blocking access to FTP from this computer. It can also occur if the DNS or IP specified in the upload test is not reachable.

-3 Unable to open the temp file, usually due to a server problem such as incorrect permissions on the /temp directory or a full disk.

-4 Error occurred while writing, most often due to a full disk or broken connection.

Troubleshooting

Cox Business Services bandwidth tests require the browser to have JavaScript enabled. The download test does not require ActiveX support and should work with any browser (IE 5+, Netscape 5+, Opera 5+, Mozilla). Results may vary slightly among the browsers because of differences in the way each browser loads and caches files. The ping, traceroute, and upload tests require ActiveX and are designed and tested for IE 5.5 or higher.

Here are some common reasons for test failures or erratic results: