Hi Dirk,
DB> Therefore I have installed as additional protocol the
DB> "NETBIOS over TCP/IP" on the Server (and TCP/IP before)
DB> and on the client the "NETBIOS over TCP/IP" protocol only.
I have it working fine here talking between a Warp Connect box and an NT
server using NETBIOS over TCP/IP, but it took some work......;-)
The end result was the discovery that Warp Connect Blue box fails to update
ALL the files correctly if you ADD NETBIOS over TCP/IP to an existing
configuration. If you install Warp Connect from scratch and configure it with
NETBIOS over TCP/IP at the start, then the install program gets it right.
Its quite involved to explain the complete story here, however depending on
how familiar you are with manaully configuring control files the folloing may
provide you with enough hints.
1. You MUST configure your adapater to support BOTH NETBIOS and NETBIOS
over TCP/IP using a second LEVEL of protocol on the SAME card as TCP/IP.
0 - IBM TCP/IP,
0 - IBM NETBIOS
1 - IBM NETBIOS over TCP/IP
This part is usually installed correctly by the config program.
2. You need to MANUALLY add the level 1 device to the \IBMLAN\PROTOCOL.INI
file as a SECOND network connection -
[networks]
net1 = NETBEUI$,0,...
net2 = TCPBEUI$,1,... (just copy these setting from the NET1 line.
And then update the sections -
[requestor]
... (other existing lines...)
worknets = NET1, NET2
[peer]
... (other existing lines)
srvnets = NET1, NET2
This is the part that is missing if you update your configuration
froma working NETBIOS only config.
After that you should be just about ready to fly... You also need to ensure
you define the TCP/IP addressing for the remote systems in MPTS configuration
for the NETBIOS over TCP/IP protocol entry to make sure you can see the
resources. There are literally HEAPS of settings available, but most things
do not need to be touched to get it working.
I hope that starts you in the right direction............pk.
--- Maximus/2 3.01
---------------
* Origin: Another Good Point About OS/2 (3:772/1.10)
|