🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.os.os2.bugs
Article #40

Re: TCPBeui on Net2 causes VDMs to hangup OS/2

#40
From: brian
Date: Fri, 09 Feb 2001 12:42
74 lines
3535 bytes
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,...
Technical Details
Message-ID: <3A83E5D0.D19C225B@altavista.net>
Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!sn-xit-04!supernews.com!216.227.56.88.MISMATCH!telocity-west!TELOCITY!enews.sgi.com!harbinger.cc.monash.edu.au!newsfeed.ozemail.com.au!ozemail.com.au!not-for-mail
References: <95n9vo$clh$1@merki.connect.com.au> <95nesq$35c$1@sshuraaa-i-1.production.compuserve.com> <3A8273D6.2FA6E922@altavista.net> <95vkrk$asj$1@sshuraac-i-1.production.compuserve.com>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10a752,4e6036128c148d8d
X-Google-Attributes: gid10a752,public
X-Google-Thread: 10c4f5,4e6036128c148d8d
X-Google-Attributes: gid10c4f5,public
X-Google-ArrivalTime: 2001-02-09 04:44:32 PST
Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!sn-xit-04!supernews.com!216.227.56.88.MISMATCH!telocity-west!TELOCITY!enews.sgi.com!harbinger.cc.monash.edu.au!newsfeed.ozemail.com.au!ozemail.com.au!not-for-mail
Message-ID: <3A83E5D0.D19C225B@altavista.net>
From: brian <bnc@altavista.net>
X-Mailer: Mozilla 4.61 [en] (OS/2; U)
X-Accept-Language: en
MIME-Version: 1.0
Newsgroups: comp.os.os2.bugs,aus.computers.os2
Subject: Re: TCPBeui on Net2 causes VDMs to hangup OS/2
References: <95n9vo$clh$1@merki.connect.com.au> <95nesq$35c$1@sshuraaa-i-1.production.compuserve.com> <3A8273D6.2FA6E922@altavista.net> <95vkrk$asj$1@sshuraac-i-1.production.compuserve.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Original-NNTP-Posting-Host: dial-tint120.webone.com.au
Organization: Web One Internet http://webone.com.au
Lines: 74
NNTP-Posting-Host: iridium0.webone.com.au
X-Trace: ozemail.com.au 981722616 203.102.39.2 (Fri, 09 Feb 2001 23:43:36 EST)
NNTP-Posting-Date: Fri, 09 Feb 2001 23:43:36 EST
Distribution: world
Date: Fri, 09 Feb 2001 23:42:56 +1100