[Q]: Configuring NetBios over TCP/IP with Warp Connect
[A]: Sergey Afonin (2:5057/29.13)
H���p���� ��p�py⨧�樨 NetBIOS over TCP/IP
(�p���������� �p����쭮 ����p����y� ��p�py⨧��� TCP/IP)
����:
-- 192.168.1.1/24 NetBIOS name: win1; Host name: host1.domain.ru (W95)
|
|
A -- 192.168.1.2/24 NetBIOS name: os1; Host name: host2.domain.ru (OS/2)
|
|
-- 192.168.1.254/24 NetBIOS name: osrout; Host name: rout.domain.ru (OS/2)
-- 192.168.2.254/24 ��p�� �⥢�� ���p䥩� osrout
|
|
B -- 192.168.2.1/24 NetBIOS name: win2; Host name: host3.domain.ru (W95)
|
|
-- 192.168.2.2/24 NetBIOS name: os2; Host name: host4.domain.ru (OS/2)
��� ⮣�, �⮡� y������ � ��設 win2 � os2 p��yp�� ��設 win1 � os1
����室��� �믮����� �����y�騥 ����⢨�.
��� win2:
ᮧ���� � ��⠫��� \windows 䠩� lmhosts
----lmhosts begin-----
192.168.1.1 win1
192.168.1.2 os1
-----lmhosts end------
�� �⮣� �y�y� ����y��� ������� ���� net view \\os1
��� os2:
1) �p�����p���p����� ���祭�� �y��� ����� � protocol.ini:
--------
[tcpbeui_nif]
NODETYPE = "B-Node"
NAMESFILE = 50
--------
���⢥��⢥��� ��p����p� Node Type � Maximum number of name-ip address pairs
in names file � ���� ���䨣yp�樨 NetBIOS over TCP/IP -> Driver parameters
� MPTS. ������ - 䠪��᪨ ���ᨬ��쭮� � ��⮢ � �py��� IP-����,
� ���p묨 ����� ᮥ�������� �� tcpbeui;
�� ��ᠥ��� "B-Node", �, ��������, �y��� p������ � "H-Node", �� � ��
�p������.
2) ᮧ���� 䠩� \IBMCOM\RFCBCST.LST � ᯨ� ip ��p�ᮢ ��� ���� ��⮢,
� ���p묨 �p��y���� y�⠭����� ᮥ�������. H����p� ��p�����:
- ---RFCBCST.LST begin---
192.168.1.1
host2.domain.ru
----RFCBCST.LST end----
���
- ---RFCBCST.LST begin---
host1
host2
----RFCBCST.LST end----
������ �� y������, ����y ����� ��騩 �� ��� ��.
NetBIOS over TCP/IP -> Broadcast list � MPTS.
3) ᮧ���� 䠩� \IBMCOM\RFCNAMES.LST, � ���p�� �������� ᮮ⢥��⢨� IP-
��p�ᮢ � NetBIOS-����:
----RFCNAMES.LST begin----
"win1" 192.168.1.1
"os1" 192.168.1.2
-----RFCNAMES.LST end-----
NetBIOS over TCP/IP -> Names list � MPTS.
�� �⮣� �y�y� ����y��� ������� ���� net view \\os1
�p���砭�� 1:
H� Win95-������� � ����p����� TCP/IP ������ ���� ����祭 NetBIOS � ������
����� �p��離� � ������y Microsoft
�p���砭�� 2:
��� y�p�饭�� ���䨣yp�p������ �⠭権 ���������� 䠩�� (RFCBCST.LST,
RFCNAMES.LST) ��� OS/2 � ���������� 䠩�� (lmhosts) ��� Windows ���
ᥣ���⮢ "A" � "B" ����� ��ꥤ�����.
�p���砭�� 3:
����� ��� y�p�饭�� p�������y� ����� ��⮢ p�������y� �������� � ����
nbname.domain.ru. H��p���p:
NetBIOS Name : name1
Host name: name1.domain.ru
�p���砭�� 4:
� �ᯮ�짮����� p��ypᮢ �������p� osrout �� TCPBEUI �� �����py����,
� ����稥 NetBIOS over TCP/IP ⠬ ᮢ�p襭�� �� ��易⥫쭮. �
�ᯮ�짮����� �����py����, � �����筮 ��� y�⠭���� ���� �� ���� ��
�⥢�� ���p䥩ᮢ. �p�祬 �� ��� �� ���p䥩� ����� ���� y�⠭����� �
�p��� NetBIOS, �� � �py��� �����᪨� ����p��.
[A]: (
courtney@timken.com)
Assuming you've got IBM Peer working using NETBIOS over NETBEUI, here are
the steps I follow when adding support for NETBIOS over TCP/IP:
1. Install TCP/IP if you don't already have it on the system. You can use
the "Warp Connect Install/Remove" function in the OS/2 System folder
to accomplish this.
2. From an OS/2 command line, or from the Workplace Shell, use MPTS.EXE
to add the NETBIOS over IP protocol.
a. From MPTS's first screen, select "Configure" (not Install!)
b. Choose "LAN Adapters and Protocols" on the next screen, then go to
the "Configure" button.
c. In the lower-left listbox, select your desired network adapter. It
should already be installed and the hardware settings configured. Do
not add a new adapter from the upper-left corner.
d. With the adapter highlighted, select "NETBIOS over TCP/IP" in the
upper-right listbox and click on "Add" nearby. You should see this
protocol added to the lower-left listbox.
e. Single-click on the new protocol in the lower-left listbox and click
"change number". You can't have two NETBIOS protocols be the
same logical adapter number. If all the existing numbers are "0" you
can make the new protocol "1". Note: It doesn't matter what the
number is for TCP/IP itself...this setting only applies to NETBIOS
type functions.
f. In the same listbox, click "Edit". You'll see a dialog box with
three radio buttons. Set things up as shown below:
f1. Driver Parameters
You'll see a LONG list of text entries. Near the bottom is one
that says "Maximum number of name-IP address pairs..." and
defaults to zero. Change it to a reasonable number, such as
30. This limits how many NETBIOS over IP devices you can
connect to that are reached through an IP router. E-mail me if
you want a detailed explanation of this.
f2. Names List
Use this dialog to map the NETBIOS computername to an IP
address. Only necessary for nodes that are NOT on your own
IP subnet. The entry in step "f1" above is the max number
of items in this list, and the results of this step wind up in
a file called RFCNAMES.LST.
f3. Broadcast List
Add an entry of each IP broadcast address you want to use.
For example, I connect to nodes in subnet 147.185.104.xxx,
so my Broadcast List has 147.185.104.255.
Save and exit this screen.
g. Back at the LAPS Configuration dialog where you added the
new protocol, click OK to save and exit. You'll return to the
"Configure" dialog. There is an option called "TCP/IP Socket
Access" that says "Must configure". Fortunately, all that is
required to accomplish this is to click on the "Configure" button!
h. Click "Close" to save and exit this dialog. Then exit from MPTS
and let it make the changes it wishes to your CONFIG.SYS and
PROTOCOL.INI files.
i. MPTS will tell you to shut down and reboot. NOT NEEDED YET!
2. Use OS/2 Peer install routine to "tell" Peer about the second logical
adapter.
a. In the OS/2 Peer folder, choose the install program and run it.
b. You'll get a warning message that multiple adapters were detected
but that you have to use MPTS to configure them. No problem---
you just finished that step.
c. Proceed through the OS/2 Peer installation...at each step, just tell
it "OK" without changing anything. Make sure both of your logical
adapters are enabled. ***CAUTION*** When it asks you if you
want to reset "NET.ACC", tell it NO!!! Otherwise you will reset
your local admin password, user accounts, access lists, etc. Yech!
(However, if you ever forget your password, this is how to reset to
the defaults without reinstalling...)
d. Save and exit. Again, the install program will want to modify
CONFIG.SYS and IBMLAN.INI...let it.
3. Shut down and reboot.
With this configuration, OS/2 Peer will first try to reach the other node on your NETBEUI network, and will use TCPBEUI only if that times out. This
has the side effect of making initial connections (only) to TCP/IP nodes a little slower, but once you have connected the speed is normal.
I have successfully used this configuration to communicate amongst the following node types, within and across subnets on a WAN:
OS/2 Peer (on Warp Connect)
Windows NT 3.5
DEC Pathworks 1.3g running on ULTRIX 4.3a
DEC Pathworks 5.0 running on Open/VMS
If you need further help, you are welcome to e-mail me as "
courtney@timken.com".
[A]: Andrey Kvasha (
sysop@is.nsk.su)
�����p���� ���� !
�⢥�� �� � �� ���쬮 �⮡� �py��� �� �p���� �� ����y���� :)
���饬 �� ��y夭������ ���y����� �� ����᪨� ����� y������ ���론�� �y�饥 :
_________________________
�p����p NetBIOS API �ᯮ��y�� ��� p����饭�� p��ypᮢ ���p�p뢭y� ������� ������ ��ꥬ�� � 64 �����. �⮡� p������� p��yp�� ��� NetBIOS API, ���� �����, �� ����y���� �p����py NetBIOS API ���p�⨢��� ������ �� �����
��室��� �� �p����� 64 �����. �y��� �y��� ����稭 �� ������ �p������
64 �����:
- 95 ���� �� ����� ���� NCB, ����y��� ��� NetBIOS API
- 15*(�� ������ NCB, ����y���� ��� NetBIOS API - 15)
(� �� � ����� 0, �ᯮ��y�� 0)
- 990 �� ����� �����p, �䨣yp�p������ ��� NetBIOS
- 11200 ���� �������⥫쭮
�p���p� �ᯮ�짮����� ���p�⨢��� ����� NetBIOS API �p������� �
�p���筨�� LAN Technical Reference.
� �� ��諨 �� �p����� 64 ��������, � �� �p��� ��砫쭮� ���py��� �y��� �뤠�� �y�饥 ᮮ�饭�� �� �訡��:
LT00065: ��p����p� ���䨣yp�樨, ������� � 䠩�� PROTOCOL.INI, ��室�� �� �p����� 64 �����. �����p��� NetBIOS 4.0 �p��p�饭�. __________________________________
����� ����y���p � y� :)
y����蠥� � NCB ������ � protocol.ini ( y ���� �� p���⠬ �� �p�
�⥢y� 155 )
[tcpbeui_nif]
NCBS = 225
--- INN 2.7.3 (rc1 version)
* Origin: This echo is READ-ONLY. Send %HELP to FAQSERVER at (2:5020/181)