MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID:<20040520201038.GA91915@mail15e.boca15-verio.com>
Date:  Thu, 20 May 2004 20:10:37 -0500
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  "David Butkovich" <os2-wireless_users@2rosenthals.com>
To:  "os2-wireless_users@2rosenthals.com" <os2-wireless_users@2rosenthals.com>
Subject: [OS2Wireless] Cisco 340 not working

On Thu, 20 May 2004 19:20:25 -0400, Julian Thomas wrote:

>I took the plunge to set up a wireless capability (most of the house is on
>a wired network but I wanted to be able to use a thinkpad T23 untethered). 
>I have a Dlink DWL700AP access point and the Cisco 342 pc card.  Needless
>to say, it's all working smoothly under Win2k.
>
>eCS is a different story.  It wouldn't work, so I installed the latest
>cardbus drivers from the eCS website.  They work - at least I can use a pc
>card modem and a cf adapter and read the cf card.  However, the wifi is
>still not working under eCS (yet).
>
>Situation is that I have a wired NIC in the machine - assigned to Lan0
>[since it was the first one there] using dhcp.  I installed the cisco
>drivers from the file that I found on hobbes, and verified that the ssid
>matches that in the WAP (I'm not using any WEP for now; not concerned due
>to an extremely rural location - it's too far even for drive-by access). 
>I get an amber activity light on the cisco, but no green status indicator.
>
>LANTRAN.LOG shows:
>
>FFST/2 is installed but is not started.  LANMSGDD is loaded and
>operational.
>
>Netstat shows the adapter, as does PC Card director [what a kludgy
>interface!]
>
>TCPIP config won't allow me to set it to DHCP (that may be because I had
>LAN0 set to use DHCP).
>
>What should I try next?
>
> 
>-- 
> Julian Thomas:   jt@jt-mj.net    http://jt-mj.net

The following frags from my vintage Toshiba Laptop using Warp 3 FP 40 on a Linksys 
WAP54G for TCPIP and NetBios using static addressing.

Config.sys for PCMCIA

REM FOR PCMCIA CARDS
BASEDEV=PCMCIA.SYS
BASEDEV=IBM2TOS1.SYS /S0=2 /E
REM USE FOR HARD DRIVES
BASEDEV=PCM2ATA.ADD /S:1 /B
REM FOR FAX/MODEM
DEVICE=C:\OS2\BOOT\AUTODRV2.SYS C:\OS2\AUTODRV2.INI
REM FOR WINOS/2
DEVICE=C:\OS2\MDOS\VPCMCIA.SYS

My Lantran.log for netbios for TCPIP and NetBios

LT00073: FFST/2 is installed but is not started.  LANTRAN.LOG is being created.
IBM OS/2 LANMSGDD [04/26/95] 2.01 is loaded and operational.
IBM OS/2 LAN Protocol Manager
IBM OS/2 NETBEUI 2.60.5
NETBEUI: Using a 32-bit data segment.
Installing NETWKSTA.200 Version 4.0. IBM LAN Redirector (Apr 17, 1995)

IBM OS/2 NETBIOS 4.0
Adapter 0 has 155 NCBs, 96 sessions, and 7 names available to NETBIOS 
applications.
NETBIOS 4.0 is loaded and operational.
IBM LANVDD is loaded and operational.
IBM OS/2 LAN Netbind
Adapter 0 is using node address 0004AC25A51E.  The Token-Ring format is 
002035A4A578.

Protocol.ini end frag

[PCMNICCS_nif]

   DriverName = PCM_CS$
   IOBASE = 0x300
   INTERRUPT = 11
   RAMADDRESS = 0x0
   PCMCIA

Setup.cmd

rem laptop01 - Toshiba Laptop
rem 192.168.1.10 Cisco AiroNet 340 wireless and
rem All devices on the same subnet.

route -fh
arp -f

ifconfig lo 127.0.0.1
ifconfig lan0 192.168.1.10 netmask 255.255.255.0 metric 1 mtu 1492

route add default 192.168.1.1 1

ipgate off


That is all I can think of at the moment, use these for clues on your setup and let us know 
how it's going.

David
David

David Butkovich
CM Consultants, Inc.
Ocoee, Florida  USA

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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)

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=