Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server

Transcription

1 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server

2 2 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server Module 1: Reviewing the Suite of TCP/IP Protocols Overview The suite of TCP/IP Protocols is basically the same in Microsoft Windows Server 2003 as it was in Windows 2000 Server. There are, however, some changes in the protocol suite. Suggestions for new functionality obtained in Request for Comments (RFCs) are submitted by the engineering community for review by Internet members as a whole. There are times when Microsoft includes new TCP/IP functionality in its operating system products before a standard has been finalized. An example of this is the secure dynamic updates introduced in the Windows 2000 timeframe. Lesson: Overview of the OSI Model What is the OSI Model? The Layers of the OSI Model Lesson: Overview of the TCP/IP Protocol Suite Why Do I Need to Know About TCP/IP? What Is the Architecture of the TCP/IP Protocol Suite? How Does the TCP/IP Model Relate to the OSI Model? How an IP Packet Moves Through the Suite of TCP/IP Protocols

3 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server 3 Practice: Associating the TCP/IP Suite of Protocols with the OSI Model Lesson: Viewing Frames Using Network Monitor What Is Ping? What Is Network Monitor? Network Monitor is very much the same as it was in Windows 2000 Server. However, the Windows Server 2003 version does have a few changes in the configuration screens. For example, the Save Configuration option on the Capture menu in Windows 2000 Server is omitted in Windows Server In addition, Identify Network Monitor Users and the link to Performance Monitor are omitted in the Windows Server 2003 version of Network Monitor. The Ping utility has been updated in Windows Server 2003 to provide some IPv6 capabilities. IPv6 switches are not available in the default installation of Windows 2000 Server. How to Install Network Monitor

4 4 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server How to Capture Frames Network Monitor is very much the same as it was in Windows 2000 Server. However, some configuration screens and procedures have changed. Procedure to Capture Frames In Windows 2000 Server, the user is prompted to select an interface identified by MAC address. If your computer contains two or more adapters, the user needs to open a command prompt and use the following command to display the network configuration information for the computer: ipconfig /all How to Filter for Select Frames This command helps the user identify which adapter is the primary adapter because it also identifies the IP address and name of each network adapter. Because most users identify the network adapter by name, however, this introduces additional tasks needed to successfully utilize Network Monitor. When Network Monitor is opened in Windows Server 2003, the user is prompted to select an interface by name. This is a new feature of Windows Server 2003 that makes the tool easier to use. Examining Captured Network Traffic Practice: Examining Packets Additional Resources See the RFCs for the TCP/IP protocols under Additional Reading on the Student Materials compact disc.

5 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server 5 Module 2: Assigning IP Addresses in a Multiple Subnet Network Overview Lesson: Assigning IP Addresses The Components of an IP Address What Are the Classes of IP Addresses? Practice: Determining the Class of an IP Address How Dotted Decimal Notation Relates to Binary Numbers How to Convert Dotted Decimal Notation to Binary Format Practice: Converting Numbers Between Decimal and Binary How Subnet Masks Work Practice: Identifying the Components of an IP Address

6 6 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server Guidelines for IP Addressing Practice: Identifying Invalid IP Addresses Lesson: Creating a Subnet What Is a Subnet? How to Create a Subnet How Bits Are Used in a Subnet Mask How to Calculate the Subnet Mask Defining Subnet IDs No changes in Windows Server 2003 Practice: Calculating a Subnet Mask Lesson: Using IP Routing Tables What Is a Router? Using a Default Gateway

7 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server 7 The Role of Routing in the Network Infrastructure How the Computer Determines Whether an IP Address Is a Local or Remote Address Practice: Determining Whether an IP Address Is a Local or Remote Address What Is Static and Dynamic Routing? How IP Uses the Routing Table Using the Routing Table in Windows Server 2003 How the IP Protocol Selects a Route Practice: Viewing and Modifying a Routing Table Lesson: Overcoming Limitations of the IP Addressing Scheme How IP Addresses Are Wasted What Are Private and Public IP Addresses?

8 8 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server What Is VLSM? How to Use VLSM What Is Supernetting? Using CIDR to Implement Supernetting Additional Resources

