Message-ID: <41DD65CA.3000105@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>
In-Reply-To: <41DD00FA.3030000@hccnet.nl>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Thu, 06 Jan 2005 11:22:34 -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 04:12 am, Kris Steenhaut thus wrote :

>
>
> Lewis G Rosenthal schreef:
>
>> Kris, how many addresses do you have assigned to the pool in the router,
>
>
> None. The router always was/is with in dhcp enabled.
>
The address pool must have at least one available address for it to be a 
"pool." Doesn;t the router tell you how many clients may obtain 
addresses??????

>> and how many addresses have already been assigned?
>
>
> router always assings 192.168.2.101 to the jacaranda (with mac address 
> jacaranda listed too).
>
But at the client side running ifconfig lan1 you don't see an address 
assigned, correct? What does netstat -n show for lan1 (try netstat -n | 
more or netstat -n > netstat.txt)?

>> Clear the address assigned to the Jacaranda in the router, and then 
>> attempt to obtain an address via XWLAN.
>>
> Been already there many times.
>
> - dhcp doesn't work

So after clearing 192.168.2.101 at the router, the router still assigns 
it again to the card but the card doesn't see the address? Or.... you 
haven't actually cleared the DHCPTAB in the router (look for something 
in the router to release or delete the client)?

> - when in xwlan set to "manually" and ip address 192.168.2.102, then 
> connection is established and working for 100 %.
>
If the router has truly assigned an address to the correct MAC of the 
card, using a second address with the same MAC (on the same network) 
should generate errors. If it doesn;t we may be looking at the wrong 
side of the equation, and the problem may lie in the router's firmware.

-- 
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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=