🚀 go-pugleaf

It seems you may have and error in the [networks]. Here is what I have:
[networks]

  net1 = NETBEUI$,0,LM10,34,100,14
  net2 = tcpbeui$,1,LM10,34,100,14

Note the numbering, netbeui is '0' and tcpbeui is '1'
Your requester info is correct, but you also need an entry in the [peer] as well:
  srvnets = NET1,NET2

Hope this helps...

 Bruce



In <9500vb$ocv$1@merki.connect.com.au>, vbien@smartchat.net@smartchat.net writes:
>  I have got OS/2 to access Linux Samba following the instructions in
>Redhat Linux 6.2
>/usr/doc/samba-2.0.6/docs/textdocs/OS2-CLIENT-HOWTO.txt and the web
>page it points to.  The critical lines to add in IBMLAN.ini are:
>
>        net2 = TCPBEUI$,2,LM10,100,150,14
>in the [networks] section and
>       wrknets = NET1,NET2
>in the [requester] section
>
>  The existing line in IBMLAN.ini remained as:
>        net1 = NETBEUI$,1,LM10,100,150,14
>
>  However, I have an existing setup where I would like to be able to 
>use OS/2 as the server and Linux as the client.  The Linux command:
>
>    smbclient -L os2machine
>always gives an error message:
>Session request to os2machine failed (code 0)
>
>Similarly nmblookup -B os2machine '*'
>gives the message:
>name_query failed to find name *
>
>  The same commands to access a Win95 machine works fine.
>
>  Does anyone here know how to solve this problem?
>
>Victor Bien
>VCB Computing Alternatives (R)
>http://sydney.dialix.com.au/~vcbien/
>

In <c1.2c.2Z6bvx$017@transit.homeip.net>, bruce@os2box.omen.com.au writes:
>It seems you may have and error in the [networks]. Here is what I have:
>[networks]
>
>  net1 = NETBEUI$,0,LM10,34,100,14
>  net2 = tcpbeui$,1,LM10,34,100,14
>
>Note the numbering, netbeui is '0' and tcpbeui is '1'
>Your requester info is correct, but you also need an entry in the [peer] as well:
>  srvnets = NET1,NET2

  I didn't say that my "adapter 0" is a dialup adapter for a ppp 
telephone dial-in for a NFS linkup sometimes.  That was done on the 
advice of Bill Kredenster who posts in comp.os.os2.networking.tcpip 
some time back.  Net1 on 1 is therefore where the LAN netbeui was 
placed.  Therefore Net2 tcpbeui had to be placed on 2.

  I am somewhat confused in that before Xmas when I last had a go at 
this, placing srvnets = NET1,NET2 in peer stopped peer working at all. 
This time I have put in this line but have added an assignment to
SRVSERVICES in peer to = PEER (rather than the default blank) I don't 
know that whether this upsets correct workings.

  Can I take it that you can get Linux to client onto OS/2?  If so 
then I can be confident it's only a matter of detail to get the whole 
lot to work.

TIA

Victor Bien
VCB Computing Alternatives (R)
http://sydney.dialix.com.au/~vcbien/

On Mon, 29 Jan 2001 06:47:59, brian <bnc@altavista.net> wrote:

> In the Information folder under tasks there should be a
> 
> Network Adapters and Protocol Services Guide.
> 
> In this guide there is a section titled;
> 
> How TCPBeui Chooses a Network Interface.

Thanks for pointing me to this.  I haven't found that exact section yet,
but I'm having fun reading about B-node, H-node, M-node and P-node 
operation.

I have made some progress already.

-- 
Regards,
Al S.