9 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server 9 Module 3: Configuring a Client IP Address Overview Windows Server 2003 has introduced some network configuration changes that are not available in Windows 2000 Server. Objectives Windows Server 2003 has a new feature that first appeared in Windows XP called Alternate Configuration. This feature is not available in Windows 2000 Server. Lesson: Configuring a Client to Use a Static IP Address Static and Dynamic IP Addresses How to Manually Assign a Static IP Address Viewing Static TCP/IP Configuration Viewing TCP/IP Configuration Using Ipconfig Practice: Manually Assigning and Viewing an IP Address Lesson: Configuring a Client to obtain an IP Address Automatically What Is DHCP?

10 10 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server Obtaining an Address Using DHCP Viewing DHCP Assigned Settings on the Client Practice: Configuring a Client to Use DHCP Renewing an IP Address How to Manually Release, Renew, and Verify an IP Address Practice: Manually Releasing and Renewing an Address Lesson: Using Alternate Configuration Alternate Configuration is a new feature of Windows Server 2003 that enables a mobile computer user to obtain correct IP address settings based upon location. This feature is not available in Windows 2000 Server. Lesson Objectives Windows Server 2003 has a new feature that first appeared in Windows XP called Alternate Configuration. This feature allows a user to define a manually assigned IP address or to use APIPA rather than DHCP, where the alternate network does not have access to a DHCP server. This feature is not available in Windows 2000 Server. How Alternate Configuration Assigns IP Addresses Windows Server 2003 enables a user to specify more than one set of TCP/IP configuration parameters for the same network adapter. User configured Alternate Configuration Windows Server 2003 enables a user to specify static IP address settings or APIPA for the alternate configuration.

11 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server 11 How to Determine Which Alternate Configuration Method to Use APIPA is used to configure local networks that will not connect to the Internet. If Internet connectivity is required at the alternate network location and DHCP cannot be used, the user configured options permit a secondary set of TCP/IP parameters to be specified. This feature is not available in Windows 2000 Server. How Alternate Configuration Works Mobile users are sometimes faced with a network environment that requires the use of a static IP address rather than DHCP. This might be the requirement of an ISP or a network at a remote location that uses static IP addresses. Alternate configuration allows the computer to be configured to detect this network environment automatically and to assign the appropriate configuration where a DHCP server cannot be detected. This is helpful because users are often unable to troubleshoot connectivity problems without the assistance of a network administrator. This feature is not available in Windows 2000 server. How APIPA Assigns IP Addresses Both Windows 2000 Server and Windows Server 2003 default to APIPA when a DHCP server is not detected. How APIPA Works In Windows Server 2003, APIPA can be selected as an Alternate Configuration. Although the Alternate Configuration tab is not available in the Internet Protocol (TCP/IP) Properties page of Windows 2000 Server, the default functionality is the same. When a DHCP server cannot be detected, Windows 2000 Server defaults to APIPA. Practice: Configuring Alternate Configuration Additional Resources Practice The Alternate Configuration tab is a new properties page in Internet Protocol TCP/IP Properties configuration. This configuration page is not available in Windows 2000 Server.

12 12 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server Module 4: Configuring a Client for Name Resolution Overview Lesson: Resolving Client Names The Name Resolution Process The procedure for resolving client names is the same in both Windows 2000 Server and Windows Server Lesson: Managing the ARP Cache Static and Dynamic ARP Cache Entries How ARP Resolves IP Addresses to MAC Addresses Using the ARP Tool to Manage the ARP Cache Practice: Identifying a MAC Address Practice: Viewing and Modifying the ARP Cache Lesson: Overview of NetBIOS The Types of Names Computers Use

13 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server 13 What Is NetBIOS? What Is a NetBIOS Name? What Is NetBT? Practice: Determining the NetBT Node Type of a Client What Is Nbtstat? Lesson: Using Static Naming Methods Using an Lmhosts file Practice: Adding an Entry to the Lmhosts File Guidelines for Configuring a Client to Use Lmhosts Using a Hosts File Practice: Adding an Entry to the Hosts File Lesson: Using Dynamic Naming Methods

14 14 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server What Is WINS? What Is DNS? The DNS Suffix Primary DNS Suffix The properties sheet of the System icon in Control Panel, which can also be invoked by choosing the properties sheet of the My Computer folder, has changed in Windows Server The Network Identification tab in Windows 2000 Server has been renamed the Computer Name tab in Windows Server Practice: Using Ipconfig to Manage the DNS Client Resolver Cache Practice: Configuring a Client to use a Name Server Lesson: Summarizing the Name Resolution Process How Client Names Are Resolved

