Protocols come in many different flavors and performdifferent functions on the
network. Some, such as NetBEUI, lack elements that allow their signals to travel
through routers, making them non-routable (essentially, this protocol is unsuitable
for a large network that uses routers to re-transmit data). The network
protocols supported by Windows include NetBEUI, NWLink (IPX/SPX), and
TCP/IP, although Windows XP drops support for NetBEUI.
NetBEUI
NetBEUI is easy to configure, since no network addresses are needed. Generally,
all you need to establish a connection between computer systems using NetBEUI
is a NetBIOS computer name. NetBIOS names must be unique and contain 15
or fewer characters, but other than that there isn’t much to it.
NWLink (IPX/SPX)
As mentioned, NWLink isMicrosoft’s implementation of the IPX/SPX protocol.
TheMicrosoft version of NWLink provides the same level of functionality as the
Novell protocol and also includes an element for resolving NetBIOS names.
NWLink packages data to be compatible with client/server services on NetWare
networks, but it does not provide access to NetWare File and Print Services. For
this, you also need to install the Client Service for NetWare, as noted earlier.
Follow the same steps used to install NetBEUI to install NWLink, except
choose NWLink rather than NetBEUI when you make your final selection.
You’ll be prompted to reboot after adding the protocol.
NWLink is a relatively easy protocol to configure.Normally, the only settings
youmay need to specify are the internal network number and frame type (usually,
however, the default values are sufficient). The internal network number
is used by the network for routing purposes. The frame type specifies
how the data is packaged for transport over the network. For computers to
communicate by NWLink, theymust have the same frame types. By default, the
frame type is set to Auto Detect, which is usually fine.