Found this while trying to solve the same problem.
Easy networking with OS/2
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 print client 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"
Oh by the way I used this with an NT server and worstation machine as well. NT could see the files on the shared HPFS partition and OS2 could see the files on a shared NTFS partion, so the above statement about them not seeing each other over a network is crap. The redirect/requester takes for each OS care of translation.
Thanks for the person who wrote this.
