1.1 What This Configuration is For

1.2 Benefits and Limitations

Two of the benefits of running Warp Server on Warp 4 were already mentioned above. They are:

• It has the same Workplace Shell as on the OS/2 Warp 4 clients.

• It has reduced testing requirements for clients and servers both running the same operating systems.

Furthermore, there are some technical enhancements in Warp 4 that can be utilized by the server. For example, there is a new Version of MPTS and an improved TCP/IP stack. The OS/2 Warp 4 TCP/IP stack gives some improvements that might be interesting for a server. One is the possibility of using aliases, which means you can put multiple IP addresses on a single adapter. This might be useful when one Internet Connection Server or FTP server has to take over another one for maintenance reasons. In addition, having TCP/IP clients that use the TCP protocol rather then UDP socksified is a real benefit. With a socksified telnet or ftp client, you can build a connection transparently through a firewall, provided that the firewall is running a socksd daemon and you have your socks configuration set up correctly on the client.

There are, however, some limitations. Warp Server SMP, an operating system that has been specially designed for servers. It is able to work with more than one processor simultaneously. This is not possible in the configuration described in this document because it uses the Warp 4 kernel, which is a single-processor kernel.

Other features are not supported because they have not been tested by the IBM lab. They are:

• Local Security

• PSF/2 (Advanced Print Services)

It is possible that these or other untested components may work in a Warp 4 / Warp Server environment. However, they are not supported by IBM and are therefore not documented here.

Note
Before you start planning and installing, see Appendix A. Known Problems.

1.3 Performance