Filter
Top Products
7-21
Windows Does Not Detect the RoamAbout PC Card
Windows Does Not Detect the RoamAbout PC Card
If the RoamAbout PC Card was properly working at one time in the client, the problem
could be one of the following:
• The PC Card is no longer properly inserted. Reinsert the PC Card into the PC Card slot.
• The PC Card was removed and reinserted but the computer requires a reboot to
recognize the PC Card. Restart the computer.
• The RoamAbout PC Card driver was improperly removed or corrupted. Remove the
existing driver, as described in the RoamAbout 802.11 PC Card Drivers and Utilities
Setup and Installation Guide. Then reinstall the driver.
Client Cannot Connect to the Network
This situation may occur in one of the following situations:
• Wireless network name is incorrect. The wireless network name is case sensitive.
• If using ANY as the wireless network name or the field is blank, verify that the
RoamAbout AP has disabled Secure Access.
• If the wireless network is using MAC Address authentication, the client’s MAC
address must be configured on the RADIUS server.
• If the wireless network is using 802.1X Rapid Rekeying, the client must also be
configured for Rapid Rekeying. The procedure to configure a Windows XP client for
Rapid Rekeying is in “Set Up Rapid Rekeying on the Clients” on page 5-38.
• If the wireless network is using encryption, make sure that encryption is enabled and
that the correct encryption key is entered in the correct key position (1, 2, 3, or 4).
• The Microsoft Windows workgroup name is incorrect. Follow the procedure in the
next section to check the network protocols.
• The driver is not loaded. Install the driver as described in the RoamAbout 802.11 PC
Card Drivers and Utilities Setup and Installation Guide.
• There is a device conflict as described in “Device Conflict on a Windows System”
on page 7-23.
• The PC Card is defective.
In an ad-hoc configuration, the RoamAbout Client Utility could show the other computers
in the ad-hoc network but these computers are not shown in the Network Neighborhood.
The most likely cause is that the computers are not using the same workgroup name.