From: "Ed Durrant" Received: from [192.168.100.201] (HELO mail.2rosenthals.com) by 2rosenthals.com (CommuniGate Pro SMTP 5.1.16) with ESMTP id 1863616 for os2-wireless_users@2rosenthals.com; Sat, 24 Oct 2009 18:35:26 -0400 Received: from secmgr-va.2rosenthals.com ([162.83.95.194] helo=mail2.2rosenthals.com) by secmgr-ny.randr with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1N1pCi-0002gW-Uh for os2-wireless_users@2rosenthals.com; Sat, 24 Oct 2009 18:35:26 -0400 Received: from nschwqsrv03p.mx.bigpond.com ([61.9.189.237]:19469) by mail2.2rosenthals.com with esmtp (Exim 4.69) (envelope-from ) id 1N1pCd-0002fz-1g for os2-wireless_users@2rosenthals.com; Sat, 24 Oct 2009 18:35:15 -0400 Received: from nschwotgx01p.mx.bigpond.com ([58.165.212.68]) by nschwmtas06p.mx.bigpond.com with ESMTP id <20091024210309.WXBX22839.nschwmtas06p.mx.bigpond.com@nschwotgx01p.mx.bigpond.com> for ; Sat, 24 Oct 2009 21:03:09 +0000 Received: from [192.168.100.2] (really [58.165.212.68]) by nschwotgx01p.mx.bigpond.com with ESMTP id <20091024210308.GLYA1743.nschwotgx01p.mx.bigpond.com@[192.168.100.2]> for ; Sat, 24 Oct 2009 21:03:08 +0000 X-CTCH-RefID: str=0001.0A020203.4AE38123.01E5,ss=1,fgs=0 Message-ID: <4AE36B92.3060801@durrant.mine.nu> Date: Sun, 25 Oct 2009 08:03:14 +1100 User-Agent: Thunderbird 2.0.0.21 (OS/2/20090411) MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless] Re: Cannot get DHCP References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authentication-Info: Submitted using SMTP AUTH PLAIN at nschwotgx01p.mx.bigpond.com from [58.165.212.68] using ID edward.durrant@bigpond.com at Sat, 24 Oct 2009 21:03:08 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A150204.4AE36B8D.0013,ss=1,fgs=0 X-Spam-Score: 0.0 (/) X-Spam-Report: _SUMMARY_ Stuart Updike wrote: > Ed Durrant wrote: >> Hi Stuart - "a light just went on here" - the "magic" of WiFi (and it >> is a magic, not a science!) is that if anything is wrong with your >> security settings, it does not always come up with the error message >> you expect. A connection but no IP address IS one possible condition >> that occurs. >> >> Given that you have tried different WiFi adapters and tried >> connecting to different WiFi routers, I am starting to think this may >> be a security setting problem. >> >> A lot of the older cards can only support 802.11b (not G or N) and a >> lot will not support WPA or WPA2 encryption only WEP. >> >> On your WiFi router, have you tried turning off all security and make >> sure that it is set to support all speeds of WiFi - i.e. 802.11b and >> 802.11G at least? >> >> I would not leave the router like this as it's an "open door" for >> those in range to use your network, but to test you could do this. >> Ideally at the end of the day you need to be running 802.11G or N and >> WPA2 security, but if the hardware you have wont support this, then >> you will need to set it to the best you can get but initially lets >> see if you can get things working totally without security enabled. > > Hello Ed, > > The original internal wireless card was 802.11b. Then I tried an Intel > 2200 b/g card. Then I tried a PCMCIA Cisco 350 b card. At all times > the security was turned off on my router. I understand that it needs > to be tightened up when I am not testing. The router is a b router. > > I appreciate you suggestions! > > Stu Updike > Bedford, Texas > > That sounds like it's not a security issue then. By the way do you have other devices working with the router wirelessly? -- Cheers/2 Ed eComStationAustralia podcast RSS feed http://eComStationAustralia.podbean.com/feed or iTunes Warpstock Europe at Stralsund, Germany 12-15 November 2009 http://www.warpstock.eu