From: "Stanley Sidlov" Received: from mxout2.mailhop.org ([63.208.196.166] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 326298 for os2-wireless_users@2rosenthals.com; Thu, 31 Aug 2006 17:00:49 -0400 Received: from mxin1.mailhop.org ([63.208.196.175]) by mxout2.mailhop.org with esmtp (Exim 4.51) id 1GIteX-000MPG-Kn for os2-wireless_users@2rosenthals.com; Thu, 31 Aug 2006 17:00:47 -0400 Received: from admin.nni.com ([216.107.0.100]) by mxin1.mailhop.org with esmtp (Exim 4.51) id 1GIteX-000AIZ-HJ for os2-wireless_users@2rosenthals.com; Thu, 31 Aug 2006 17:00:45 -0400 X-Scan:Scanned for Virus By NuNet Received: from [67.81.124.65] (account stanleys@cybernex.net) by admin.nni.com (CommuniGate Pro POP 4.1.8) with XMIT id 523064167; Thu, 31 Aug 2006 17:00:43 -0400 To: "OS/2 Wireless Users Mailing List" Date: Thu, 31 Aug 2006 17:00:44 -0400 (EDT) Reply-To: "Stanley Sidlov" Priority: Normal X-Mailer: PMMail 2.20.2300 for OS/2 Warp 4.5 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: [OS2Wireless]Re: DHCP Problems Message-ID: X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -2.5 (--) On Thu, 31 Aug 2006 12:44:40 -0400, Lewis G Rosenthal wrote: >Maybe in Hakan's situation he was dealing with a BOOTP server and not a >DHCP server? Though even there, one would think that he would at least >get a local address, and naturally, there were other transient Windows >clients who/which were able to get (supposed) DHCP information without >incident. I would have been interested in trying with a Linux client >which has a more modern dhcpcd implementation than we have. windows being what it is, it's also possible that some windows dhcp request/parameter that was not supplied by OS/2's requestor hung or caused a timeout on the server's thread.... I've been in a number of hotels the last few months and find that without IE even on windows it's impossible to get an IP for more than a minute or two, as Firefox on windows is resistant to the redirect to the (I guess) radius server the router is trying to force me to. Wayport is particularly good at knocking you off-line without the agreement within a few minutes, others may allow you on, once the redirected page is presented without the 'agreement' being actually clicked.