From: "Andy Willis" Received: from mxout4.mailhop.org ([63.208.196.168] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 549428 for os2-wireless_users@2rosenthals.com; Tue, 21 Nov 2006 15:14:37 -0500 Received: from mxin2.mailhop.org ([63.208.196.176]) by mxout4.mailhop.org with esmtp (Exim 4.51) id 1Gmc0p-000FCj-Sx for os2-wireless_users@2rosenthals.com; Tue, 21 Nov 2006 15:14:36 -0500 Received: from wr-out-0506.google.com ([64.233.184.230]) by mxin2.mailhop.org with esmtp (Exim 4.51) id 1Gmc0p-000Jbu-Ka for os2-wireless_users@2rosenthals.com; Tue, 21 Nov 2006 15:14:35 -0500 Received: by wr-out-0506.google.com with SMTP id i23so605472wra for ; Tue, 21 Nov 2006 12:14:35 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding; b=eLpGjweg38VLYyidzhaYWo9g0t5aya9tjB2wdxi7CFM78MGkuNYC/5TTBn5XTaz93sHUDeyRI55MYkKPGKPBMpUeGgjWX0rrUSJtubp6H+IMMSVPKZnA0GZigAgZpB1t7LE1/ncZjzxrD2lKEdLOmieuoCAzFIz4ekCnwP6zoKs= Received: by 10.100.142.12 with SMTP id p12mr1490625and.1164140074966; Tue, 21 Nov 2006 12:14:34 -0800 (PST) Received: from ?192.168.1.88? ( [32.97.110.142]) by mx.google.com with ESMTP id 43sm15910857wri.2006.11.21.12.14.33; Tue, 21 Nov 2006 12:14:34 -0800 (PST) Message-ID: <45635E29.9020104@gmail.com> Date: Tue, 21 Nov 2006 13:14:33 -0700 Reply-To: abwillis1@gmail.com User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9a1) Gecko/20061111 SeaMonkey/1.5a MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless]Issues with WPA References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -0.5 (/) Chris Clayton wrote: > I have not been able to get WPA to work between my TP T41 internal wifi > and an Actiontec DSL gateway. WEP is working without problems. > > Genmac 2.00 & XWLAN 3.00 installed without issues and the correct > driver for the Intel 2100 miniPCI card is loaded. > > I copied the profile for WEP to another WPA profile and changed the > security settings only to 'WiFi Protected Access (WPA2-PSK)' and > entered a preshared key. I then changed the DLS gateway to WPA with > the same key. When I try to activate the WPA profile I usually get an > icon with red bars indicating that it is connected but out of range. > The T41 is 2 feet from the DSL gateway. Occasionally I get an icon > with green bars indicating a strong signal. In either case, I cannot > communicate over wifi with WPA enabled even though the routing and IP > addresses are correctly assigned. > > I did try 'WiFi Protected Access (WPA-PSK)' but just got a 'searching > for connection' icon. > > Other issues: > 1) I am occasionally getting a trap e when trying to activate the WPA > profiles. This may or may not be related to the fact that I have > Object Desktop installed as, once, the system trapped when I opened the > Tab Launchbar with the WEP profile active. > > 2) I still need to use a script when switching between a wifi and a > wired connection. This is because when using the method described in > the manual, the configuration for lan0(1) are not completely deleted > when switching to lan1(0) > > 3) Netbios over TCP/IP does not start is I follow the instructions for > configuring setup.cmd for networks that switch between a wifi and wired > connection. The instructions state that the wifi lan configuration > should not be in setup.cmd, rather left to XWLAN. I have found that I > need both LAN0 (wifi) and LAN1 (wired) configured. I put in a 'dummy' > ip address for LAN1, so that both subnets are present when the system > starts. This may be needed because, in config.sys, a tcpbeui protocol > is run after the call to run setup.cmd: > > CALL=E:\OS2\CMD.EXE /Q /C E:\MPTN\BIN\MPTSTART.CMD >NUL > RUN=E:\IBMCOM\PROTOCOL\NBTCP.EXE > > Note: once the system is running, then lan0(1) can be deleted when > switching between lan1(0). > > Cheers, > > Chris Clayton > Have you tried connecting via the wpa-supplicant.exe? I found that I can only way I use xwlan to use wpa is to limit the psk to 43 characters though wpa-supplicant allows 63. Andy