After seeing numerous responses to this issue I think it is time to
step and look at what is key to having NETBIOS over TCP/IP operational.
1) NetBIOS over TCP/IP must be properly installed. Unfortunately this
is best done using a fresh install oe migration, as 'Selective Install
for Networking' sometimes leaves out key files. Though I believe eCS
1.2 is better at this than eCS 1.1 and earlier.
2) The MPTD MPTS setup should look like:
a) simplified view for TCP/IP and NetBIOS over TCP/IP or NetBIOS only:
Adapter0
- 0 - TCP/IP
- 0 - NetBIOS over TCP/IP
Adapter1
- 1 - TCP/IP <===
the numbering is key, it must be consistent!
- 1 - NetBIOS over TCP/IP
Adapter2
- 2 - TCP/IP
- 2 - NetBIOS over TCP/IP
b) It is more complicated when someone (unnecessarily) chooses to use
both NetBIOS and NetBIOS over TCP/IP:
Adapter0
- 0 - TCP/IP
- 0 - NetBIOS over TCP/IP
-1 - NetBIOS
Adapter1
- 1 - TCP/IP
- 2 - NetBIOS over TCP/IP
- 3 - NetBIOS
In fact, I would not recommend anyone trying to use both NetBIOS and
NetBIOS over TCP/IP with more that one adapter.
3) After exiting MPTS, ibmcom\protocol.ini needs to contain the
following (for 3 adapters using NetBIOS over TCP/IP);
4) MPTS, does not automatically configure ibmlan\ibmlan.ini, but in
eCS "System Setup | Network | Select Interfaces for Sharing' should.
The resulting ibmlan.ini should look like (again for NetBIOS over
TCP/IP with 3 adapters):
[requester]
...
wrkservices = peer[,messenger] (messenger is really not needed in
a soho use)
wrknets = NET1,NET2,NET3
COMPUTERNAME = name
DOMAIN = domain
[peer]
....
srvnets = NET1,NET2,NET3
5) mptn\bin\setup should look something like this for fixed ip
addresses:
route -fh
arp -f
ifconfig lo 127.0.0.1
ifconfig lan0 192.168.2.55 netmask 255.255.255.0 metric 0 mtu 1500
ifconfig lan1 192.168.1.55 netmask 255.255.255.0 metric 0 mtu 1500
ifconfig lan2 192.168.0.55 netmask 255.255.255.0 metric 0 mtu 1500
REM ifconfig lan3
REM ifconfig lan4
REM ifconfig lan5
REM ifconfig lan6
REM ifconfig lan7
REM ifconfig sl0
route add default 192.168.2.1 -hopcount 1
ipgate on
for dhcp on lan 0 the setup should look like:
ifconfig lo 127.0.0.1
dhcpstrt -i lan0 -d 0
ifconfig lan1 192.168.1.55 netmask 255.255.255.0 metric 0 mtu 1500
ifconfig lan2 192.168.0.55 netmask 255.255.255.0 metric 0 mtu 1500
REM ifconfig lan3
REM ifconfig lan4
REM ifconfig lan5
REM ifconfig lan6
REM ifconfig lan7
REM ifconfig sl0
ipgate on
The subnet IP address range for lan1 & lan2 could be real (i.e. the
subnet actually exists) or 'dummy'. So. once the network is up and
running, one should be able shutdown and reconfigure the various lans
to appropriate IPs. However, as versatile eCS is when it comes to
networking, it is still a client operating system and not meant to be
used as a network server or a complex router. However, if one is
careful, it will function quite well routing between a DSL connection
and a SOHO network using two nic adapters. Three or more adapters???
One really has to take a close look at why this configuration is really
needed!
Cheers,
Chris Clayton
On Wed, 30 Nov 2005 15:20:52 -0800, Bob wrote:
>** Reply to message from "Frank Vos frankvos@xs4all.nl" on Wed, 30 Nov 2005
>23:09:40 +0100 (CET)
>
>Here is LANTRAN.LOG. The first part is the boot process and then the last part
>is after issuing the "net use" command, which gives the message "The REQUESTER
>service could not be started". I do not see any errors although I don't know
>why there is reference to token-ring.
>
>
>
>LT00073: FFST/2 is installed but is not started. LANTRAN.LOG is being created.
>IBM OS/2 LANMSGDD [05/21/04] 6.00 is loaded and operational.
>IBM OS/2 NETBEUI 6.00.0
>NETBEUI: Using a 32-bit data segment.
>Installing NETWKSTA.200 Version 6.0. IBM LAN Redirector ( May 25, 2005)
>
>IBM OS/2 NETBIOS 4.0
>Adapter 0 has 123 NCBs, 96 sessions, and 6 names available to NETBIOS
>applications.
>Adapter 1 has 123 NCBs, 96 sessions, and 6 names available to NETBIOS
>applications.
>Adapter 2 has 123 NCBs, 96 sessions, and 6 names available to NETBIOS
>applications.
>NETBIOS 4.0 is loaded and operational.
>GENPRISM_NIF: APM registered.
>GENPRISM_NIF is loaded and operational.
>IBM LANVDD is loaded and operational.
>IBM OS/2 LAN Netbind
>WRND32$ WRAPPER for bus: 2 slot: 2 Vendor: 0x8086 Device: 0x1043.
>WRND32$ load SYS: "W70N51.SYS" length: 2479104 CRC: 0x6bb2 / 0x6bb2.
>WRND32$ load INF: "W70N51.INF" length: 2041.
>WRND32$ WRAPPER hardware init successfull MAC : 000CF1:28897E.
>WRND32$ bound to "VECTOR".
>GENPRISM_NIF: OpenAdapter called.
>
>issued "net use"
>
>Adapter 0 is using node address 000D608B5786. The Token-Ring format is
>00B006D1EA61.
>GENPRISM_NIF: SetLookAhead called. Param1=256
>GENPRISM_NIF: AddMulticastAddress called. Param2= 3 0 0 0 0 1
>GENPRISM_NIF: AddMulticastAddress rc=0
>GENPRISM_NIF: SetPacketFilter called. Param1=3
>GENPRISM_NIF: SetPacketFilter rc=0
>Adapter 1 is using node address FFFFFFFFFFFF. The Token-Ring format is
>FFFFFFFFFFFF.
>Adapter 2 is using node address 000CF128897E. The Token-Ring format is
>00308F14917E.
>
>--
>Robert Blair
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>To unsubscribe from this list, send a message to
>steward@2rosenthals.com with the command
>"unsubscribe os2-wireless_users" in the body
>(omit the quotes).
>
>For help with other commands, send a message
>to steward@2rosenthals.com with the command
>"help" in the body (omit the quotes).
>
>This list is hosted by Rosenthal & Rosenthal
>P.O. Box 281, Deer Park, NY 11729-0281. Non-
>electronic communications related to content
>contained in these messages should be directed
>to the above address. (CAN-SPAM Act of 2003)
>
>=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).
For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).
This list is hosted by Rosenthal & Rosenthal
P.O. Box 281, Deer Park, NY 11729-0281. Non-
electronic communications related to content
contained in these messages should be directed
to the above address. (CAN-SPAM Act of 2003)
volver a la lista