🚀 go-pugleaf

In  <1992Sep2.180243.17767@cis.ohio-state.edu>
reed-d@python.cis.ohio-state.edu (David Reed) writes:
>
> I have been trying to get IBM's TCP/IP and Microsoft's LAN Manager
> (using TCP/IP as the protocol) to work simultaneously - here's
> the problem:
>
> Depending on where in the config.sys file I put the command
> device=d:\ibmcom\ifndis.sys, only one of the products works
> completely.  If I put it between the protocol manager and
> network card driver devices, IBM's TCP/IP works, but I get
> the error, SYS0053: The network path was not found, when
> I try to do a "net use" (LAN Manager).  If I put ifndis.sys above
> the LAN Manager section, net use works, but then IBM's TCP/IP
> cannot access the network.  In either case, every loads without
> any errors.
>
> Sidenote: using netbeui for LAN Manager's protocol allows
> everything to work, but unfortunately all the servers (except
> the one test server that was setup for me) do not have
> netbeui loaded.
>
> Does anyone know what exactly ifndis.sys does?  And even better,
> how to fix my problem?

ifndis.sys is responsible for interfacing TCP/IP stack to NDIS
MAC drivers (and PROTMAN).
MS LAN Mgr version 2.1 (?) has its own TCP/IP stack. You can't
have two TCP/IP stacks to be bound to the same adapter.
As you said it yourself, if LAN Manager uses netbeui stack
(instead of TCP/IP) everything works.

Oleg Vishnepolsky