🚀 go-pugleaf

Hi Brian,
    thanks for your reply, but I think you may have misread my post.

> Tim,
> There are a couple of errors in this.
> 1) the setup you have will only work because you have tcpbeui on 0,
> if you want to make it go to 1 on a second nic card there is a problem.

True, that was what I describing in the post - the fact that TCPBEUI must be
bound as logical adapter 0 to TCP/IP adapter lan0.

> 2) tcpbeui completly ignores the first comma.

It was NETBEUI that was bound as logical adapter 1, with the leading comma
to cause this.

Thanks all the same.

> see INFO-TASKS-Network adapters and protocol guide.
>
> Brian
>
> > From recent experience on playing with TCPBEUI:
> >
> > 1) Only *one* LAN or SLIP/PPP adapter may be bound to TCPBEUI
> >
> > 2) The adapter to which you wish to bind TCPBEUI must be the *first*
> > configured:-
> >
> > [NETBIOS]
> >     Adapter0 = tcpbeui,0
> >
> > [TCPBEUI_nif]
> >     DriverName = TCPBEUI$
> >     Bindings = adapter0_nif
> >
> > [adapter0_nif]
> >     DriverName = ????????$
> >
> > 3) TCP/IP must be bound to it! (Otherwise, where's the transport!!!)
> >
> > [TCPIP_nif]
> >     DriverName = TCPIP$
> >     Bindings = adapter0_nif
> >
> > 4) If you *also* wish to bind NETBEUI to the *same* adapter you must use
a
> > higher logical adapter no.
> >
> > [NETBEUI_nif]
> >     DriverName = NETBEUI$
> >     Bindings = ,adapter0_nif    <=== NOTE: leading comma defines *no*
> > adapter "0" (has been used by TCPBEUI). This is adapter "1".
> >
> > 4) then you can set up OS/2 Peer to use these logical adapters
> >
> > [networks]
> >
> >     NET1 = TCPBEUI,0,...
> >     NET2 = NETBEUI,1,...