70-270, MCSE/MCSA Guide to Installing and Managing Microsoft Windows XP Professional and Windows Server 2003 Chapter Three Managing Network Protocols
Guide to MCSE , Objectives Identify the components of a network system Identify and describe the protocols commonly used in Windows XP and Windows Server 2003 Configure network components Describe the TCP/IP architecture Explain name and address resolution
Guide to MCSE , Objectives (continued) Configure and use TCP/IP protocols and services Work with TCP/IP command-line utilities Use Windows XP Remote Assistance and Remote Desktop features Understand Windows XP as used in NetWare networks Explain the purpose and functioning of redirectors
Guide to MCSE , Networking Overview Figure 3-1: Major network components
Guide to MCSE , Networking Overview (continued) Network’s pathway provides hardware for transmitting signals from one computer to another –Bits must be organized into packets Protocol stack: Collection of network protocols –Responsible for formatting packets of data –Proprietary and nonproprietary protocols Windows XP and Server 2003 designed for multiple protocols –Use similar techniques for modifying network components and configurations
Guide to MCSE , Network Protocol Stacks Supported by Windows XP NetBEUI, NetBIOS, TCP/IP, NWLink TCP/IP: All-embracing suite of protocols that cover wide range of capabilities –Designed to support multiple routing protocols –Incorporates better error detection and handling –Neither extremely fast nor simple to use NWLink: Microsoft implementation of Novell’s IPX/SPX protocol stack –Works with NDIS driver technology
Guide to MCSE , Network Protocol Stacks Supported by Windows XP (continued) NWLink (continued): –Advantages: SPX II Autodetection of frame types Direct hosting over IPX –Disadvantages: IPX might not scale well on large networks Lacks built-in feature for centralized name and address management IPX imposes higher memory requirements on DOS machines and runs less efficiently across slow serial connections
Guide to MCSE , Network Protocol Stacks Supported by Windows XP (continued) Table 3-1: TCP/IP-supported protocols and services
Guide to MCSE , Network Protocol Stacks Supported by Windows XP (continued) Table 3-1 (continued): TCP/IP-supported protocols and services
Guide to MCSE , Network Protocol Stacks Supported by Windows XP (continued) Table 3-1 (continued): TCP/IP-supported protocols and services
Guide to MCSE , Network Protocol Stacks Supported by Windows XP (continued) NetBEUI and DLC: Deemphasized in Windows XP and Windows Server 2003 NetBIOS: Widely used but simple PC client/server interprocess communication (IPC) mechanism –Works with all TDI-compliant transports NWNBLink NBT –By default, Windows XP TCP/IP configured to use NetBIOS setting defined by local DHCP server
Guide to MCSE , Configuring Network Components Figure 3-2: The Network Connections utility
Guide to MCSE , Configuring Network Components (continued) Figure 3-3: The General tab of the Local Area Connection Properties dialog box
Guide to MCSE , Configuring Network Components (continued) Elements that can be installed: –Client for Microsoft Networks –Client Service for NetWare –QoS Packet Scheduler –File and Printer Sharing for Microsoft Networks –Service Advertising Protocol –Internet Protocol (TCP/IP) –Network Monitor Driver –NWLink IPX/SPX/NetBIOS Compatible Transport Protocol
Guide to MCSE , Activity 3-1: Reviewing Local Area Connection Properties Objective: Use Network Connections in Control Panel to view the properties of the local area connection and the status of the network connection
Guide to MCSE , Wireless Networking Allows for reliable network connectivity and communications without a network cable Two primary components: –Base station: Wireless hub designed to support network connections for wireless-enabled clients –NIC Wireless standards: –802.11g: Supports 54 Mbps throughput –802.11b: Supports 11 Mbps throughput –Both support WEP
Guide to MCSE , Network Setup Wizard Used to configure nondomain networks for small offices or home use of Windows Allows easy configuration of: –Easy-to-remember computer names, such as “Study Computer” or “Den System” –Your Internet connection, whether it’s via a dial-up or dedicated link –Internet Connection Sharing (ICS) –Internet Connection Firewall (ICF) –TCP/IP for networking
Guide to MCSE , Managing Bindings Binding: Order in which networking components linked –Affects system behavior and performance –By default, XP binds any two components that share common boundary layer Complete binding Disabling unused and unneeded protocol bindings improves system performance –Decreases likelihood of communication errors XP makes connections in order in which protocols bound
Guide to MCSE , Managing Bindings (continued) Figure 3-6: The Adapters and Bindings tab
Guide to MCSE , Activity 3-2: Working with Network Bindings Objective: Use the Advanced Settings of the Network Connections object to view the network bindings
Guide to MCSE , Bridging and Routing Bridging takes place at data link layer using MAC addresses Routing works at Internet layer using network addresses XP Professional can’t perform routing –Can act as bridge between two network segments Can support single network bridge per system
Guide to MCSE , Bridging and Routing (continued) Figure 3-7: Multiple network segments connected by a server
Guide to MCSE , TCP/IP Architecture Figure 3-8: The TCP/IP protocol stack
Guide to MCSE , TCP/IP Architecture (continued) IP Addressing: –Four octets, each between 0 and 255 –Subnet mask: Blocks out address’s host portion Only network ID portion remains visible to computer Enables sending computer to determine whether destination on same network segment –Classless interdomain routing (CIDR): Divided available addresses into more subnetworks Table 3-2: Classes of IP addresses
Guide to MCSE , TCP/IP Architecture (continued) Private IP Addressing and Network Address Translation: –Public IP addresses: Used to connect to Internet –Private networks can potentially use any IP address range To access other networks, each computer must have IP address of its gateway –Network Address Translation (NAT): Used to transmit requests from private network to Internet Table 3-3: Private IP addresses
Guide to MCSE , TCP/IP Architecture (continued) Figure 3-9: Private networking using NAT to connect to the Internet
Guide to MCSE , TCP/IP Architecture (continued) Internet Protocol (IP) Suite: –Internet Protocol (IP): Provides source and destination addressing and routing in TCP/IP Connectionless datagram protocol –Internet Control Message Protocol (ICMP): Used to send control messages between IP hosts e.g., error messages and confirmations –Address Resolution Protocol (ARP): Used to associate logical and physical addresses –IPv6: Uses 128-bit address space
Guide to MCSE , TCP/IP Architecture (continued) Dynamic Host Configuration Protocol: –DHCP used to automatically configure computers with IP address information obtained from DHCP server Can be installed on Windows Server 2003 systems Configured to block(s) of IP addresses –Automatic Private IP Addressing (APIPA): Used if no DHCP service available –DHCP server handles granting, renewing, or canceling leases
Guide to MCSE , TCP/IP Architecture (continued) Automatic Private IP Addressing: Allows home users and small business users to create single subnet TCP/IP network –Without using static addressing or DHCP server Transmission Control Protocol (TCP): Primary Internet transport protocol –Accepts messages and provides transportation to TCP peer on remote network host –Connection oriented –TCP port number used to determine which process on host is to receive particular packet
Guide to MCSE , TCP/IP Architecture (continued) User Datagram Protocol (UDP): Connectionless transport protocol –Used for distributed file systems e.g., Network File System (NFS) –Used for TFTP File Transfer Protocol (FTP): Connection-oriented file transfer service –Uses TCP as transport protocol –Windows Server 2003 can provide FTP services to clients
Guide to MCSE , TCP/IP Architecture (continued) Trivial File Transfer Protocol (TFTP): Lightweight analog of FTP –Uses UDP rather than TCP Telnet: Remote terminal emulation protocol –Used for connectivity between dissimilar systems Simple Mail Transfer Protocol (SMTP): Provides IP-based messaging services Simple Network Management Protocol (SNMP): Used for network management
Guide to MCSE , Name-to-Address Resolution TCP/IP translates names to IP addresses using a number of different protocols NetBIOS: Resolves name to address by sending broadcast packet to all computers on a subnet –Asks for address of specific computer or service name –Runs over transport protocols Including TCP/IP, NWLink, and NetBEUI –Does not work over routers
Guide to MCSE , Name-to-Address Resolution (continued) Lmhosts File: Static file placed on network members to provide resolution mechanism between NetBIOS names and IP addresses –Each line contains IP address and corresponding NetBIOS name Windows Internet Naming Service (WINS): Dynamically associates NetBIOS names with IP addresses –Automatically updates as systems enter and leave network
Guide to MCSE , Name-to-Address Resolution (continued) The Hosts and Lmhosts Files: –Hosts file provides name to IP address information for TCP/IP protocols Can be used to hard-code important systems DNS: Translates symbolic names to corresponding numeric IP addresses –Provides reverse lookup services
Guide to MCSE , Activity 3-3: Resolving Names to Addresses Objective: View the contents of the Hosts and Lmhosts files –Via Notepad –In \Windows\System32\Drivers\Etc folder
Guide to MCSE , TCP/IP Configuration Performed through Network Connections window –If machine uses DHCP, DHCP server configures –If not, may need following info: Unique IP address for computer Subnet mask for network Address of default gateway Address DNS server(s) Address for WINS server
Guide to MCSE , TCP/IP Configuration (continued) Figure 3-10: The DNS tab of the Advanced TCP/IP Settings dialog box
Guide to MCSE , Activity 3-4: Configuring TCP/IP Objective: Configure the IP address of a computer from the Local Area Connection properties dialog box –Via Network Connections window
Guide to MCSE , TCP/IP Command Line Utilities Rsh (remote shell): User on one network host accesses shell commands on another network host Rexec (remote execution): User on one network host to runs programs remotely across network Route Command: View and manipulate local IP routing tables Table 3-4: Valid commands for the Route command action
Guide to MCSE , TCP/IP Command Line Utilities (continued) Tracert Command: Determines path used by ICMP echo request message –Displays routers encountered between client and target system Ping Command: Uses ICMP to inquire whether designated host is reachable –Ping own system by entering Ping or Ping loopback Pathping Command: Provides name and IP address of each gateway a Ping packet traverses
Guide to MCSE , TCP/IP Command Line Utilities (continued) Ipconfig Command: Used to manage and view information related to DHCP and DNS Figure 3-12: The results of an Ipconfig /all command
Guide to MCSE , TCP/IP Command Line Utilities (continued) Netstat command: Displays list of active TCP connections –Including open ports, Ethernet statistics, IP routing table, and IPv4/IPv6 statistics Nbtstat command: Displays protocol statistics for NetBIOS over TCP/IP (NetBT), NetBIOS name tables, and the NetBIOS name cache
Guide to MCSE , Activity 3-5: Testing TCP/IP Communications Objective: Use the Ping command to test the communication with a host address –Must know IP address, host name, or FQDN of at least one system on network –Run from command prompt
Guide to MCSE , Activity 3-6: Testing Name-to-address Resolution Objective: View the contents of the Hosts file and modify it to use your name as an alternative name for your computer –Review Activity 3-3 first –Use Ping to test name-to-address resolution
Guide to MCSE , Windows XP Remote Assistance Tools: Remote Assistance Designed to simplify training users or walking users through tasks To initiate Remote Assistance invitation, use “Invite a friend to connect to your computer with Remote Assistance” link in Help and Support Both systems must be running Windows XP or newer with Windows Messenger Service or MAPI compliant utility Uses Remote Desktop Protocol (RDP) –Uses TCP port 3389 for establishing session
Guide to MCSE , Activity 3-8: Providing Remote Assistance Objective: Respond and take control of a person’s computer with the Remote Assistance utility
Guide to MCSE , Windows XP Remote Assistance Tools: Remote Desktop Developed so that workers can access work desktops from home systems Enabled through Remote Desktop Web Connection –Component of IIS After connected, have full control over host client Remote Desktop Connection utility: Second method for Remote Desktop –Does not need IIS
Guide to MCSE , Windows XP and NetWare Networks Many companies use Novell NetWare –Microsoft includes interconnectivity enhancements to allow Windows XP computers to connect to NetWare servers Bindery: Proprietary database that contains network resource information Novell Directory Services (NDS): Hierarchical database used by NetWare 4.0 and later servers to store network resource and object data –Comparable to Active Directory
Guide to MCSE , Windows XP and NetWare Networks (continued) Figure 3-14: An eDirectory (NDS) tree structure for an organization
Guide to MCSE , Windows XP and NetWare Networks (continued) NetWare Compatibility Components: –NWLink protocol: Microsoft’s implementation of IPX/SPX –Client Service for NetWare: Allows Windows XP computer to access resources on NetWare server Installing NetWare Components: –Installed through a connection object in Network Connections File and Print Servers: –CSNW adds NetWare-focused redirector that acts as an extension of file system
Guide to MCSE , Redirectors Examines requests for system resources and decides whether they are local or remote –Handles transmission of remote requests across network Workstation Service: Supports client access to network resources –Handles functions such as logging in and connecting to network shares –Two elements: User mode interface and redirector
Guide to MCSE , Redirectors (continued) Server Service: Handles creation and management of shared resources –Performs security checks against requests for shared resources –Allows Windows XP computer to act as a server on a client/server network Multiple Universal Naming Convention Provider: Defines link between applications that make UNC requests for different redirectors –Allows applications to remain oblivious to number or type of redirectors in use
Guide to MCSE , Redirectors (continued) Universal Naming Convention Names: Represent format used in NetBIOS-oriented name resolution systems Multi-Provider Router: Lets applications written to older Microsoft specifications behave as though they were written to conform to UNC naming –Can recognize UNCs representing drive mappings –Handles all Win32 Network API calls
Guide to MCSE , Summary Windows XP Professional and Windows Server 2003 both provide network access primarily by using TCP/IP, but also support the NWLink protocol TCP/IP is routable, supports enterprise-level networks, and has been designed to interconnect dissimilar types of computers TCP/IP is an industry-standard protocol that provides easy cross-platform communication
Guide to MCSE , Summary (continued) Thorough knowledge of TCP/IP is important Both Windows XP and Windows Server 2003 support and use numerous TCP/IP subprotocols and utilities, including FTP, Telnet, SMTP, SNMP, Route, Tracert, Ping, TFTP, Hosts and Lmhosts files, DNS, WINS, Netstat, Nbtstat, and Ipconfig Windows includes a number of applications that use TCP/IP and provide Internet connectivity
Guide to MCSE , Summary (continued) Windows XP includes several new networking features and utilities, including network bridging, Remote Assistance, Remote Desktop, improved support for wireless networking, and support for the upcoming IPv6 protocol Windows XP includes NWLink and Client Service for NetWare (CSNW) to enable users to access resources and services from NetWare-based networks Redirectors are used to examine all requests for system resources and decide whether these requests are local or remote