Architecture for Client for NetWare Network
If you are installing Windows 95 to run on a NetWare network, Microsoft recommends that you use the Microsoft Client for NetWare Networks, which provides a 32-bit, protected-mode redirector. Client for NetWare Networks can be installed to coexist with Client for Microsoft Networks or a 16-bit network client, or it can be used as the sole network support for Windows 95. For technical information about these optional configurations, see Chapter 32, "Windows 95 Network Architecture."
Using Client for NetWare Networks provides the following benefits.
A high-performance system using no conventional memory.
Client for NetWare Networks uses only 32-bit protocols, drivers, and supporting files. This client is designed to be used in a multitasking environment and provides the robust performance available for all protected-mode components in Windows 95, using no conventional memory space. On large block transfers over the network, Client for NetWare Networks is up to 200 percent faster than Windows 3.x with the VLM client. For most network operations that are a mix of reading and writing, Client for NetWare Networks is 50 to 200 percent faster, depending upon the mix of I/O operations.
Protected-mode peer resource sharing services.
This includes the ability to share resources such as a CD-ROM drive as a network resource. To use Microsoft File and Printer Sharing for NetWare Networks, the computer must be running Client for NetWare Networks. For more information, see Chapter 11, "Logon, Browsing, and Resource Sharing."
Interoperation and logon with NetWare 2.15, 3.x, and 4.x servers.
This includes support for running NetWare login scripts. Client for NetWare Networks can access servers running NetWare 2.15 and above, NetWare 3.x servers (which are bindery-based), and NetWare 4.x servers using bindery emulation. Windows 95 provides a script processor for running login scripts.
Support for packet-burst protocol for faster data transfer.
Client for NetWare Networks with peer resource sharing supports burst-mode NCPs, a sliding window implementation. This feature can also be disabled, as described in Chapter 11, "Logon, Browsing, and Resource Sharing."
Automatic reconnection for lost server connection
When servers are available again after the loss of a NetWare Core Protocol (NCP) connection, Windows 95 reconnects automatically and rebuilds the user's environment, including connection status, drive mappings, and printer connections. (Novell-supplied AUTO.VLM only reconnects servers.) This also means that the client is not affected if the server is down or the network cable is not working.
Large Internetwork Packet (LIP) protocol support.
LIP works to increase the speed of data transmission when communication occurs over a router. Previously, if a server identified a router between itself and the client, the packet size was set to 576 bytes (including 64 bytes of header information). Using LIP, the client and server can negotiate the packet size used when communication occurs through a router. With LIP, the packets can be set to a maximum of 4202 bytes, based on the maximum physical packet size of the server. LIP is enabled between computers running Client for NetWare Networks and NetWare 3.12 – 4.x servers or any computer running Microsoft File and Printer Sharing for NetWare Networks.
Support for all documented MS-DOS and NetWare APIs defined by Novell.
This includes support for all NetWare 3.x APIs defined in Novell NetWare Client SDK. NetWare-aware applications that use only these documented APIs are compatible with Client for NetWare Networks. For more information, see "Client for NetWare Networks Technical Notes" later in this chapter.
Enhanced performance and new networking features.
These features, which are made available when using protected-mode networking components, are described in detail elsewhere in the Windows 95 Resource Kit: