** Reply to message from "Lewis G Rosenthal"
<virtualized_ecs_users@2rosenthals.com> on Mon, 14 Sep 2009 00:39:07 -0400
> Hmmm... Well, none of the above will work without the TAP driver, as
> that's what's doing the bridging.
>
> My TAP driver is:
>
> 1-07-08 6:21p 104,557 0 ---- prot.os2
> > I also have the NetBIOS loaded to get the peer network working between two
> > eCS computers. NetBIOS over TCPIP is loaded by default during install.
Lewis,
Before I ask more questions I want to thank you and Ed for all your time and
effort to help me get this problem solved. It is much appreciated!
That is the same one I have except mine says 5:21pm.
Before I try installing it again let me clarify the process. I had installed
it via MPTS as instructed in the readme which was basically copying the nif
and os2 files to \IBMLAN\MAC and then installing the driver via MPTS
including attaching the TCPIP protocol. That way it looks like another
network card which would give the routing function.
Your way of installing the driver manually in Config.sys, adding info to
Protocol.ini sounds like the end result would be the same as using MPTS other
than the fact that IBMLAN.INI isn't updated. Maybe it isn't necessary in this
instance, but I know that if they get out of sync there are serious problems.
Is there a problem with using the MPTS method? It seems like a safer method,
but maybe that is why it isn't working here.
spä? do zoznamu