From: "Hakan" Received: from mxout1.mailhop.org ([63.208.196.165] verified) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTP id 392253 for os2-wireless_users@2rosenthals.com; Thu, 28 Sep 2006 09:35:16 -0400 Received: from mxin1.mailhop.org ([63.208.196.175]) by mxout1.mailhop.org with esmtp (Exim 4.51) id 1GSw2h-0003UZ-8A for os2-wireless_users@2rosenthals.com; Thu, 28 Sep 2006 09:35:12 -0400 Received: from [217.160.230.41] (helo=mout.perfora.net) by mxin1.mailhop.org with esmtp (Exim 4.51) id 1GSw2g-0009Eb-E6 for os2-wireless_users@2rosenthals.com; Thu, 28 Sep 2006 09:35:10 -0400 Received: from [70.20.163.170] (helo=progstn) by mrelay.perfora.net (node=mrelayus1) with ESMTP (Nemesis), id 0MKp2t-1GSw2e0Nlv-0001sW; Thu, 28 Sep 2006 09:35:09 -0400 To: "OS/2 Wireless Users Mailing List" Date: Thu, 28 Sep 2006 09:35:06 -0400 (EDT) Reply-To: "Hakan" Priority: Normal X-Mailer: PMMail 2.20.2382 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: <0MKp2t-1GSw2e0Nlv-0001sW@mrelay.perfora.net> X-Provags-ID: perfora.net abuse@perfora.net login:15932942dc79fdd7ddce274cd78af770 X-Mail-Handler: MailHop by DynDNS X-Spam-Score: -2.3 (--) Lewis, The conference sounds interesting. Re your problem with getting a DHCP address and the troubles I had a month ago, I was back at that same office last week and the issue was resolved -- the IT person told me that the address pool was exhausted and anyone logging one would have had the same problem, regardless of OS. Now I can get a DHCP address but am unable to resolve any name lookups... (did not have a chance to discuss that issue with the IT person.) On Wed, 27 Sep 2006 23:50:45 -0700, Lewis G Rosenthal wrote: >On 09/01/06 03:24 pm, Stanley Sidlov thus wrote : >> On Fri, 01 Sep 2006 18:17:37 -0400 (EDT), Stanley Sidlov wrote: >> >> >>> option 60 in Windows XP client. It is currently at "MSFT 5.0" value. >>> http://en.wikipedia.org/wiki/DHCP >>> >> >> and a BTW: http://articles.techrepublic.com.com/5100-1035_11-5498436.html >> "How to setup vendor class to deny access to unauthorized machines.." >> >> >First practical use of this DHCP client daemon option, Stan: > >I'm in Milpitas, CA for a two-day workshop on large-scale Wi-Fi >deployments (see http://www.moonblinkwifi.com/pd_training.cfm). Here at >the Beverly Heritage Hotel, there are no less than four 802.11b networks >visible from my room, all at between 65% and 70% signal, all >unencrypted, and all - naturally! - on channel 11. > >iBahn provides the hotel Wi-Fi, and while I have never to date >experienced an issue getting a DHCP address, I just hung forever >tonight, waiting. I rebooted; same thing. Finally, I set option 60 to >"MSFT 5.0" and bounced the box a final time. Presto! DHCP config came >right down. Coincidence? Perhaps. However, I think it may very well be >that blasted option. Perhaps W2K3 Server specifically looks for that by >default? Not that I know for a fact what is behind the iBahn AP... > >Anyway, I wanted to pass this along. > >Thanks again for the good info. > >-- >Lewis >------------------------------------------------------------ >Lewis G Rosenthal, CNA, CLP, CLE >Rosenthal & Rosenthal, LLC >Accountants / Network Consultants > New York / Northern Virginia www.2rosenthals.com >eComStation Consultants www.ecomstation.com >Novell Users Int'l www.novell.com/openenterpriseserver >Need a managed Wi-Fi hotspot? www.hautspot.com >------------------------------------------------------------ > > >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >This message is sent to you because you are subscribed to > the mailing list . >To unsubscribe, E-mail to: >To switch to the DIGEST mode, E-mail to >To switch to the INDEX mode, E-mail to >Send administrative queries to >To subscribe (new addresses), E-mail to: and reply to the confirmation email. > >This list is hosted by Rosenthal & Rosenthal >P.O. Box 281, Deer Park, NY 11729-0281. Non- >electronic communications related to content >contained in these messages should be directed >to the above address. (CAN-SPAM Act of 2003) > >=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= >