From: "Lewis G Rosenthal" Received: from [192.168.100.201] (account lgrosenthal HELO [192.168.100.26]) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTPA id 325640 for os2-wireless_users@2rosenthals.com; Thu, 31 Aug 2006 12:44:40 -0400 Message-ID: <44F711F8.2090003@2rosenthals.com> Date: Thu, 31 Aug 2006 12:44:40 -0400 Organization: Rosenthal & Rosenthal, LLC User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9a1) Gecko/20060701 MultiZilla/1.8.2.0i SeaMonkey/1.5a MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless]Re: DHCP Problems References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 08/31/06 11:36 am, Andy Willis thus wrote : > Hakan wrote: >> This is a wired question but the participants here are so knowledgeable >> I am sure this is old hat... >> On a business trip I encountered a network where I was unable to log on >> using my ThinkPad and the wired NIC. The network supposedly used DHCP >> but my system was unable to obtain an IP address despite multiple >> attempts, even after rebooting (also on different days). I eventually >> was able to log on using a static IP address but also had supply the >> DNS addresses as I was otherwise unable to surf the 'net. I should add >> that this was an office network with many users and others temporarily >> using it like myself had no problems with their Win systems. >> >> What might the problem have been? TIA. >> > This sounds similar (though it may not actually be related) to an > issue that I have recently ran into that previously I would have said > would not be an issue. I have a customer that has recently gone from > using static ip's nationwide to almost all of them using dhcp with > regional dhcp servers. During the transition the users were switched > via a Tivoli push. Some of these user were suddenly getting "cable > disconnect". I ended up having to change, of all things, the dns > suffix search order. I don't recall now even how I stumbled on that > as being the issue but afterwards found that those that had that > problem (and happened to have admin rights) I could change the dns > suffix search order and get them connected. What is really odd is > that it is not universal... some people connect just fine without > anything set in there. To test this though, I would after getting > them connected remove the dns suffix search order and it would go back > to "Cable disconnect", they then got connected again when adding it > back in. > Andy > Seems odd that the DNS suffix search order would come into play that early in the negotiation. One would think that the client would first need the DNS server address (supplied via DHCP, along with everything else) before even attempting a DNS lookup. 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. -- 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 ------------------------------------------------------------