Lesson 2: NWLink

This lesson discusses the NWLink IPX/SPX/NetBIOS-compatible transport protocol (usually referred to as NWLink), Microsoft's implementation of Novell's NetWare Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX) protocol. NWLink is most commonly used in environments where clients running Microsoft operating systems are used to access resources on NetWare servers, or where clients running NetWare are used to access resources on computers running Microsoft operating systems.

After this lesson, you will be able to

Install and configure NWLink.

Estimated lesson time: 30 minutes

Understanding NWLink Features

NWLink allows computers running Windows 2000 to communicate with other network devices that are using IPX/SPX. You can also use NWLink in small network environments that use only clients running Windows 2000 and other Microsoft operating systems.

NWLink supports the networking APIs that provide the interprocess communications (IPC) services described in Table 7.7.

Table 7.7 Networking APIs Supported by NWLink

NWLink also provides NetWare clients with access to applications designed
for Windows 2000 Server, such as Microsoft SQL Server and Microsoft SNA Server. To provide NetWare client access to file and print resources on a computer running Windows 2000 Server, you should install File and Print Services for NetWare (FPNW).

In summary, the 32-bit Windows 2000 implementation of NWLink provides the following features:

Supports communications with NetWare networks

Supports sockets and NetBIOS over IPX

Provides NetWare clients with access to Windows 2000 servers

Installing NWLink

The procedure for installing NWLink is the same process that you use to install any network protocol in Windows 2000:

Right-click My Network Places, and then click Properties.

In the Network And Dial-Up Connections window, right-click Local Area Connection, and then click Properties.

The Local Area Connection Properties dialog box appears, displaying the network adapter in use and the network components configured for this adapter.

Click Install.

In the Select Network Component Type dialog box, click Protocol, and then click Add.

In the Select Network Protocol dialog box, in the Network Protocol list, click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol (see Figure 7.7), and then click OK.

Figure 7.7 The Select Network Protocol dialog box

Configuring NWLink

NWLink configuration involves three components: frame type, network number, and internal network number. By default, Windows 2000 detects a frame type and a network number automatically when you install NWLink. Windows 2000 also provides a generic internal network number. However, you must manually specify an internal network number if you plan to run FPNW or IPX routing, as shown in Figure 7.8.

NOTEEach network adapter card bound to NWLink in a computer requires a frame type and network number.

Figure 7.8 Configuring NWLink

Frame Type

A frame type defines the way that the network adapter card formats data. To
ensure proper communication between a computer running Windows 2000 and
a NetWare server, you must configure the NWLink frame type to match the frame type on the NetWare server.

NOTEA connection between two computers that use different frame types is possible if the NetWare server is acting as a router. However, this is inefficient and could result in a slow connection.

Table 7.8 lists the topologies and frame types supported by NWLink.

Table 7.8 Topologies and Frame Types Supported by NWLink

NOTEOn Ethernet networks, the standard frame type for NetWare 2.2 and NetWare 3.11 is 802.3. For NetWare 3.12 and later, the default is 802.2.

When you install NWLink, Windows 2000 automatically determines which IPX frame type is in use on the network and sets the NWLink frame type accordingly. If Windows 2000 detects frame types in addition to 802.2 during NWLink installation, the frame type for NWLink defaults to 802.2.

Network Number

Each frame type configured on a network adapter card requires a network number, which must be unique for each network segment. All computers on a segment using the same frame type must use the same network number to communicate with one another.

NOTEOn a computer running Windows 2000, type ipxroute config at a command prompt to display the network number, frame type, and device in use.

Although Windows 2000 automatically detects a network number during NWLink installation by default, you can also manually specify a network number by using Registry Editor.

Setting a network number in the registry for a given frame type requires entering two corresponding entries, NetworkNumber and PktType, in this subkey of the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Nwlnkipx\Parameters\Adapters\Adapter.

NetworkNumber specifies the network number (in hexadecimal) for the adapter. If the value for this entry is 0, NWLink gets the network number from the network while it is running. Network numbers are 4 bytes (eight hexadecimal characters). The NetworkNumber entry takes the data type REG_MULTI_SZ.

PktType specifies the packet form to use. The PktType entry takes a data type REG_MULTI_SZ. Table 7.9 lists the values for the PktType entry and the packet forms supported by NWLink.

Table 7.9 Packet Types or Forms Supported by NWLink

NOTEIf an adapter uses multiple packet types, you can specify the network number for each packet type by adding corresponding values in the NetworkNumber entry.

Internal Network Number

An internal network number uniquely identifies a computer on the network for internal routing. This eight-digit hexadecimal number, or virtual network number, is set to 00000000 by default.

The internal network number identifies a virtual network segment inside the computer. That is, the internal network number identifies another (virtual) segment on the network. So, if an internal network number is configured for a computer running Windows 2000, a NetWare server or a router adds an extra hop in its route to the computer.

You must manually assign a unique, nonzero internal network number in the
following situations:

FPNW is installed, and there are multiple frame types on a single adapter.

FPNW is installed, and NWLink is bound to multiple adapters in the computer.

An application is using the NetWare Service Advertising Protocol (SAP). SQL Server and SNA Server are examples of applications that can use SAP.

NOTEIf a computer has multiple network adapter cards bound to NWLink, and if you want each one to use a different frame type, configure each network adapter card to use the Manual Frame Type Detection option. You must also specify a frame type, network number, and internal network number for each network adapter card.

Practice: Installing and Configuring NWLink

In this practice, you will install and configure the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol.

NOTEYou can install any of the available protocols in Windows 2000 by using this procedure.

To install and configure NWLink

Restore the Network And Dial-Up Connections window.

Right-click Local Area Connection, and then click Properties.

The Local Area Connection Properties dialog box appears, displaying the network adapter card in use and the network components used in this connection.

Click Install.

The Select Network Component Type dialog box appears.

Click Protocol, and then click Add.

The Select Network Protocol dialog box appears.

What protocols can you install?

Answer

Select NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, and then click OK.

Notice that the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol is listed in the Components list in the Local Area Connection Properties dialog box that appears.

Select NWLink IPX/SPX/NetBIOS Compatible Transport Protocol, and then click Properties.

Which type of frame detection is selected by default?

Answer

Click OK to close the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol Properties dialog box.

Click OK to close the Local Area Connection Properties dialog box.

Lesson Summary

In this lesson, you learned that NWLink is Microsoft's implementation of Novell's NetWare IPX/SPX protocol. NWLink is most commonly used in environments where clients running Microsoft operating systems are used to access resources on NetWare servers, or where clients running NetWare are used to
access resources on computers running Microsoft operating systems. NWLink supports Winsock and NetBIOS over IPX networking APIs. Winsock supports existing NetWare applications written to comply with the NetWare IPX/SPX Sockets. NetBIOS over IPX is implemented as NWLink NetBIOS and supports communication between a NetWare client running NetBIOS and a computer running Windows 2000 and NWLink NetBIOS.