• Introduction
  • Support for Standard Features




    Download 0.8 Mb.
    bet2/161
    Sana21.03.2017
    Hajmi0.8 Mb.
    #1047
    1   2   3   4   5   6   7   8   9   ...   161

    Contents




    Contents 3

    Introduction 1

    Capabilities and Functionality 2

    Architectural Model 11

    The NDIS Interface and Below 14

    Core Protocol Stack Components and the TDI Interface 18

    Network Application Interfaces 47

    Critical Client Services and Stack Components 55

    Appendix A: TCP/IP Configuration Parameters 58

    Appendix B:


    NetBIOS over TCP/IP Configuration Parameters 85

    Appendix C:


    Windows Sockets and DNS Registry Parameters 96

    Appendix D: Tuning TCP/IP Response to Attack 106

    Appendix E: Format of the Daytime Service Response String 109

    Summary 110




    Introduction


    Microsoft has adopted TCP/IP as the strategic enterprise network transport for its platforms. In the early 1990s, Microsoft started an ambitious project to create a TCP/IP stack and services that would greatly improve the scalability of Microsoft networking. With the release of the Microsoft® Windows NT® 3.5 operating system, Microsoft introduced a completely rewritten TCP/IP stack. This new stack was designed to incorporate many of the advances in performance and ease of administration that were developed over the past decade. The stack was a high-performance implementation of the industry-standard TCP/IP protocol. It has evolved with each version of Windows based on the Windows NT code base to include new features and services that enhance performance, security, and reliability.

    The goals in designing the TCP/IP stack were to make it:



    • Standards-compliant and interoperable

    • Portable

    • Scalable and fast

    • Versatile

    • Self-tuning and easy to administer

    In this paper, the Windows Server 2003 TCP/IP protocol suite is examined from the bottom up. Throughout the paper, network traces are used to illustrate key concepts. These traces were gathered and formatted using Microsoft Network Monitor 2.0, a software-based protocol tracing and analysis tool included in the Microsoft Systems Management Server product. Windows 2000 Server and Windows Server 2003 include a limited functionality version of Network Monitor. The primary difference between this version and the Systems Management Server version is that the limited version can only capture frames that would normally be seen by the computer that it is installed on, rather than all frames that pass over the network (which requires the network interface card to be in promiscuous mode). It also does not support connecting to remote Network Monitor Agents.


    Download 0.8 Mb.
    1   2   3   4   5   6   7   8   9   ...   161




    Download 0.8 Mb.