The Best Damn Windows Server 2003 Book Period- P80

The Best Damn Windows Server 2003 Book Period- P80:The latest incarnation of Microsoft’s server product,Windows Server 2003, brings manynew features and improvements that make the network administrator’s job easier.Thischapter will briefly summarize what’s new in 2003 and introduce you to the four membersof the Windows Server 2003 family: the Web Edition, the Standard Edition, theEnterprise Edition, and the Datacenter Edition.
Nội dung trích xuất từ tài liệu:
The Best Damn Windows Server 2003 Book Period- P80756 Chapter 21 • Planning, Implementing, and Maintaining the TCP/IP Infrastructure You should also provide a DHCP server at each location. When you have multiple DHCP servers on your network, use the 80/20 rule to balance the load on the subnet: 80 percent of the scope will be on the primary server, with 20 percent on the other server.The DHCP server must have an interface on each network for which it has a scope defined, or you must locate a DHCP relay server on the same subnet as the DHCP clients. If you implement WINS, you will need to examine the quantity of data replicated between WINS servers and the cost of WINS reverse lookups from DNS servers.You should minimize the number of WINS servers you implement in order to minimize the impact of WINS replication traffic on your network. Use the Help and Support Center on Windows Server 2003 to see examples of performance statistics in a high traffic environment to help you gauge your enterprise needs. Planning Network Traffic Management After you decide where to place your physical equipment, the users will begin accessing the services supplied by DHCP, DNS, and WINS. Other traffic comes from accessing the Internet, file sharing, and the many other network resources that will be used.You can estimate the amount of traffic at peak times by using some of the utilities provided with the operating system.The tools can be used to create baselines, identify the peak network usage areas, and identify the traffic sources. You will also need to monitor network traffic and analyze the usage.You might be able to iden- tify illicit network access from external sites, find Trojan horse viruses that generate broadcast storms, or just discover who is actually hogging all that Internet bandwidth.You can also determine whether your server-to-server traffic is managed well, or if it is necessary to modify the physical location of equipment. Monitoring Network Traffic and Network Devices Every network administrator should be familiar with two key utilities: I Network Monitor Allows you to capture data, identify the source, and analyze the con- tent and format of the message. I System Monitor Allows you to monitor other resources and determine the performance of those resources. Network Monitor should be run during low-usage times or for short intervals to minimize the impact on performance of capturing all that data on your machine. It is also useful to identify the type of traffic you are concerned with and use the filters to capture only the data you need. Using System Monitor System Monitor is a Microsoft Management Console (MMC) snap-in tool that allows you to use counters to monitor the performance of hardware, applications, and operating system components on Windows Server 2003 machines. Planning, Implementing, and Maintaining the TCP/IP Infrastructure • Chapter 21 757 System Monitor also allows you to view more than one log file at the same time, so you cancompare baseline logs with the current data.The Performance Logs and Alerts service can gatherdata and store it in a Microsoft SQL Server database that can be viewed by System Monitor.You canalso save portions of log files or SQL Server data to a new file.This can help save space, simplifycomparisons of data, and reduce analysis time.Determining Bandwidth RequirementsWhen you have captured performance statistics and viewed the network traffic during various timesof the day, you can identify the different sources of traffic on your network.You will need to analyzehow name resolution occurs, where the requests for name resolution initiate, and the server-to-server traffic when replicating the information. You will need to identify the following: I The slow connections and the quantity of data transmitted over those connections.This will help you to identify how often servers transmit replicated data to other servers. I The cost of one client obtaining information from these servers.You can then use that information to calculate the cost of many users. I Broadcast traffic, so that you can isolate that to certain networks.You will be able to iden- tify areas where clients communicate heavily with other clients, such as file servers, and locate those resources on the same segment as the heavy users.Optimizing Network PerformanceTCP traffic uses a sliding window method of transmitting data. As data is successful transmitted to thedestination, the window slides over the remaining data and transmits the next packets of data. Windowsize is basically the maximum number of packets that can be sent without waiting for positiveacknowledgment. If you transmit large amounts of TCP data, then larger TCP windows will improveTCP/IP performance.The maximum window size is limited to 64 kilobytes by default and is deter-mined by the windows size setting of the destination host machine. It is possible to increase the size ofthe TCP window dynamically on Windows Server 2003 to accommodate this by enabling large TCPwindow support. Client computers can be set to request large windows by editing their Registries.These are then called TCP1323Opts-enabled computers.The window size is negotiated during theTCP three-way handshake process.TCP1323 is a TCP extension defined in RFC 1323. With Windows Server 2003, it is possible to disable NetBIOS encapsulation over TCP/IP (disableNetBT).This can significantly reduce the overhead of data transfer and eliminate the need for WINSand any other NetBIOS name resolution. It will also reduce the browse master traffic.The dra ...