Chapter 7, Installing and Configuring Network Protocols

Chapter 7, Installing and Configuring Network Protocols

Chapter 7, Lesson 1

TCP/IP

|1| 1. Understanding the TCP/IP Protocols Suite

A. Industry-standard suite of protocols that enable enterprise networking and connectivity

|2| B. Advantages to a Windows 2000 configuration

1. A routable networking protocol supported by most operating systems

2. A technology for connecting dissimilar systems

3. A robust, scaleable, cross-platform client/server framework

Note TCP/IP supports the Microsoft Windows Sockets (Winsock) interface, which is ideal for developing client/server applications for Winsock-compliant stacks. Winsock is an application programming interface (API) that is the standard interface between socket-based applications and TCP/IP.

4. A method of gaining access to Internet resources

|3| C. The TCP/IP suite maps to a four-layer conceptual model.

1. Network interface layer puts frames on the wire and pulls frames off the wire.

2. Internet layer protocols encapsulate packets into Internet datagrams and run all the necessary routing algorithms.

a. Internet Protocol (IP) provides connectionless packet delivery for all other protocols in the suite. IP does not guarantee packet arrival or correct packet sequence.

b. Address Resolution Protocol (ARP) provides IP address mapping to the media access control (MAC) sublayer address to acquire the physical MAC control address of the destination.

c. Internet Control Message Protocol (ICMP) provides special communication between hosts, allowing them to share status and error information.

d. Internet Group Management Protocol (IGMP) provides multicasting, which is a limited form of broadcasting, to communicate and manage information between all member devices in a multicast group.

3. Transport layer protocols provide communication sessions between computers. The desired method of data delivery determines the transport protocol.

a. Transmission Control Protocol (TCP) provides connection-oriented, reliable communications for applications that typically transfer large amounts of data at one time or that require an acknowledgement for data received.

b. User Datagram Protocol (UDP) provides connectionless communications and doesn’t guarantee that packets will be delivered. Applications that use UDP typically transfer small amounts of data at one time. Reliable delivery is the responsibility of the application.

4. Application layer provides applications access to the network.

a. Many standard TCP/IP utilities and services reside in the application layer, including FTP, Telnet, SNMP, and DNS.

a. Winsock serves as the standard interface between socket-based applications and TCP/IP protocols.

c. NetBIOS over TCP/IP (NetBT) serves as the standard interface for NetBIOS services, including name, datagram, and session services. It also provides a standard interface between NetBIOS-based applications and TCP/IP protocols.

|4| 2. Configuring TCP/IP to Use a Static IP Address

A. By default, client computers running Microsoft Windows 2000, Windows 98, or Windows 95 obtain TCP/IP configuration information automatically from the DHCP (Dynamic Host Configuration Protocol) Service.

B. Even in a DHCP-enabled environment some computers should be assigned a static IP address, for example the computer running the DHCP Service.

|5| C. Options used in configuring a static TCP/IP address

1. IP address

a. A logical 32-bit address that identifies a TCP/IP host

b. Required by each network adapter card in a computer running TCP/IP

c. Must be unique on the network

d. Two parts: a network ID identifying all hosts on the same physical network and a host ID that identifies a host on the network

2. Subnet mask

a. A subnet is a network in a multiple-network environment that uses IP addresses derived from a single network ID.

b. Subnets are connected with routers.

c. A subnet mask blocks out part of the IP address so that TCP/IP can distinguish the network ID from the host ID.

d. The subnet mask determines whether the destination host is on a local or remote network.

e. To communicate on a network, computers must have the same subnet mask.

3. Default gateways

a. The intermediate devices on a network that store network IDs of other networks in the enterprise or Internet

b. Allows communication between hosts on different networks

c. If no route is configured, TCP/IP sends packets for remote networks to the default gateway, which forwards the packets to other gateways until the packet is delivered to a gateway connected to the specified destination.

|6| 3. Configuring TCP/IP to Obtain an IP Address Automatically

A. A server running the DHCP Service on the network can automatically assign TCP/IP configuration to DHCP clients.

B. Automatic IP addressing simplifies administration and ensures correct configuration information.

