Share via

Troubleshooting Wireless LAN (802.11) Testing

  • Article

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

The following list describes some common troubleshooting tips for WLAN testing:

  • Changes that you made to devices on DTM clients machines are not reflected in DTM Studio. For example, the machine is expected to be in the Ready state but it is not.

    1. Open a Command Prompt window on the client machine, and then run net stop wttsvc.
    2. Run net start wttsvc. This command will update the C:\wtt\JobsWorkingDir\AssetCfg\Log\ directory.
    3. Refresh the Device Console window in DTM Studio. You might have to wait several minutes for the DTM controller to poll the client machine for changes in its device list.

  • Machines have not been discovered for the machine pool.

    1. Open the Job Monitor window in DTM Studio.
    2. Select the Show Query Builder button at the top of the screen.
    3. Click the Machine Query tab.
    4. Define search parameters for the machines that you are looking for. Typically, you can set a single rule such as "DataStore equals 'Controller Name'".
    5. Right-click the rule that you just defined, and then click Execute. An extensive list of machines should populate the Machines list below the query fields that you defined.
    6. Drag any machines in the Machines list into new machine pools that you created.

  • Machines do not seem to run jobs that are scheduled for them.

    1. Open the Job Monitor window in DTM Studio.
    2. In the Machine Pool tab, select the machine pool that you expect to be running jobs.
    3. For each machine in that pool, verify that its status is Ready.
    4. If a machine's status is not Ready, right-click the machine, point to Change Status, and then click Reset.
    5. After a few minutes, refresh the screen and the status will change to Ready.
    6. Schedule and start the jobs again.

  • Problems with installing the Test SoftAP driver on the topology: Device Manager reports code 52

    Do not install the x64 Test SoftAP driver before installing the DTM client. When the DTM client is installed, the Root Certificate is installed. Because the Test SoftAP driver signing depends on installation of the Root Certificate, the device manager reports device code 52.

  • Configuring NDISTest for stand-alone execution

    Installing NDISTest separate from DTM Studio enables you to execute individual tests. A DUT, SUT, and Test SoftAP needs to be configured to enable stand-alone execution.

    Note All test machines must use the same processor architecture.

    Note  To troubleshoot the NDISTest, try attaching a debugger to the test machine.

  • Configuring a Support Device Under Test (SUT)

    1. Copy all NDISTest binaries and sub directories from the following DTM controller:

      \\<ControllerMachine>\tests\<architecture>\nttest\nettest\ndis\ndistest.net\

      <ControllerMachine> is the name of the DTM controller computer and <architecture> is either x86 (for x86-based processors) or amd64 (for x64-based processors).

    2. Launch NDISTest.exe from the install directory. When the main form opens, select Server from the File menu to launch the server form.

    3. Select the message device from the Message Device list. This device must be IP-enabled and on the same subnet as the client message device that will be set up later.

    4. Select SUT device(s) from Support Devices. The support device selected on this server from will be visible to the client after the server is started.

    5. Select the "server" job from Jobs. This is the server side test that will be launched after you click the start button.

    After all the options have been selected, click Start to start the server.

  • Configuring a Test Software Access Point (Test SoftAP)

    1. Copy all NDISTest binaries and sub directories from the following DTM controller:

      \\<ControllerMachine>\tests\<architecture>\nttest\nettest\ndis\ndistest.net\

      <ControllerMachine> is the name of the DTM controller computer and <architecture> is either x86 (for x86-based processors) or amd64 (for x64-based processors).

    2. Install SoftAP driver for both of the Atheros WLAN devices on the Test SoftAP. You can install this driver from Device Manager, which you can open by running devmgmt.msc from a command prompt. Complete the following step:

      In Device Manager, install the driver for SoftAP stations from \\<ControllerMachine>\Tests\<architecture>\nttest\nettest\ndis\NDISTest.net\SoftAPMiniport\

      <ControllerMachine> is the name of the DTM controller computer and <architecture> is either x86 (for x86-based processors) or amd64 (for x64-based processors), depending on the processor architecture of the DTM client machine that have the SoftAP devices.

    3. Launch NDISTest.exe from the install directory. When the main form opens, select Server from the File menu to launch the server form.

    4. Select the message device from the Message Device list. This device must be IP-enabled device and on the same subnet as the client message device that will be set up later.

    5. Select the AP device(s) from AP Devices. AP devices selected on this server will be visible to the client after the server is started.

    6. Select the "server" job from Jobs. This is the server side test that will be launched after you click the start button.

    After all the options have been selected, click Start to start the server.

  • Configuring the Device Under Test (DUT)

    1. Copy all NDISTest binaries and sub directories from the following DTM controller:

      \\<ControllerMachine>\tests\<architecture>\nttest\nettest\ndis\ndistest.net\

      <ControllerMachine> is the name of the DTM controller computer and <architecture> is either x86 (for x86-based processors) or amd64 (for x64-based processors).

    2. Launch NDISTest.exe from the install directory. When the main form opens, select Client from the File menu to launch the client form.

    3. Select the test target from the Test Target list. For network device, this test target should be Miniport.

    4. Select the test device from the Test Device list. This must be a vendor-specific test device.

    5. Select a message device from the Message Device list. This should be an IP-enabled device that is on the same subnet as the server message device. After the message device has been selected, the AP device section should be displayed and the server AP device should be available in the list.

    6. Select a support device from Support Devices. This must be a vendor-specific support device.

    7. Select an AP device from AP Devices. This must be the AP device that was select on the server side.

    8. Select the tests from the Jobs section that will be run after the client is launched.

    After all the options have been selected, click Start to start the client. Any jobs that were selected will begin execution. Test results will be stored on the client in the following logging sub-folder:

    <NDISTestRootFolder>/logs/<AdapterName>/

  • Configuring Client Packet Capture

    1. Configure a test topology for stand-alone execution. For more information, go to "Configuring NDISTest for stand-alone execution."

    2. Setup a second SUT. For more information, go to "Configuring a Support Device Under Test (SUT)."

    3. Launch NDISTest.exe from the install directory. When the main form opens, select Debug from the View menu to launch the Packet Capture section on the client.

    4. Select a Capture device from Packet Capture. This must be a Support device that was selected on the server side.

    5. From Jobs, select the tests that will be run after the client is launched.

    6. After all of the options have been selected, click Start to start the client.

    7. Packet captures corresponding to the Tests will be generated on the Server with the capture device. The logs will be in the following logging sub-folder:

      <NDISTestRootFolder>/logs/<AdapterName>/

  • Troubleshooting when the Packet Capture section does not show up on client

    Verify that the message center user interface is closed. If the NDISTest user interface is not maximized, the Packet Capture section may be hidden behind the message center user interface.

 

 

Build date: 9/14/2012