From: "Lewis G Rosenthal" Received: from [192.168.100.201] (account lgrosenthal HELO [192.168.100.24]) by 2rosenthals.com (CommuniGate Pro SMTP 5.0.9) with ESMTPA id 414414 for os2-wireless_users@2rosenthals.com; Sat, 07 Oct 2006 10:21:22 -0400 Message-ID: <4527B7E4.5050300@2rosenthals.com> Date: Sat, 07 Oct 2006 10:21:24 -0400 Organization: Rosenthal & Rosenthal, LLC User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.9a1) Gecko/20060904 MultiZilla/1.8.3.0a SeaMonkey/1.5a MIME-Version: 1.0 To: OS/2 Wireless Users Mailing List Subject: Re: [OS2Wireless]Re: T23 internal cards success References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit I just run the script again to activate the interface. I, too, get the "DHCP Client is not running" message. It's probably a timing thing, where we kill off the one instance but need to insert a do nothing loop (or a few of them) to wait long enough before we try to start it up again. The problem is probably more noticeable with the faster machines than it might have been some years ago, but I never ran this stuff on the older hardware (ThinkPad 360-era). I'll see if I can experiment with this before Warpstock (read: this weekend), and even touch on it during my workshop. Run TOP the next time and see whether DHCPCD may be exiting. Or, kill it from TOP and then run the script. See what you get. On 10/06/06 09:31 pm, Carl Gehr thus wrote : > Lewis, > I don't think that's my problem... > > In this case, the DHCP Monitor shows: > Settings->Monitor_Interface->LAN1 > Status: DHCP Client is not running. > > The first of the above is as it should be. The second is wrong! > i.e., When I display the active tasks [Ctrl-Task_List on eCenter], > there, right at the top is: > DHCPCD.EXE (82) > Methinks DHCPMON is confused! And, it did not work this way a while > back. But, I've forgotten when it changed or what I might have done to > cause the change. FWIW, the DHCP Monitor is V4.1. > > Carl > > On Mon, 25 Sep 2006 09:37:25 -0400, Lewis G Rosenthal wrote: > > >> Carl, I've found that when that issue occurs, I simply wait a bit, and >> then re-start DHCPMON. Eventually, it gets the idea that the interface >> it previously accessed is no longer there, and gets the new information. >> Bug? Probably. I haven't seen it overly persistent, however. >> >> On 09/24/06 11:57 pm, Carl Gehr thus wrote : >> >>> Lewis, >>> >>> In the set of commands you show below [I use them almost verbatim.], >>> there is the command that stops the DHCP Monitor. [ dhcpmon -t ] >>> >>> BUT, I have had problems trying to get the monitor back so it will >>> display the status, config, etc., of the newly started LAN1. I've >>> tried specifying: >>> dhcpmon -i LAN1 >>> but this seems to do absolutely nothing. >>> >>> Can this be done? What, if anything, am I missing? >>> >>> TIA, >>> Carl >>> >>> -- 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 ------------------------------------------------------------