Message-ID: <40EE02E2.6080903@comcast.net>
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8a2) Gecko/20040702
MIME-Version: 1.0
References: <auto-000323732728@admin.nni.com> <40E2B816.1020806@comcast.net> <40E44F2D.9020609@clanganke.de> <40E4665F.7000500@comcast.net> <40E685DD.4020900@clanganke.de> <40E706E6.5030307@comcast.net> <40EC5882.8000505@clanganke.de>
In-Reply-To: <40EC5882.8000505@clanganke.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Date:  Thu, 08 Jul 2004 20:28:50 -0600
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  Andy Willis <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: [OS2Wireless] WiFi Wiget XLan Monitor ??

Christian Langanke wrote:

> Andy Willis wrote:
>
>> The only interface that is configured in TCP/IP configuration is Lan 
>> 0 (didn't make sense to set Lan 7 to static IP as I wanted DHCP and 
>> it wouldn't allow DHCP as only one can be configured in there).  
>
>
> If the number left to the TCP/IP protocol bound to your WLAN device 
> driver within MPTS is 0, you must set the interface in the WLAN 
> monitor to lan0, and _nothing else_. Setting it to any other value 
> will help you nothing. "lan7" is the default value only in order to 
> not hurt any running IP interface.
>
>> I tried to close xcenter and restart it but it didn't seem to do 
>> anything.  I finally tried opening properties and just closing them 
>> but it didn't have and affect either.  It wasn't till I switched to 
>> Lan 1 and closed out the properties dialog and switched back to Lan 0 
>> and closed the properties dialog that it configured.  I haven't 
>> applied the fix that was released yet, I will try that and see if 
>> that makes a difference
>
>
> The fix was for the install routine only. If the widget shows up in 
> the Xcenter, everything worked so far.
>
> Hmm, cannot think of a reason for this. Lets get through what I do on 
> a "new" system, where the WLAN driver is installed. I recommend to do 
> that with the stand-alone executable first.
>
>     launch wlanstat.exe
>
>     create a new profile with no TCP/IP configuration and select that 
> profile
>
>     the widget now must get "green", showing a working WLAN radio 
> connection. If that fails, you have other problems, and, of course, 
> the IP configuration takes place only if a radio connection could be 
> established. If you have problems setting up the radio connection, 
> make sure that the SSID is set correct and check for the proper 
> encryption. That is if your access point uses encrpytion, you must 
> configure the same level and the same WEP keys. Refer to the online 
> help for the security page.
>
>     when the radio shows green, modify the TC/PIP config for that 
> connection profile to configure a manual address first. Right after 
> closing the properties of the profile and the selection dialog, the 
> configuration takes place. Move the mouse over the monitor to view the 
> IP address set, it should have the configured value. Play around with 
> several IP address values of your IP subnet, it should change every time.
>
>     export that working profile and reimport it to an empty slot, then 
> open the properties of it and add "DHCP" to the name, change the 
> TCP/IP config to DHCP. Now close this profile and switch back and 
> forth between the two profiles, either setting the IP address manually 
> or via DHCP.
>
> Please let me know if that works.
>
> thanx, Christian
>
> P.S.: Possibly I should add that to the online help...
>
I figured out that I can only use the first profile.  The others never 
take the selection (caret never is next to them, even if the first 
selection is blank -- then there is no caret).  I do connect to the 
wireless piece but dhcp is not established on its own.  I did find that 
if I shut off the radio and then reenable it then dhcp will get an 
address.  For me that is all I need but will try some other tests if you 
want. 
This is the cisco 340 pcmcia card -- flashed with the 350 firmware.  I 
am using Jens' driver. 
Oh one thing I learned while doing some different testing with this.... 
at one point I removed tcpip from the binding to the wireless card in 
MPTS and put in Netbios instead. --- this was very bad.  When the widget 
went to enable tcpip the system locked hard.  Ctrl-Alt-Num-Num didn't 
even do anything, I had to power the system off.
Andy
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=