🚀 go-pugleaf

>   The setup is that in Protocol.ini are:
> Adapter 0 and Adapter 1 are bound to an ethernet NIC.  TCPIP & Netbeui
> are bound to Adapter 0 and TCPBeui is bound to Adapter 1. I also have
> Adapter 2 bound to IBM's virtual NULL MAC (NulNDIS.os2) but excluding
> this make no difference to the VDM problem.
>
>   In IBMLan.ini the following allows VDMs to work OK but if ,NET2 is
> added after NET1 in [Peer], as soon as you invoke any VDM, just a
> command line for instance, OS/2 hangs.  Fortunately CAD will restart
> the computer so you don't get chkdsk having to run with its lengthy
> processing every time this happens.

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,...

You *really* would be best advised to use the Install/Configure object of
OS/2 Peer to *correctly* configure your bindings and protocols, until you
understand thoroughly the interrelationship between the values in each
configuration file. You will also need to look at the NETBIOS Names
configuration information, which results in entries in the files
\IBMCOM\RFCNAMES.LST and RFCBCST.LST, amongst others.

HTTH

Tim

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.
2) tcpbeui completly ignores the first comma.

see INFO-TASKS-Network adapters and protocol guide.

Brian



Tim Clarke wrote:
> 
> >   The setup is that in Protocol.ini are:
> > Adapter 0 and Adapter 1 are bound to an ethernet NIC.  TCPIP & Netbeui
> > are bound to Adapter 0 and TCPBeui is bound to Adapter 1. I also have
> > Adapter 2 bound to IBM's virtual NULL MAC (NulNDIS.os2) but excluding
> > this make no difference to the VDM problem.
> >
> >   In IBMLan.ini the following allows VDMs to work OK but if ,NET2 is
> > added after NET1 in [Peer], as soon as you invoke any VDM, just a
> > command line for instance, OS/2 hangs.  Fortunately CAD will restart
> > the computer so you don't get chkdsk having to run with its lengthy
> > processing every time this happens.
> 
> 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,...
> 
> You *really* would be best advised to use the Install/Configure object of
> OS/2 Peer to *correctly* configure your bindings and protocols, until you
> understand thoroughly the interrelationship between the values in each
> configuration file. You will also need to look at the NETBIOS Names
> configuration information, which results in entries in the files
> \IBMCOM\RFCNAMES.LST and RFCBCST.LST, amongst others.
> 
> HTTH
> 
> Tim

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,...

Tim,
True, misreading posts can become an occupational hazard.
I just wanted to point out that according to the manual TCPBEUI will
bind
to the first adapter it finds active. I have a setup where I want
TCPBEUI to
bind to the 2nd adapter(lan1). I have some ideas on how to achieve this
but would
appreciate any input,
Thanks,
Brian  

Tim Clarke wrote:
> 
> 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,...

Hi Brian...

> Tim,
> True, misreading posts can become an occupational hazard.
> I just wanted to point out that according to the manual TCPBEUI will
> bind to the first adapter it finds active.

This is the main cause of (current) confusion and problems. AFAIK, TCPBEUI
will *only* bind to the first LANn (in TCP/IP terms) adapter that is
running. Everything else can be re-numbered to get what other protocol
stacks bound to the same or other *physical* adapters.

> I have a setup where I want TCPBEUI to bind to the 2nd adapter(lan1).

Not possible, unless you change/re-order the *logical* numbering of the
adapters via MPTS. It must end up as TCP/IP logical adapter LAN0, for
TCPBEUI to correctly bind to the desired physical adapter.

Starting from scratch:

1) Add physical adapter and configure.
2) Add TCP/IP protocol to adapter (logical number is automatically 0).
3) Add TCPBEUI (Netbios over TCP/IP) protocol to adapter (binds to lan0,
which is necessary) and configure.
4) Optionally, add NETBIOS protocol to adapter and *re-number* to logical
adapter 1!!! (MPTS will moan, if you don't) and configure.

Save and Test.

5) Optionally, add other physical adapter(s) and configure
6) Add protocol (except TCPBEUI) stacks to other adapter(s), ensuring no
duplicate logical adapter number for NETBIOS protocol (i.e. only 2 and 3
available after point 4 above).

Save and Test.

> I have some ideas on to achieve this but would appreciate any input,

HTTH

Tim

Tim,
> 
> > I have a setup where I want TCPBEUI to bind to the 2nd adapter(lan1).
> 
> Not possible, unless you change/re-order the *logical* numbering of the
> adapters via MPTS. It must end up as TCP/IP logical adapter LAN0, for
> TCPBEUI to correctly bind to the desired physical adapter.

I agree, I did exactly that, and configured the adapter that I wanted
TCPBEUI on on LAN0 and switched the second adapter to LAN1.

SNIP

I was just wondering if there was any way to select which adapter
becomes
"active" first?
Brian

> Tim,
> >
> > > I have a setup where I want TCPBEUI to bind to the 2nd adapter(lan1).
> >
> > Not possible, unless you change/re-order the *logical* numbering of the
> > adapters via MPTS. It must end up as TCP/IP logical adapter LAN0, for
> > TCPBEUI to correctly bind to the desired physical adapter.
>
> I agree, I did exactly that, and configured the adapter that I wanted
> TCPBEUI on on LAN0 and switched the second adapter to LAN1.
>
> SNIP
>
> I was just wondering if there was any way to select which adapter
> becomes
> "active" first?

Physically? The one whose section comes first in PROTOCOL.INI.

HTTH

Tim