Hi Eric,
 EB> Does anyone have any experience with the following combination:
 EB> OS/2 &
I have Warp Connect at Fixpack 21 currently in use
 EB>  a notebook & 
on an IBM Thinkpad 755CE
 EB> TCP/IP on a ethernet LAN
with 802.2, TCP/IP, NETBIOS and NETBIOS over TCP/IP (used to have IPX as well 
but thats now removed) protocols,
 EB> and pcmcia ehternet card especially XirCom pcmcia card.
I am using a 3COM 3C589 PCMCIA card and UTP cabling. I am aware of the Xircom 
card, but know nothing about them.
 EB> Dialup tcp/p works  ( wouldn't be here if it did not)
 EB> but I cxannot get it to connect via a LAN anda router to a leased line.
I connect my laptop to a local LAN which links via routers to other LANS and 
everything works fine, but I dont use PPP Dialup from the notebook. I have 
other OS/2 machines on local LAN segments that also have PPP running for 
inbound calls, and that required some tweaking to get the routing right, but 
it is certainly possible. The catch comes when trying to alternate the Serial 
port between PPP Dial-in and PPP Dial Out! That makes life quite interesting, 
but it certainly is possible in most cases if you think abut it.
So in your case, you can use outbound PPP connections from the notebook ok, 
but not LAN IP connections? Are you attempting to do concurrent LAN AND PPP 
connections, or are you trying to alternate between the 2 types? If the 
former, then depending on exactly what you are trying to reach and where it 
is located, you may only have to enable ROUTING under OS/2 to solve a routing 
problem. If the later, then you may need to change the routing when you 
switch to the other connection type (depending on the routing setup). This 
may require quite a bit more detail from you to understand exactly what you 
are trying to do, and the addressing involved.
Can you PING any other local LAN systems (EG, the router) when connected to 
the LAN? If you can't, then it really does sound like the routing is not 
correct.
 EB> The lan works (trumpet windsock tested it) but via os/2 , no luck
I take it that is native Windows Trumpet and nothing to do with Win-OS/2? If 
the LAN works ok from a Native Windows environment, but not a Win-OS/2 
environment, then it may be the OS/2 configuration (or a driver) problem for 
the PCMCIA card that is the cause.
Is the Warp install from Red Pack or Blue Pack? I am aware of people having 
odd problems with Red Pack installs, but I only use Blue Pack and they have 
all been fine. I think the trick with Red Pack is to get everything working 
under Windows only, THEN install OS/2 and dont let Windows Installs touch the 
Windows environment again, but thats only my guess.
 EB> Anyone with pcmcia experience please let me know.
If you can PING OK from OS/2 sessions and then Win-OS/2 sessions, then there 
is probably not much wrong with the PCMCIA H/W.
I hope this helps.........pk.
--- Maximus/2 3.01
---------------