From: "Jon Harrison" <ecs-t6x@2rosenthals.com>
Received-SPF: none (secmgr-ny.randr: 216.162.174.5 is neither permitted nor denied by domain of seadog.reno.nv.us) client-ip=216.162.174.5; envelope-from=jharrison@seadog.reno.nv.us; helo=pop5.greatbasin.net;
Message-ID: <100-012a0a48-35112.028@seadog.reno.nv.us>
To: "eCS ThinkPad T60/61 Mailing List" <ecs-t6x@2rosenthals.com>
Date: Sat, 19 Apr 2008 10:21:05 -0700 (PDT)
Priority: Normal
User-Agent: PMMail/3.00 (os/2; U; Warp 4.5; en-US; i386; ver 3.00.00.0935)
In-Reply-To: <185323.09.15.08.19.04.2008@seadog.reno.nv.us>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [eCS T60/T61] lantran.log & wrapper error

On Sat, 19 Apr 2008 12:11:32 -0400, Lewis G Rosenthal wrote:

>You have TCPBEUI binding to both the wird and wireless interfaces, and 
>the wireless seems to bind with no issue? Have you tried testing with 
>*ONLY* TCP/IP to see if that makes a difference?

The problem turned out to be a combination of things.

First, I installed eCS w/o a wired connection attached.  So the
install did not pick up that nic.  I chose genmac driver and it
seems to work.  Is that the correct driver for the wired nic?

Once I set up MPTN for the wired connection I could not get peer
and had troubles with tcpip routing.

For tcpip I had to read the wLan monitor docs several times before
I finally understood it.  My LAN is DSL -> InJoy Firewall ->
computers, hubs, & wireless access point (acting as a hub).  This
complicated my wLan setup because it assumes the access point is
the router.

I had to disable wireless, redo the tcpip config (several times -
for example I messed up on the LAN interfaces), install netbios
protocol and edit ibmlan.ini.  Problems with wireless setup messing
with my dns and routing were due to my misunderstanding of the wLan
interface and not reading the doc's carefully enough.

One thing unresolved is ip addressing.  Most of my network is
static ip, the laptops are dhcp.  I couldn't figure this out w/
wLan and gave it a static ip for the time being.  Since I can have
multiple profiles I probably will leave it this way.

Thanks, Jon