Windows 98 network protocols are implemented as 32-bit, protected-mode virtual device drivers (VxDs) that offer high performance. Windows 98 can support multiple protocols simultaneously, and protocol stacks can be shared among the installed network clients. For example, the Internet Packet Exchange/Sequenced Packet Exchange (IPX/SPX) – compatible protocol can support both Client for NetWare Networks and Client for Microsoft Networks. The following protocols are included with Windows 98:
All four protocols are Plug and Play – compliant, so they can be loaded and unloaded automatically. For example, if a PC Card network adapter is removed from the computer so that the network is no longer available, the protocols are unloaded automatically after any dependent applications have been notified.
Windows 98 can support multiple network protocols and can share a protocol among the network providers that are installed. You might choose more than one protocol to ensure communication compatibility with all systems in the enterprise. However, choosing multiple protocols can cause more network traffic, more memory used on the local computers, and more network delays.
The following sections briefly describe the benefits of using each protocol and issues to consider when using each protocol.
This is a complete implementation of the standard, routable Transmission Control Protocol/Internet Protocol (TCP/IP) protocol. Windows 98 includes only protected-mode support for this protocol. Microsoft TCP/IP provides the following benefits:
Consider the following issues when using this protocol:
This protocol is compatible with the Novell NetWare Internetwork Packet Exchange/Sequential Packet Exchange (IPX/SPX) implementation. Windows 98 includes both 32-bit, protected-mode and real-mode support for this protocol. This protected-mode protocol provides the following benefits:
Consider the following issues when using this protocol:
This protocol is compatible with existing networks that use the NetBIOS extended user interface (NetBEUI), including Windows for Workgroups peer networks, Windows NT Server, LAN Manager, and other networks, and includes support for the NetBIOS programming interface. Windows 98 provides both protected-mode and real-mode support for this protocol.
NetBEUI was first introduced by IBM in 1985, when it was assumed that LANs would be segmented into workgroups of 20 to 200 computers and that gateways would be used to connect one LAN segment to other LAN segments or to a mainframe. NetBEUI is optimized for high performance when used in departmental LANs or LAN segments. Microsoft NetBEUI under Windows 98 is completely self-tuning.
One common method for setting up a network is to use NetBEUI plus a protocol such as TCP/IP on each computer that needs to access computers across a router. If you set NetBEUI as the default protocol, Windows 98 uses NetBEUI for communication within the LAN segment and uses TCP/IP for communication across routers to other parts of the WAN.
Consider the following issues when choosing this protocol:
The 32-bit DLC protocol provides connection and communication with mainframe computers using DLC. With the 32-bit Data Link Control (DLC) protocol, you can establish multiple connections to different IBM host and AS/400 computers over the same network token-ring, FDDI, or Ethernet adapter. Host terminal emulation programs use the 32-bit DLC to communicate directly with host computers. The 32-bit DLC protocol also allows multiple 32-bit applications to use the same network adapter at the same time to connect to different host computers. You can also use the 32-bit DLC protocol to provide connectivity to local area printers connected directly to the network.
The 16-bit DLC protocol is also available; however, in most cases, it is recommended that you use the 32-bit DLC protocol.