AW-GM120 User’s Guide
Document Conventions Text Conventions Bold Bold type within paragraph text indicates commands, file names, directory names, paths, output, or returned values. Example: The DK_Client package will not function, except when the wdreg_install batchfile is used. Italic Within commands, italics indicate a variable that the user must specify. Example: mem_alloc size_in_bytes Titles of manuals or other published documents are also set in italics. Courier The Courier font indicates output or display.
Revision History Revision Description of Changes 2005/10/20 Initial AW-GM120 release.
Contents Preface 4 About this Document 4 1 Installation 5 ACU Installation and Driver Update 5 Driver Installation 8 Windows NT 4.0 Installation 10 Windows NT 4.0 Driver Installation and TCP/IP Setup 10 Windows NT 4.
Preface This user's guide provides the necessary information for first-time users to successfully install the AW-GM120 network driver interface specification (NDIS) driver. This guide also provides information for users who wish to upgrade the AW-GM120 NDIS driver from previous releases. This guide describes the steps required to install NDIS drivers for the AW-GM120 Wireless Network Adapter in Windows 2000, Windows XP, Windows Millennium Edition, Windows 98SE, and Windows NT 4.0.
1 Installation This chapter describes using the AW-GM120 installer to install the Atheros Client Utility (ACU) and driver. AW-GM120 provides an InstallShield utility to upgrade the NDIS driver, if a previous release is installed, and to install the ACU. ■ Use the ACU to configure the device driver. The ACU provides extensive online help to aid in configuring the device. ■ Use the InstallShield Updater to uninstall the NDIS driver and ACU application and remove them from the Device Manager.
4. The installer program detects any previous installations. a. If the installer program finds a previous installation, the Previous Installation Detected window appears. Choose to update the previous installation. Click Next. Figure 1-1. Installer Initial Setup (Previous Installation Detected) b. If the installer program finds no previous installation, the installation Setup Type window appears with three setup options. Choose the installation type.
6. Choose the setup directory. The default is C:\Program Files\Atheros. Click Next. 7. Choose the program folder for the start menu. The default is Atheros. Click Next. 8. For a Windows XP installation, the next screen defines the Windows Zero Configuration. Windows XP Zero Configuration provides functionality to automatically try to connect the STA to available wireless networks. For complete information on Windows Zero configuration, see the Microsoft web site.
10. The installation program begins to install the client utility and driver. A “Digital signature Not Found” screen may appear. Click Yes to continue. Figure 1-4. Digital Signature Not Found Window 11. Click OK at the prompt to reboot and complete the installation. Use the ACU to configure the device driver. The ACU provides extensive online help to aid in configuring the device. Access the ACU by double-clicking the tray icon.
Figure 1-5. Install Hardware Device Drivers Window 3. Choose “Search for a suitable driver for my device” and click Next. Figure 1-6. Locate Driver Files Window 4. Check “Specify a location” and click Next. 5. Windows asks for the directory to search for a new Driver in. Enter the directory, then click OK to start Windows searching for the drivers.
Figure 1-7. Driver Files Search Results Window 6. Once Windows finds the driver for the device, click Finish to complete driver installation. Use the ACU to configure the device driver. The ACU provides extensive online help to aid in configuring the device. Windows NT 4.0 Installation This section describes the Windows NT 4.0 driver installation, TCP/IP setup, and ACU installation. Windows NT 4.0 Driver Installation and TCP/IP Setup Windows NT 4.
addresses) is usually obtained from the corporate IT staff. For a simple demonstration, the STA is assigned a static IP address. 7. Choose “Specify an IP address” and enter an IP address and subnet mask. Assigning an IP address and subnet mask allows the STA to interact with the AP or other STAs in the same IP subnet. 8. Click OK to complete the TCP/IP configuration. 9. Restart the system for the changes to take effect. Windows NT 4.
3. Click Search Now. A few files matching these criteria are possible, if previous drivers have not been removed properly. 4. Choose the files that have been found and delete them from the system. 5. To complete the uninstallation, remove \WINNT\system32\drivers folder. 12 the file ar5211.
2 Security This chapter describes setting up security using the Atheros Client Utility (ACU). See the Atheros Client Utility Online Help for more information on configuring the security settings using the ACU. While using the client adapter, encrypting data can protect it as it is transmitted through the wireless network. The ACU allows connection profiles of: ■ No security (not recommended) Link encryption/decryption is disabled, no keys are installed.
■ 802.1X security Enables 802.1X security. This option requires IT administration. This option includes the EAP (with dynamic WEP keys) security protocols: EAP, PEAP, and LEAP. 802.1X is the standard for wireless LAN security defined by IEEE as 802.1X for 802.11, or simply 802.1X. An AP that supports 802.1X and its protocol, EAP, acts as the interface between a wireless client and an authentication server such as RADIUS server, to which the AP communicates over the wired network.
1. In the ACU, edit the security settings by clicking New or Modify on the Profile Management tab. 2. Choose a profile to edit, or name the new profile in the Profile Management window. Enter the SSID of the AP the STA connects to. 3. On the Security tab, choose the WPA/WPA2 radio button. OR: On the Security tab, choose the 802.1X radio button. 4. Choose EAP-TLS or EAP-TTLS from the drop-down menu. To enable EAP-TLS security: 1.
client certificate for authentication. 2. If EAP-TTLS is supported, choose EAP-TTLS from the drop-down menuon the right, then click the Configure button. Figure 2-2. EAP-TTLS Configuration Window 3. Select the appropriate certificate from the drop-down list and click OK. 4. Specify a user name for EAP authentication: Check Use Windows User Name to use the Windows user name as the EAP user name.
Management tab. 2. Choose a profile to edit, or name the new profile in the Profile Management window. Enter the SSID of the AP the STA connects to. 3. On the Security tab, choose the WPA/WPA2 radio button. OR: On the Security tab, choose the 802.1X radio button. 4. Choose PEAP (EAP-GTC) or PEAP (EAP-MSCHAP V2) from the drop-down menu. – PEAP (EAP-GTC) is designed to support one-time Password (OTP), the Windows NT or Windows 2000 domain, and L DAP user databases over a wireless LAN.
Figure 2-3. PEAP (EAP-GTC) Configuration Window 3. Select Use Machine Information For Domain Logon to use the machine name as the security user name. 4. Select the network certificate authority from the drop-down list. 5. Specify a user name for inner PEAP tunnel authentication: – Check Use Windows User Name to use the Windows user name as the PEAP user name. – OR: Enter a PEAP user name in the User Name field to use a separate user name and start the PEAP (GTC) authentication process. 6.
PEAP-xxxxxxxxxxxx, where xxxxxxxxxxxx is the computer's MAC address. Change the login name if needed. 8. Click OK. 9. Enable the profile. To enable PEAP (EAP-MSCHAP V2) security: 1. To use PEAP (EAP-MSCHAP V2) security, the server must have PEAP certificates, and the server properties must already be set. Check with the IT manager. 2. If supported, choose PEAP (EAP-MSCHAP V2) from the drop-down menu on the right, then click the Configure button. Figure 2-4. PEAP (MSCHAP V2) Configuration Window 3.
– Leave the server name field blank for the client to accept a certificate from any server with a certificate signed by the authority listed in the Network Certificate Authority drop-down list. (recommended) – Enter the domain name of the server from which the client will accept a certificate. – The login name used for PEAP tunnel authentication, fills in automatically as PEAP-xxxxxxxxxxxx, where xxxxxxxxxxxx is the computer's MAC address. Change the login name if needed. 7. Click OK. 8. Enable the profile.
LEAP Security The LEAP authentication type uses Cisco Key Integrity Protocol (CKIP) and MMH message integrity check for data protection. The client adapter uses the username and password to perform mutual authentication with the RADIUS server through the AP. To use LEAP security, access the Security tab in Profile Management. 1. In the ACU, edit the security settings by clicking New or Modify on the Profile Management tab. 2.
Use Windows User Name to use the Windows user name as the LEAP user name. OR: Check Manually Prompt for LEAP User Name and Password to manually login and start the LEAP authentication process. – Select to Use Saved User Name and Password by choosing the radio button. Specify the LEAP user name, password, and domain to save and use. 4. Enter the user name and password. 5. Confirm the password. 6.
WPA/WPA2 Security WPA2 Security WPA2 is the next generation of WPA, based on the 802.11i standard.On the STA side, for Microsoft Zero Configuration, install SP2 for Windows XP. Then apply the Microsoft Zero Configuration patch, available at the Microsoft update site. Then install an Atheros WPA2-capable driver and control the connection with Windows. WPA/WPA2 Passphrase Security To use WPA/WPA2 Passphrase security In the ACU, access the Security tab in the Profile Management window. 1.
Pre-Shared Key Security To use Pre-Shared Key (static WEP) security In the ACU, access the Security tab in the Profile Management window. 1. In the ACU, edit the security settings by clicking New or Modify on the Profile Management tab. 2. Choose a profile to edit, or name the new profile in the Profile Management window. Enter the SSID of the AP the STA connects to. 3. On the Security tab, choose Pre-Shared Key (Static WEP). To enable Pre-Shared Key security: 1.
DGT 警語 : 經型式認證合格之低功率射頻電機，非經許可，公司、商號或使用者均不得擅自 變更頻率、加大功率或變更原設計之特性及功能。 低功率射頻電機之使用不得影響飛航安全及干擾合法通信；經發現有干擾現象 時，應立即停用，並改善至無干擾時方得繼續使用。前項合法通信，指依電信法 規定作業之無線電通信。低功率射頻電機須忍受合法通信或工業、科學及醫療用 電波輻射性電機設備之干擾。 本模組於取得認證後將依規定於模組本體標示審合格籤，並要求平台上標示[本 產品內含射頻模組:ID 編號] 25
OEM Installation Info: This device is intended only for OEM integrators under the following conditions: 1) The antenna must be installed such that 20 cm is maintained between the antenna and users, and 2) The transmitter adapter may not be co-located with any other transmitter or antenna. As long as 2 conditions above are met, further transmitter test will not be required.
