Yes, it's even easier than you thought! Networking OS/2 isn't black magic like many people think. It has the same features as NT, but just different names for things and different places to click. This step by step howto will show how to connect an IBM PS/2 server 95 (featured in the computer museum) running OS/2 version 4 FP14 with HPFS drives to an IBM aptiva running windows95a using FAT. Both computers run 10base-T ethernet NICs and use TCP/IP. NetBIOS isn't used anymore since it's not as good. These steps can be applied to any other machines besides what is used here. As the systems are running now, I can boot up OS/2, and it automatically mounts the shares on the Aptiva just fine and I can transfer files from the Aptiva over to the PS/2 for safekeeping on an 8mm tape drive. The steps shown are for OS/2 version 4. Warp connect and OS/2 Warp server will be similar. Later I will mention differences in those. I would like to have screen shots, but am too lazy to do this right now. This exercise assumes proficiency in both windows and OS/2.
Windows 95 and 98 requirements:
Install TCP/IP and specify an IP for the NIC, in this case, it is 192.168.1.53 with a subnet of 255.255.255.0. Think of a machine name and set the workgroup to TEST. Make sure file and print sharing are installed as well. That should do it. BTW, get rid of NETBEUI and IPX/SPX if you don't need them. To find out why, read about windows security isses at GRC.com
OS/2 requirements:
Starting from a new OS/2 install, choose the advanced option. During the OS/2 installation you will come to a point where you are prompted for what services to install. Choose the option that says, let me choose. Choose the option to install file and printclient and make sure that sharing is installed. Next step is to enter in a name for the workstation, i.e. the hostname. The next field is the workstation description so fill that in with whatever you want or leave the default choice. The next screen prompts for a domain name. I use test in this case. The following screen prompts for a userid and password for the file and print client. Type in something you can remember here. For this example I use user and user. Don't forget what it is, or else you'll have to copy over a default file and you will lose all your previous settings! There is an option to install the netware client. Choose no. Also choose no to install mobile office services. You have an option to install the system management client. I believe it may only work on another OS/2 machine. The next screen prompts whether you want to install TCPIP services. Choose to install TCPIP for both lan and modem support. You will be prompted whether you want to install DHCP or DDNS support. Choose neither. the next screen prompts you for tcpip names and ip addresses. fill in the TCPIP address and the subnet mask, then continue. Next, choose no to install remote access client. On the next screen, choose your NIC then continue. If you get prompted if hardware settings have changed, choose the appropriate option. For IBM PS/2 models, the answer is NO. Review the selections made, then continue. Wait for files to copy over.
When the computer reboots, watch for and make sure the NIC driver in the config.sys loads. If it does not, you will have to reconfigure it.. Once the desktop loads, open up the connections icon and then the network icon. Double click on the logons icon and then select start file and print client. This can be added to the startup folder if needed. Once completed, run the file and print client workstation logon icon. Logon to the machine here using the userid and password you chose when initially installing the network services. In this case, it's user and user. A message should say logon was successful. Sharing can now be setup. To do so, you can right click on the desktop to open the system menu to choose the options to either start sharing, or manage access of a share that's been setup. Back under the network-icon view window, open up the network services icon and run the shared resources and network connections icon. Within this settings notebook is where shares, connections and permissions as well as users can be setup. To share out C: drive for example, select the shares tab and then key in the drive and directory you want to share out and then click OK.. The following screen will allow you to set a description, number of connections and the ability to manage access of that share. Obviously, it will be wise to create shadows of all these icons used on the desktop. Within the network-icon view window, and then within the file and print client resource browser- icon view, your win95 machines that are previoulsy set up should be shown. To verify your tcpip settings, run TCPCFG from a command prompt. From there you can verify your IP addresses as well as other related tasks.
For initial OS/2 installation choosing the easy install:
On the type of activites screen, choose the options to access the internet and connect directly to a LAN. Then choose next. Install file and print client and install sharing. Type in a unique name for the workstation (hostname) enter in a workstation description if needed. Key in TEST for domain name. On a subsequent screen, enter a userid and password for the file and print client. for this example, USER and USER are used.
Do not install netware client. Do not select DHCP or DDNS. Key in IP address and subnet then click next. Select your NIC if it is not detected and continue. Review the selections to install when the screen comes up and then continue. Allow the installation to copy files over. Wait for the computer to reboot and start with the paragraph above.
The OS/2 machines used in this exercise run HPFS which windows is able to access with a problem. If you have lost the userid and/or password for the file and print client logon, there is an original NET.ACC file in the \IBMLAN\INSTALL directory. Replace the one in the \IBMLAN\ACCOUNTS folder. This will restore the default account settings, losing everything previously setup.
If you get an error in the config.sys when booting that references a filename called NETWKSTA.200 basically that means that there is a network setting that is wrong. Go back into your TCPIP configuration notebook and/or MPTS and doublecheck your settings.
Second exercise:
I've decided to include another configuration currently used to show how things work together. For this essay, 3 computers are used; a Compaq machine running windows me, a AMD 1200 running win2k server and an IBM PS/2 server 95 running OS/2 v4 FP14. All machines are running TCP/IP and are using ethernet NICs. The compaq is using an IP of 192.168.1.4 and file and print sharing are turned on and client for MS networks installed. The workgroup is TEST. The win2k machine has an IP of 192.168.1.120 and a preferred DNS server of 127.0.0.1. Client for MS networks and file and print sharing are also installed.The workgroup is TEST. The OS/2 machine has LAN interface 0 enabled using an IP of 192.168.1.67 using the program TCPCFG.EXE. Within the Adaptors and Protocol Services icon (MPTS.EXE) the NIC driver is installed with IBM TCP/IP installed and then IBM OS/2 NETBIOS OVER TCP/IP installed last. Both protocols have <1> listed beside them. At this point, I suggest dragging shadows (the original concept of windows' shortcuts) of TCP/IP CONFIGURATION (LAN), Adapters and Protocol Services, File and Print Client Resource browser and Shared Resources and Network Connection icons to the desktop to make them easier to access.
To get this all going, open up the Connections icon and then the logons icon. Execute the Start File and Print Client icon. You may want to place a shadow in the startup folder if you plan to connect all the time. Once complete, execute the File and Print Client Workstation Logon icon. As in the first exercise, the logon is USER and USER. Login will complete shortly.
Open the Shared Resources... icon and verify that the primary domain name is TEST to match Windows' workgroup name. Select Start Lan Services... if you wish that option to be enabled. Select either the Connections or Shares tab to setup the relevant options. This is where folders and drives are shared out for OS/2. For easy networking, none of the other tabs need any modification. Open up the File and Print Client... icon next. The two windows machines in this exercise have drives shared out and show within the resource browser window. In this case, the Compaq computer icon said unknown user. To originally identify it, I chose the icon's properties, choosing the network status tab. The server name listed corresponds to windows' Computer name. Be sure to place something relevant in the Description field of any Windows computer used, since OS/2 uses that info to name the icons in the resource browser. Opening up any of the listed computer icons will show the directories and/or drives that are shared out. Using the power of OS/2's object desktop, icons can be dragged to local folders.
Networking messaging actually works with Win2k, although it seems that win9x series cannot see the messages. After typing in the message, choose the option to broadcast to the selected domain, in this case, that being TEST. The message will show up on the originating OS/2 machine as well as on the win2k system.
Third exercise:
I won't go into details on this essay except to say that the computers in question are now using RoadRunner. The same Linksys router is still being used. An old Dell Optiplex has been set up with OS/2 version 4 FP15 and connects and runs Mozilla and Staroffice fine. Unfortunately, I'm having problems getting a Token Ring NIC working. Even with the fixpack CD installed, any changes made within MPTS don't always update the IBMLAN.INI file correctly and as a result, you'll get errors about the NETWKSTA file when starting up. In this case, I had to edit the NET1 and NET2 lines in the IBMLAN.INI file which corrected it. There's other OS/2 based websites that will detail that for now.
Important files to know
There's some files you will want to make backups of when experimenting around with networking.
C:\IBMCOM\LANTRAN.LOG This file is a log of things started up when networking. If you have trouble, view this file to get an idea of what is going wrong where
C:\IBMCOM\PROTOCOL.INI Obviously a configuration file of the protocols you have set up.
C:\IBMLAN\IBMLAN.INI Not sure how/where this is used, but it's one to watch for
C:\IBMLAN\NETPROG\NETWKSTA.200 This file is created when you setup all your networking stuff. If something's not right, this file will not load in your config.sys. This means you get to have lots of fun trying to fix it all.
C:\CONFIG.SYS I'm sure you know how and what this is for.
This completes this exercise on networking to Micros~1 products. An essay on connecting to <blech> winxp is forthcoming. Further essays may include using token ring, DSL and multiple NICs, all within OS/2.
Return to main page