Message-ID: <41DEEC4F.4020109@2rosenthals.com>
Organization: Rosenthal & Rosenthal
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8a6) Gecko/20041130 MultiZilla/1.6.4.0b Mnenhy/0.6.0.104
MIME-Version: 1.0
References: <E1ClvFB-0000J2-00@pop-a065d01.pas.sa.earthlink.net> <41DB0D2F.3070504@hccnet.nl> <41DCC86C.2070908@2rosenthals.com> <41DD00FA.3030000@hccnet.nl> <41DD65CA.3000105@2rosenthals.com> <41DDBD7D.2070504@hccnet.nl>
In-Reply-To: <41DDBD7D.2070504@hccnet.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Fri, 07 Jan 2005 15:08:47 -0500
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Lewis G Rosenthal <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] wlanstat question

On 01/06/2005 05:36 pm, Kris Steenhaut thus wrote :

<snip>

> Hmm, may I remind you, before you bothering all, I already have done 
> the obvious, that is:
>
> just the Artem driver in the config.sys
> just in setup.cmd: dhcpstrt -i lan0 and the loopback etc.
>
Actually, your wireless adapter is lan1 (according to the data you 
posted from netstat), so the command should be:

dhcpstrt -i lan1

However, I don't think this will make a difference...

> Should have worked, shouldn't it?
>
Well, assuming the correct interface is specified, yes, it should.

> But the answer was "dhcp server didn't get parameters".
>
> The same exercise with the Genprism drivers do give exactly the same 
> result ""dhcp server didn't get parameters".
> It is always like that when dhcp is set to a wireless lanx 
> (jacaranda). OTOH, dhcp works as it should when set to a wired lanx 
> (onboard intel nic).
>
> I have checked with Frank Vos, he has exactly the same card as I have, 
> and at his Laptop, a T23 IIRC, DHCP is working with Artem drivers as 
> well as with Genprism (remember, Artem drivers don't work here at all, 
> except for the flashing lights).
>
Which again leads me to believe that this is software-related 
(somewhere), and probably in the DHCP client and not the router (good 
news, actually).

> I still wonder whether the internal wireless nic (intel) of my T41 
> couldn't be in the game. After all, there is no option in the bios to 
> disable the intel onboard nic. Meaning it is always powered on. A 
> radiating device that is powered on, always radiates, doesn't it?
>
You're obviously able to connect with a ststic address, so there's no 
interference from the internal card. As IP isn't bound to the internal 
card (for obvious reasons), it can't be interfering with obtaining an 
address. The router obviously doesn't see the card, either.

-- 
Lewis
------------------------------------------------------------
Lewis G Rosenthal, CNA 
Rosenthal & Rosenthal, LLC
Accountants / Network Consultants 
  New York / Northern Virginia           www.2rosenthals.com
eComStation Consultants                  www.ecomstation.com
Novell Users International        www.novell.com/linux/truth
------------------------------------------------------------ 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).

For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=