>>>> Download the PDF version here ! <<<<
Connect vs Warp 4.0
3.1.1 Windows NT
3.1.1 Windows NT: WINS
3.1.2 Windows NT: Browsing
3.2 Banyan Vines
3.2.1 Banyan Vines: OS/2 DOS VDM Support
3.2.3 Banyan Vines: WinOS2 Support
3.3 Samba (Jacco de Leeuw's networking page, this link will take you away from this site.)
3.4 Peer in
4.0 What is it?
This article may be republished in its entirety or partially as long as Robert "RokNroB" Thomas is given credit somewhere in the republished material along with my email address of email@example.com
The issues range from Network Operating Systems and
network protocols to data file formats. These issues alone require herculean
efforts for the average user. Even to the experienced OS/2 Power user, these
problems can be difficult. Hopefully, this document will solve some of the
issues for an OS/2 user lost in a sea of Windows.
In the present OS/2 Warp architecture, IBM refers to this networking support as Multi-Protocol Transport Services. The support is provided by drivers called requester's. The requester's are specified in the config.sys file and loaded at boot. Network communication is provided to and from the requester's and protocol's using NDIS (Network Driver Interface Specification). OS/2 Warp version 4 and OS/2 Warp Connect ship with these requesters: IBM LAN, 3270 Emulation, Netware, IBM TCP/IP. These requester's also have their associated protocol drivers as described previously (TCP/IP, 802.2, etc.). Banyan supports networking in native OS/2 as well as DOS VDM's and WinOS2.
The installation of MPTS will install a copy of the online book "Network Adapters and Protocol Service Guide". This book is located in the Assistance Folder inside the Information folder under Tasks. This book traverse's OS/2 Warp networking in detail.
OS/2 Warp Connect has separate requester's for LAN
Server and Peer. Warp Connect will only allow either the LAN Server requester
or the Peer requester to be installed. This is because they both share the
same file name and directory structure.
OS/2 Warp 4 combines the LAN Server requester and the Peer requester into one requester. Warp 4 also shipped with DHCP, whereas Warp Connect had this software added via a fixpack. Warp 4 TCP/IP stack is newer than Warp Connect's. However, fixpacks will bring Warp Connect's TCP/IP stack to par with Warp 4.As a final note, some users claim that Connect's Peer client is superior to Warp 4's. However, I have seen no evidence or documentation to support these claims.
This passage will help you set up the OS/2 Warp client to be compatible with Windows. Microsoft has changed little tidbits of LAN Manager operating characteristics with the release of NT 4.0 and Win95. Some of the default settings shipped with these products can and will cause confusion and frustration for the OS/2 user.
You will need to install IBM Peer for OS/2 to interoperate with a Microsoft Network. The OS/2 Warp client is very easy to setup to interoperate with a Microsoft Network if you know the tricks involved. OS/2 Warp 4 will install the "File and Print Client Guide" when Peer is installed which incorporates a brief section on interoperability with Microsoft Networks. Literature is spread throughout IBM, some docs at PSP, some at Raleigh, some here and there on the net.
The three protocols generally needed to interoperate with Microsoft Network's are TCP/IP, NetBios, and NetBios over TCP/IP. The NetBios protocol is used locally on a subnet because it contains no routing information. This also means that NetBios cannot see past a router without help. NetBios over TCP/IP can see past a router and this protocol is generally used at corporate sites where large segmented networks are the norm as shown in figure 1.
3.1 Windows NT
Microsoft has strayed once again from networking standards in their proprietary implementation of domain registration. What does this hack on networking standards mean to an OS/2 user? It means that OS/2 Warp clients cannot logon to NT domains through a router. This also will cause problems for products from other vendors as well. Microsoft has a long way to go before they are an Enterprise NOS.
Despite Microsoft efforts to keep Warp off an NT server, an OS/2 Warp client can take advantage of Microsoft Network in one of two ways. The Warp client can logon to the NT domain or logon locally. However, browsing is severely limited on a Microsoft Network if the servers have been configured with the default settings (more on this in a later section). Either method will achieve the desired results, to use the resources on a Windows NT server domain. One precaution, your local OS/2 Warp logon must exactly match the logon ID on the NT domain controller. In addition, NT server allows lower case in passwords whereas Warp does not.
In a segmented network architecture where the OS/2 Warp client is separated from the NT server via a router, NT domain authentication is impossible with the default configuration of the Warp client. IBM has described this issue in Technical Document #7775533. IBM Technical Document #3724433 describes some useful NT administrator tips. In order for the Warp client to be authenticated by the NT domain controller the IP address will have to be added to the RFCBCST.LST file. Other NT resources would be added to the RFCNAMES.LST file. These files may be updated using MPTS or a text editor may be used. After the RFC files have been modified, the RFCADDR command can be run from an OS/2 window which will update the system and prevent the client from having to be restarted.
3.1.1 Windows NT: WINS
WINS (Windows Internet Name Service) is a proprietary implementation of a Domain Name Server and a NetBios Name Server (NBNS). This hack gives the appearance that WINS is a Dynamic Domain Name Server. However, since WINS in not really a DDNS, other network operating systems that are compliant with a DDNS will not operate properly. The other function of WINS is to provide NetBios computer name registration. Combined with the DHCP server option which passes out IP addresses, WINS will update the database with pointers to the DNS (this is the hack).
OS/2 Warp clients can take advantage of the NT WINS
NetBios Name Server. Your administrator or another peer can give you the IP
address of the primary and backup WINS servers. If you are you using DHCP you
can request these IP addresses and view them from the DHCP Monitor program. If
the Warp client is separated from the WINS server via a router, the NetBios
over TCP/IP protocol is a must. Also the node type should be set to "H-NODE"
when operating in a segmented network. Due to the implementation of DHCP in
OS/2 Warp you will have to manually edit the protocol.ini and add the
WINS IP addresses into the TCPBEUI section as follows:
The following are some useful DHCP options provided by the Microsoft DHCP server. These are the only options supported by Windows based DHCP clients (lease options 51,58 and 59 not included in Table 1).
|1||Subnet Mask||Defines the subnet mask for the client.|
|3||Router||Defines the default router IP address (gateway).|
|6||DNS Servers||Defines the IP addresses of the domain name servers.|
|15||Domain Name||Defines the domain name for the client.|
|44||WINS/NBNS||Defines the IP address of the NetBios Name Servers.|
|46||WINS/NBT||Node type: 1 = B node, 2 = P node, 4 = M node, 8= H node|
|47||NetBios scope ID||Defines a text string for NetBios over TCP/IP scope ID.|
Banyan Vines support is installed using a Banyan provided install program called VCLIENT. Vclient will also modify your config.sys heavily. Do not run VCLIENT until you have installed your network adapter using MPTS and other networking protocols.
If you are using OS/2 Warp 4.0 you will need a fixpack from Banyan. This fixpack consists of two files, VINES2-5.IFS and VINES2-6.IFS. Depending on what version of Banyan Vines server that your network is running will determine what file to use. VINES2-5 is for Vines version 5.x and VINES2-6 if for Vines version 6.x. You will need to install one of these files before rebooting OS/2 after installation of Vines. Your machine will trap on every boot until you install the needed file into the Vines subdirectory.
The following is a real handy feature to get access to
files for different OS's from the Banyan server. You can map your server (Z:\)
drive in DOS, OS/2 or Win95/NT by using the setdrive command. By
mapping the server drive to root will provide a hint to what OS's the server
is setup to provide client connectivity with. Use the following procedure to
C:\VINES\BANSVC.COMThis program provides the Vines interface from a DOS VDM and WinOS2 to OS/2.
Leeuw has created a fantastic web page containing
information on how to setup and get connected using
Installation is easy and painless. Start Win-OS/2, open Win-OS/2 Setup from the Main Window, select Options, then select Change system settings, select IBM Peer for OS/2, then select OK. Win-OS/2 Setup will prompt for the Windows diskettes it needs (Insert your OS/2 Warp CD into the CD drive and point the location to \OS2IMAGE\DISK_W1, etc). The above mentioned files will need to handy also (NETAPI.DLL, PMSPL.DLL).
this is pretty cool (IBM has some great Software Engineer's), I've noticed a
performance hit in my Win-OS/2 sessions with IBM Peer for OS/2 enabled in
Win-OS/2. This is due to the setup program modifying the system.ini with some
new parameters, PSP and timer variables. I removed these from the [386enh]
section without any problems and my performance was on par
Exchange is a Microsoft application that runs on a Windows server. Exchange provides e-mail and other services such as being able to setup meetings electronically. In order to use the Exchange service you must have the Exchange client installed or another client application that is compliant with the Exchange protocols.
TIP2: Choose the Aerial font for the
Exchange client. MS Outlook defaults to this font and others will not know any
difference. The default font in Exchange WIN16 is MS San Serif . This font
does not display well for some reason in MS Outlook under Win95 and
This document was created and published with StarOffice 4.0 International Beta 1
Number of hits: 38402