15 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server 15 Module 5: Isolating Common Connectivity Issues Overview Although the process of isolating and troubleshooting common connectivity issues remains largely unchanged from Windows 2000 Server to Windows Server 2003, this module reinforces the importance of a systematic approach to Network Troubleshooting which is derived largely from MOF practices and processes. Lesson: Isolating Common Connectivity Issues The procedure for resolving client names is the same in both Windows 2000 Server and Windows Server Why You Need to Isolate Connectivity Issues Before You Touch Anything Isolating the Issue Resolving the Issue After the Issue Is Resolved Lesson: Using Utilities and Tools to Isolate Connectivity Issues

16 16 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server Installing Windows Server 2003 Support Tools The name of the.msi file used for installing Support Tools in Windows Server 2003 has been changed. The Windows Server 2003 file is called Suptools.msi. The Windows 2000 file was called 2000RKST.msi. The local path on the Windows Server 2003 product compact disc remains the same: <cdrom drive>\tools\support\ as does the default installation path: c:\program Files\Support Tools\. The following table charts the differences between the two toolsets. Windows 2000 Server Windows Server 2003 ACL Diagnostics (acldiag.exe) Active Directory Administration Tool (ldp.exe) Active Directory Diagnostics Tool (dsastat.exe) Active Directory Object Manager (movetree.exe) Active Directory Replication Monitor (replmon.exe) Active Directory Search Tool (search.vbs) ADSI Edit Snap-in (adsiedit.msc) Advanced Power Management Status (apmstat.exe) Application Compatibility Program (apcompat.exe) Browser Status (browstat.exe) ClonePrincipal (clonepr.dll) Dependency Walker (depends.exe) Windows 2000 Resource Kit Distributed File System Utility (dfsutil.exe) ACL Diagnostics (acldiag.exe) LDP Tool (ldp.exe) Directory Services Utility (dsastat.exe) Move Users (movetree.exe) Active Directory Replication Monitor (replmon.exe) Active Directory Search Tool (search.vbs) Application Deployment Diagnosis (addiag.exe) ADSI Edit Snap-in (adsiedit.msc) Advanced Power Management Status (apmstat.exe) Moved to Microsoft Debugging Tools Binary File Difference Finder (bindiff.exe) BITS Administration Utility (bitsadmin.exe) Browser Status (browstat.exe) Cabinet Tool (cabarc.exe) ClonePrincipal (clonepr) FRS Connection Status Report (connstat.cmd) Dependency Walker (depends.exe) Device Console Utility (devcon.exe) DFS and SYSVOL Replication Topology Analysis Tool (topchk.cmd) DHCP Server Locator Utility (dhcploc.exe) Distributed File System Utility (dfsutil.exe)

17 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server 17 (continued) Windows 2000 Server Windows Server 2003 Windows 2000 Resource Kit Windows 2000 Resource Kit DiskProbe (dskprobe.exe) Domain Controller Diagnostic Tool (dcdiag.exe) DNS Server Troubleshooting Tool (dnscmd.exe) Directory Services ACL Editor (dsacls.exe) Dump Check (dumpchk.exe) Windows 2000 Resource Kit Windows 2000 Resource Kit File and Directory Comparison (windiff.exe) File Version (filver.exe) Windows 2000 Resource Kit Global Flags Editor (gflags.exe) Windows 2000 Resource Kit Kerberos Keytab Setup (ktpass.exe) Kerberos Setup (ksetup.exe) Windows 2000 Resource Kit Memory Pool Monitor (poolmon.exe) Memory Profiling Tool (memsnap.exe) Network Connectivity Tester (netdiag.exe) NLTest (nltest.exe) Windows 2000 Resource Kit Point-to-Point Tunneling Protocol Ping Utilities Directory Disk Usage (diruse.exe) Disk Manager Diagnostics (dmdiag.exe) DiskProbe (dskprobe.exe) Domain Controller Diagnostic Tool (dcdiag.exe) DNS Server Troubleshooting Tool (dnscmd.exe) DNS Lint (dnslint.exe) Directory Services ACL Editor (dsacls.exe) Functionality moved to Microsoft Debugging Tools Encrypting Files System Information (efsinfo.exe) Extensible Performance Counter List (exctrlst.exe) Windiff File and Directory Comparison (windiff.exe) File Version (filver.exe) Fault Tolerant Disk Mounter (ftonline.exe) FRS Health Check (health_chk.cmd) FRS inbound and Outbound Logs Summary Report Tool (iologsum.cmd) Get Security ID (getsid.exe) Global Flags Editor (gflags.exe) HTTP Configuration Utility (httpcfg.exe) IAS Parse Tool (iasparse.exe) Kerberos Keytab Setup (ktpass.exe) Kerberos Setup (ksetup.exe) Manipulate Service Principal Names for Accounts(setspn.exe) Memory Pool Monitor (poolmon.exe) Memory Profiling Tool (memsnap.exe) Network Monitor Capture Utility (netcap.exe) Network Connectivity Tester (netdiag.exe) NLTest (nltest.exe) NTFRS Utility (ntfrsutl.exe) Removed from Windows Server 2003 Port Query (portqry.exe)

