[Previous] [Next]
Network bindings enable communication between network adapter card drivers, protocols, and services. Figure 7.10 shows an example of network bindings. In Figure 7.10, the workstation service is bound to each of three protocols, and each protocol is bound to at least one network adapter card. This lesson describes the function of bindings in a network and the process for configuring them.
The Windows 2000 network architecture uses a series of interdependent layers. The bottom layer of the network architecture ends at the network adapter card, which places information on the cable, allowing information to flow between computers.
After this lesson, you will be able to
- Explain how to configure network bindings.
Estimated lesson time: 20 minutes
Figure 7.10 Network bindings
Binding Between Architectural Levels
Binding is the process of linking network components on different levels to enable communication between those components. A network component can be bound to one or more network components above or below it. The services that each component provides can be shared by all other components that are bound to it. For example, in Figure 7.10, TCP/IP is bound to both the Workstation service and the Server service.
Many combinations of network bindings are possible. In the example shown in Figure 7.10, all three protocols are bound to the Workstation service, but only the routable protocols, NWLink and TCP/IP, are bound to the Server service. It is possible to select which protocols are bound to the network adapter cards. Network adapter card (0) is bound to all three protocols, while network adapter card (1) is bound only to the routable protocols. To control which components are bound together, you must be a member of the Administrators group.
When adding network software, Windows 2000 automatically binds all dependent network components accordingly. Network Driver Interface Specification (NDIS) 5 provides the capability to bind multiple protocols to multiple network adapter card drivers.
You can configure your network bindings by using My Network Places.
You can configure network bindings by following these steps:
NOTE
Only an experienced network administrator who is familiar with the requirements of the network software should attempt to change binding settings.
You can also specify binding order to optimize network performance. For example, a computer running Windows 2000 Workstation has NetBEUI, NWLink IPX/SPX, and TCP/IP installed. However, most of the servers to which this computer connects are running only TCP/IP. Verify that the Workstation binding to TCP/IP is listed before the Workstation bindings for the other protocols. In this way, when a user attempts to make a connection to a server, the Workstation service first attempts to use TCP/IP to establish the connection.
You can follow these steps to specify binding order:
Practice: Working with Network Bindings
In this practice, you will change the binding order of the protocols bound to your network adapter card. Next you will unbind a protocol from your network adapter card and then bind a protocol to your network adapter card. Finally you will uninstall a network protocol.
After completing this practice, you will be able to
In this exercise, you will change the binding order of the protocols bound to your network adapter card.
The Advanced Settings dialog box appears.
What is the order of the protocols listed under Client For Microsoft Networks in the Bindings For Local Area Connection list?
Notice that the order of the protocols listed under Client For Microsoft Networks has changed. NWLink IPX/SPX/NetBIOS Compatible Transport Protocol should now be listed below Internet Protocol (TCP/IP). If it's not, click the downward-pointing arrow again to move it below Internet Protocol (TCP/IP).
In this exercise, you will unbind TCP/IP from your network adapter card, which will leave NWLink as the only protocol available to access other computers.
TCP/IP is now unbound from your network adapter card.
In this exercise, you will uninstall the NWLink IPX/SPX/NetBIOS Compatible Transport Protocol.
The Local Area Connection Properties dialog box appears, displaying the adapter in use and the network components configured for this connection.
The Uninstall NWLink IPX/SPX/NetBIOS Compatible Transport Protocol dialog box appears.
Notice that NWLink IPX/SPX/NetBIOS Compatible Transport Protocol is no longer listed as an installed protocol.
In this exercise, TCP/IP is the only protocol installed, so you will bind TCP/IP to your network adapter card.
The Advanced Settings dialog box appears.
TCP/IP is now bound to your network adapter card.
In this lesson, you learned that binding is the process of linking network components on different levels to enable communication between them. A network component can be bound to one or more network components above or below it, which allows the services that each component provides to be shared by all other components that are bound to it. When you install network software, Windows 2000 automatically binds all dependent network components accordingly. NDIS 5 provides the capability to bind multiple protocols to multiple network adapter card drivers, and you can optimize network performance by specifying the binding order.