|7| 4. Using Automatic Private IP Addressing

A. An extension of dynamic IP address assignment for LAN adapters

B. Enables configuration of IP addresses without using static IP address assignment or installing the DHCP Service

C. The network LAN adapter for TCP/IP must be configured to Obtain An IP Address Automatically.

|8| D. Steps in Automatic Private IP Addressing

1. Windows 2000 TCP/IP attempts to find a DHCP server on the attached network.

2. In the absence of a DHCP server during startup, the client cannot obtain an IP address.

3. Automatic Private IP Addressing generates an IP address in the form of 169.254.x.y and a subnet mask of 255.255.0.0.

Note The Internet Assigned Numbers Authority (IANA) has reserved 169.254.0.0 through 169.254.255.255 for Automatic Private IP Addressing.

4. Computers enabled with Automatic Private IP Addressing can communicate only with computers on the same subnet that also have addresses of the form 169.254.x.y.

Note Windows 98 also supports Automatic Private IP Addressing.

|9| E. Disabling Automatic Private IP Addressing

1. Enabled by default

2. Add the IPAutoconfigurationEnabled value to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\Adapter subkey.

3. Set the IPAutoconfigurationEnabled to 0.

|10| 5. Using TCP/IP Utilities

A. Utilities for troubleshooting TCP/IP

1. Ping verifies configurations and tests connections.

2. ARP displays locally resolved IP addresses as physical addresses.

3. Ipconfig displays the current TCP/IP configuration.

4. Nbtstat displays statistics and connections using NetBIOS over TCP/IP.

5. Netstat displays TCP/IP protocol statistics and connections.

6. Route displays or modifies the local routing table.

7. Hostname returns the local computer’s host name for authentication by RCP, RSH, and REXEC utilities.

8. Tracert checks the route to a remote system.

9. All troubleshooting utilities are executed from within Command Prompt.

10. For information on most troubleshooting utilities in Command Prompt, type the utility followed by /? and then press Enter.

Note Hostname will return the name of the local computer. For information on how to use Tracert, open the Command Prompt, type Tracert, and press Enter.

B. Testing TCP/IP connectivity

1. FTP provides bidirectional file transfer between a computer running Windows 2000 and any TCP/IP host running FTP.

Note Windows 2000 Server ships with the ability to serve as an FTP client or server.

2. TFTP (Trivial File Transfer Protocol) provides bidirectional file transfer between a computer running Windows 2000 and a TCP/IP host running TFTP.

3. Telnet provides terminal emulation to a TCP/IP host running Telnet.

Note Windows 2000 Server ships with the ability to serve as a Telnet client.

4. Remote Copy Protocol (RCP) copies files between a client and a host that supports RCP; for example, a computer running Windows 2000 and a UNIX host.

5. Remote Shell (RSH) runs commands on a UNIX host.

6. Remote Execution (REXEC) runs a process on a remote computer.

7. Finger retrieves system information from a remote computer that supports TCP/IP and the finger utility.

6. Testing a TCP/IP Configuration

|11| A. Using ipconfig

1. Use ipconfig /all to verify the TCP/IP configuration parameters on a host.

2. Ipconfig /all | more prevents the ipconfig output from scrolling off the screen.

3. Understanding Ipconfig /all

|12| a. If a configuration has initialized, the ipconfig utility displays the IP address and subnet mask, and, if it is assigned, the default gateway.

|13| b. If a duplicate IP address exists, the ipconfig utility indicates that the IP address is configured; however, the subnet mask is 0.0.0.0.

|14| c. If the computer is unable to obtain an IP address from a server running the DHCP Service on the network, the ipconfig utility displays the IP address as the address provided by Automatic Private IP Addressing, in the range of 169.254.0.0 through 169.254.255.255.

|15| B. Using ping

1. Use ping to test connectivity.

2. Use ping to determine a TCP/IP host is available and functional.

|16| C. Using ipconfig and ping

1. Use ipconfig to verify that the TCP/IP configuration has been initialized.

2. Use ping with the loopback address (127.0.0.1) to verify that TCP/IP is correctly installed and bound to your network adapter cards.

