1. Microsoft Windows XP Professional
MCSE Exam

2. Installing, Configuring, and Troubleshooting Network Protocols
Chapter Four

3. TCP/IP Protocol Suite A routable networking protocol
A technology for connecting dissimilar systems
A robust, scaleable, cross-platform client/server framework
A method of gaining access to Internet resources

4. The Network Interface Layer

5. Configuring TCP/IP to Use a Static IP Address
By default, client computers running Windows XP, Windows 2000, Windows ME, Windows 98, or Windows 95 obtain TCP/IP configuration information automatically from the Dynamic Host Configuration Protocol (DHCP) Service.

6. Two ways to have an IP Address
By Statically enter an IP address.
By Configuring your computer to automatically receive and IP Address

7. To have a Static IP Address

8. Configuring TCP/IP to Obtain an IP Address Automatically

9. How DHCP Works
The Process is a Four Step process.

10. How DHCP Works Step 1 Client DHCP Server
Client sends DHCPDISCOVER broadcast packet – “Looking for a DHCP Server

11. DHCP Step 2 Client DHCP Server
DHCP Server responds with a DHCPOFFER packet – “I’m a DHCP Server and here is my IP address offer.”

12. DHCP Step 3 Client DHCP Server
Client responds to one of the DHCP Servers with a DHCPREQUEST packet. – “I will take this IP Address.”

13. DHCP Step 4 Client DHCP Server
The Client Then receives the IP address from the DHCP Server.

14. Automatic Private IP addressing
If no DHCP is available
Server running the DHCP Service is unavailable.
No IP address returned
Automatic Private IP addressing
IP address
Request 1 2 3

15. Automatic Private IP Addressing
The Internet Assigned Numbers Authority (IANA) has reserved for Automatic Private IP Addressing. As a result, Automatic Private IP Addressing provides an address that is guaranteed not to conflict with routable addresses.

16. Disabling Automatic Private IP Addressing
By default, the Automatic Private IP Addressing feature is enabled. However, you can disable it by specifying an alternate configuration to use if a DHCP server cannot be located.

17. Alternate Configuration

18. TCP/IP Utilities Utilities for Troubleshooting TCP/IP
Utilities for Testing TCP/IP Connectivity

19. TCP/IP Utilities IPCONFIG Using Ping
Type ipconfig /all | more to prevent the ipconfig output from scrolling off the screen; to scroll down and view additional output, press the Spacebar
Using Ping
ie c:\>ping

20. Using Ipconfig and Ping
Ping (loopback address)
Ping IP address of the computer
Ping IP address of default gateway
Ping IP address of remote host 3 4 5 1 2

21. Practice:
Installing and Configuring TCP/IP
Page 144 – 150

22. NWLink
Microsoft's implementation of Novell's NetWare Internetwork Packet Exchange/Sequenced Packet Exchange (IPX/SPX) protocol.

23. Installing NWLink

24. NWLink Features
The procedure for installing NWLink is the same process that you use to install any network protocol in Windows XP:
NWLink configuration involves three components:
frame type
network number
internal network number

25. NWLink Features Frame Type
A frame type defines the way that the network adapter card formats data.
Topologies and frame types supported by NWLink
Ethernet
Token Ring
Fiber Distributed Data Interface (FDDI)

26. NWLink Features 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.

27. NWLink Features
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.
Note page 155

28. NWLink Features 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 by default.

29. Practice:
Installing and Configuring NWLink
Pages 159 – 161

30. Other Protocols NetBEUI Capabilities
Connection-oriented and connectionless communication between computers
Self-configuration and self-tuning
Error protection
Small memory overhead
NetBEUI is NOT included, but on the XP installation CD.

31. NetBEUI No longer included with Windows Limitations
Designed for department-sized LANs.
Non-routable.
Broadcast-based.

32. Network Monitor Driver
You can also use Microsoft Systems Management Server (SMS) and Network Monitor to collect statistics from computers that are running Network Monitor Agent.
Use the Network Monitor as a diagnostic tool to find broadcast problems.

33. Network Bindings
Network bindings enable communication between network adapter card drivers, protocols, and services
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.

34. Network Bindings

35. Binding Between Architectural Levels
Binding is the process of linking network components on different levels to enable communication between those components.

36. Combining Network Bindings
all three protocols are bound to the Workstation service, but only the routable protocols, NWLink and TCP/IP, are bound to the Server service
Network Driver Interface Specification (NDIS) 5.1 provides the capability to bind multiple protocols to multiple network adapter card drivers.

37. Configuring Network Bindings
You can configure your network bindings by using My Network Places. Note page 164.

38. Specifying Binding Order
optimize network performance
Most servers will run TCP/IP only therefore TCP/IP should be bound first.
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.

39. Practice:
Working with Network Bindings
Pages 165 – 167