🚀 go-pugleaf

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