3. Use ping with the IP address of the computer to verify that your computer is not a duplicate of another IP address on the network.

4. Use ping with the IP address of the default gateway to verify that the default gateway is operational and that your computer can communicate with the local network.

5. Use ping with the IP address of a remote host to verify that the computer can communicate through a router.

Note Typically, if you ping the remote host (step 5) and the ping command is successful, steps 1 through 4 are successful by default. If the ping command isn’t successful, ping the IP address of another remote host before completing the entire diagnostic process because the current host might be turned off.

7. Practice: Installing and Configuring TCP/IP

Chapter 7, Lesson 2

NWLink

|17| 1. Introduction to NWLink

A. Stands for NWLink IPX/SPX/NetBIOS-compatible transport protocol

B. Microsoft’s implementation of Novell’s NetWare Internetwork Packet Exchange/Sequenced Packed Exchange (IPX/SPX) protocol

C. Commonly used

1. Where clients running Microsoft operating systems are used to access resources on NetWare servers

2. Where clients running NetWare are used to access resources on computers running Microsoft operating systems

|18| 2. Understanding NWLink Features

A. Allows computers running Windows 2000 to communicate with other network devices that are using IPX/SPX

B. Supports the networking APIs that provide the interprocess communication (IPC) services

1. Winsock, which supports existing NetWare applications written to comply with the NetWare IPX/SPX Sockets interface

2. NetBIOS over IPX, implemented as NWLink NetBIOS, which supports communication between a NetWare client running NetBIOS and a computer running Windows 2000 and NWLink NetBIOS

C. Provides NetWare clients access to applications designed for Windows 2000 Server

1. Microsoft SQL Server

2. Microsoft SNA Server

Note 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).

|19| 3. Installing NWLink

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

B. Use the Network and Dial-Up Connections window.

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

D. Click Install.

E. In the Select Network Protocol dialog box, select NWLink IPX/SPX/NetBIOS Compatible Transport Protocol and then click OK.

|20| 4. Configuring NWLink

A. NWLink configuration involves three components

1. Frame type

2. Network number

3. Internal network number

|21| B. By default, Windows 2000 detects a frame type and a network number automatically.

C. Windows 2000 also provides a generic network number.

D. You must manually specify an internal network number if you plan to run FPNW or IPX.

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

|22| F. Frame type

1. Defines the way that the network adapter card formats data

2. Must configure the NWLink frame type to match the frame type on the NetWare server

Note A 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.

3. You can manually configure the frame type.

|23| 4. Topologies and frame types supported by NWLink

a. Ethernet topology supports Ethernet II, 802.3, 802.2, and Sub Network Access Protocol (SNAP).

b. Token Ring topology supports 802.5 and SNAP.

c. FDDI (Fiber Distributed Data Interface) supports 802.2 and SNAP.

Note On 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.

|24| G. Network number

1. Each frame type configured on a network adapter card requires a network number.

2. The network number must be unique for each network segment.

3. All computers on a segment using the same frame type must use the same network number to communicate with each other.

4. You can manually specify a network number by using the Registry Editor.

|25| H. Internal network number

1. Uniquely identifies a computer on the network for internal routing

2. Eight-digit hexadecimal number that is set to 00000000 by default

|26| 3. Manually assign an internal network number if

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

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

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

Note If 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.

5. Installing and Configuring NWLink

Chapter 7, Lesson 3

Other Protocols Supported by Windows 2000

1. NetBEUI

|27| A. Introduction to NetBEUI

1. A protocol developed for LANs with 20 to 200 computers

2. A small, fast, and efficient protocol

3. Not routable

|28| B. NetBEUI capabilities

1. Connection-oriented and connectionless communication between computers

2. Self-configuration and self-tuning

3. Error protection

4. Small memory overhead

|29| C. NetBEUI limitations

1. Designed for departmental-sized LANs

2. Must connect computers running Microsoft Windows 2000 and NetBEUI by using bridges

Note NetBEUI is not routable, so you can’t use routers.

3. Relies on broadcasts for many of its functions, such as name registration and discovery, so creates more broadcast traffic