Supported Network Protocols

Right out of the box, Windows NT provides you with several choices of transport protocols to use with your network. Each of these choices has its good and bad aspects, which you should consider carefully before making a final decision as to which protocol to implement. Of course, if you are planning to integrate Windows NT into an existing network, your choices may already be made.

NetBEUI

The NetBEUI (NetBIOS Extended User Interface) protocol is the fastest protocol to use, but it has a few limitations. Specifically, it cannot be routed, although it can be bridged. It also floods the network with broadcast messages, which can eat up a considerable amount of network bandwidth. In addition, NetBEUI is a poor performer over WANS. Nevertheless, I always include this protocol when I install Windows NT Server. I install NetBEUI because it:

•  Provides the most efficient protocol for use within a local subnet.

•  Offers good error-recovery options.

•  Leaves a small memory footprint.

•  Is completely self-tuning.

•  Provides network connectivity with legacy platforms, such as Lan Manager or the Windows for Workgroups 3.11 Remote Access Software implementation.

•  Provides an alternate protocol if one of the other installed protocols fails.

IPX/SPX

If you have a Novell NetWare server, it’s a no-brainer decision. You will want to install the IPX/SPX protocol so that you can connect to your NetWare server. The IPX/SPX protocol is also quite useful for integrating the Microsoft SQL Server for Windows NT in a Novell environment. With IPX/SPX installed, your Novell clients can access SQL Server databases without major modifications. And, it is a much safer and faster solution than implementing an SQL Server NetWare Loadable Module (NLM), because, if an NLM running in ring zero for maximum performance fails, it can take down your entire server.

IPX/SPX is also a good choice for small-to-medium size networks because it is a routable protocol. This provides the ability to physically split network segments while maintaining a single logical network segment. On the downside, IPX/SPX also sends broadcast messages periodically, which can eat up network bandwidth. And while it is also a routable protocol, it is not the best choice for a wide area network (WAN).

---

TIP:  Another reason to use IPX/SPX is that many multiplayer games use IPX/SPX to support dynamic multiplayer interaction.

---

Microsoft has provided a software emulation of a NetWare server called File And Print Services For NetWare. This software provides the ability to let your current NetWare clients access a Windows NT Server without changing the client drivers. If this is used in conjunction with the Novell migration tools, you can just drop Windows NT Server in as a replacement for your Novell server.

TCP/IP

The Transmission Control Protocol/Internet Protocol is not a single protocol, but rather, a collocation of protocols, which includes TCP, UDP, ARP, and many others. It is the most widely utilized protocol. And while it is not the most efficient protocol to use for a LAN, it is the best protocol to use for a WAN. Some of the reasons I find TCP/IP so useful and recommend it heartily are:

•  Provides the best integration with existing Unix implementations. This includes the Windows NT clients, like Telnet, FTP, rsh, and rexec, as well as network printer connectivity to/from Unix printers.

---

The TCP/IP protocol is also required if you plan to access the Internet directly. TPC/IP is not required if you plan on using a proxy server (more on this later) to access the Internet. A proxy server can be configured to use TCP/IP between itself and the Internet but use IPX/SPX to pass the information between itself and its clients.

---

•  Provides easy integration and access to the Internet either via a dedicated connection or when used with the Remote Access Service and a supported modem.

•  Can be used to support the Windows NT Socket implementation for access to SQL Server databases.

•  Is fully routable.

•  Reduces administrative tasks due to the introduction of DHCP and WINS TCP/IP. DHCP and WINS completely automate the assignment of IP addresses and NetBIOS computer name resolution.

Data Link Control

The data link control protocol is primarily used to provide a connectivity solution for IBM mainframes on a token ring network. It is also used to communicate with network printers, such as the HP LaserJet IV with the Jet Direct network card installed, or an HP Print Server, such as the HP EX3 Plus.