18 18 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server (continued) Windows 2000 Server Windows Server 2003 Process Resource Monitor (Pmon.exe) Process Viewer (pviewer.exe) Registry Console Tool (reg.exe) Remote Command Line (remote.exe) Remote Storage Diagnostic Utility (rsdiag.exe) Remote Storage File Analysis Utility (rsdir.exe) Replication Diagnostics Tool (repadmin.exe) Security Administration Tools (SIDWalk.exe) Security Descriptor Check Utility (sdcheck.exe) Security Migration Editor (sidewalk.msc) Show Access Control Lists (showaccs.exe) SNMP Query Tool (snmputilg.exe) System Information (msinfo32.exe) Task Killing Utility (kill.exe) Task List Viewer (tlist.exe) Windows 2000 Domain Manager (netdom.exe) Windows Installer Cleanup Utility (msicuu.exe) Windows Installer Zapper (msizap.exe) Windows Report Tool (winrep.exe) Winsock Remote Console (wsremote.exe) Moved to Windows Server 2003 Resource Kit Process Viewer (pviewer.exe) Moved to %windir%\system32 Remote Command Line (remote.exe) Remote Storage Diagnostic Utility (rsdiag.exe) Remote Storage File Analysis Utility (rsdir.exe) Replication Diagnostics Tool (repadmin.exe) Security Administration Tools (SIDWalk.exe) Security Descriptor Check Utility (sdcheck.exe) Security Migration Editor (sidewalk.msc) Service Pack Check (spcheck.exe) Show Access Control Lists (showaccs.exe) Moved to Program Files\Common Files\Microsoft Shared\MSInfo %windir%\system32\taskkill.exe %windir%\system32\tasklist.exe Windows Domain Manager (netdom.exe) Windows Installer Cleanup Utility (msicuu.exe) Windows Installer Zapper (msizap.exe) Replaced by Remote Command command line (remote.exe)

19 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server 19 How to Use Network Diagnostics to Gather System Information Network Diagnostics is a new feature of Windows Server 2003 that allows a user to collect information about the configuration and operation of the computer to detect malfunctions. This feature is not available in Window 2000 Server. Definition Network Diagnostics tests various components of the computer to determine where a malfunction might exist. The following chart details basic categories of information displayed by Network Diagnostics:! Internet Service a. Mail Service b. News Service c. Web Proxy Service! Computer Information a. Computer System b. Operating System c. Version! Modems and Network Adapters a. Modems b. Network Adapters c. Network Clients TCP/IP Utilities Using Ping to Test Connectivity to a Remote Host Interpreting Ping Error Messages

20 20 Appendix A: Differences Between Microsoft Windows Server 2003 and Microsoft Windows 2000 Server Other TCP/IP Utilities You Might Find Useful Using Netsh Network Connections Repair Repair is a menu option on the Network Connections menu. Right-clicking any network connection brings up a menu that contains a Repair option. The Repair option will perform the following tasks:! Renew DCHP Lease! Flush ARP cache! Flush NetBIOS cache! Initiate NetBIOS name refresh! Flush DNS cache! Register DNS name This feature is not available in Windows 2000 Server. The Netsh has been updated with additional options in Windows Server Definition Netsh has added the following new contexts:! Diag allows you to launch the Network Diagnostics Tool from the command line in addition to displaying all network configuration information.! IPSec allows IPSec policies to be displayed and manipulated! RPC display RPC binding information by subnet These contexts are not available in Windows 2000 Server. How to Use Netsh to Configure a Network Interface Adapter Additional Resources