Prerequisites for the RAS Authentication Test
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
The following tables show the hardware requirements for the RAS Authentication Test.
| Requirements | Description |
|---|---|
Windows Embedded CE device |
The device being tested |
RAS server with serial cable |
Should accept incoming clients without authentication. Must be connected to the Windows Embedded CE device via a serial cable. |
VPN server with Ethernet or other network connection |
Must be reachable over the network for VPN test cases (PPTP and L2TP). The VPN server must accept all authentication protocols and must have dial-in permission for the username given in the command line. |
Note
If you do not have the serial cable setup, you can skip the relevant test cases by specifying only the desired test cases using the -x option in Tux.
The following tables show the software requirements for the RAS Authentication Test.
| Requirements | Description |
|---|---|
Tux.exe |
Test harness, required for all tests |
Kato.dll |
Logging engine, required for all tests |
PPPAuth.dll |
Library containing the test cases |
The RAS Authentication Test requires SYSGEN_PPP for DCC cases, SYSGEN_PPTP for PPTP cases, and SYSGEN_L2TP for L2TP cases. If you do not have one or more of these SYSGENs, you can exclude the relevant test cases by specifying only the desired test cases w the -x** option in Tux.**