throbber
Microsoft Windows NT Server
`
`TCPIIP
`
`Contents
`
`Welcome
`
`Chapter 1 Overview of Microsoft TCP/IP for Windows NT
`
`Chapter 2
`
`Installing and Configuring Microsoft TCP/IP and SNMP
`
`Chapter 3 Networking Concepts for TCP/IP
`
`Chapter 4
`
`Installing and Configuring DHCP Servers
`
`Chapter 5
`
`Installing and Configuring WINS Servers
`
`Chapter 6
`
`Setting Up LMHOSTS
`
`Chapter 7 Using the Microsoft FTP Server Service
`
`Chapter 8 Using Performance Monitor with TCP/IP Services
`
`Chapter 9
`
`Internetwork Printing with TCP/IP
`
`Chapter 10 Troubleshooting TCP/IP
`
`Chapter 11 Utilities Reference
`
`Appendix A MIB Object Types for Windows NT
`
`Appendix B Windows Sockets Applications
`
`Page 1 of 278
`
`LG Electronics Exhibit 1012
`
`

`

`Microsoft Windows NT Server
`
`TCPIIP
`
`Contents
`
`Welcome
`
`What's New in This Release
`
`How to Use This Manual
`
`Documentation Conventions
`
`Finding More Information
`
`Chapter 1 Overview of Microsoft TCP/IP for Windows NT
`
`Chapter 2
`
`Installing and Configuring Microsoft TCP/IP and SNMP
`
`Chapter 3 Networking Concepts for TCP/IP
`
`Chapter 4
`
`Installing and Configuring DHCP Servers
`
`Chapter 5
`
`Installing and Configuring WINS Servers
`
`Chapter 6
`
`Setting Up LMHOSTS
`
`Chapter 7 Using the Microsoft FTP Server Service
`
`Chapter 8 Using Performance Monitor with TCP/IP Services
`
`Chapter 9
`
`Internetwork Printing with TCP/IP
`
`Chapter 10 Troubleshooting TCP/IP
`
`Chapter 11 Utilities Reference
`
`Appendix A MIB Object Types for Windows NT
`
`Appendix B Windows Sockets Applications
`
`Page 2 of 278
`
`

`

`I Welcome
`Welcome
`
`1 of5
`
`Welcome to Microsofto TCP/IP for Windows NTrH.
`
`Transmission Control Protocol/Internet Protocol (TCP/IP) is a networking protocol that provides
`communication across interconnected networks. This manual, Microsoft Windows NT Server
`TCP/IP, describes how to install, configure. and troubleshoot Microsoft TCP/IP on a computer
`running the Microsoft Windows NT Workstation or Windows NT Server operating system. It
`also provides a reference for the TCP/IP utilities and information about how to install and use
`the other TCP/IP services such as the File Transfer Protocol (FTP) Server service, TCP/IP
`printing, and Simple Network Management Protocol (SN MP), plus the software to support new
`dynamic configuration and name resolution services.
`
`This manual assumes that you are familiar with the Microsoft Windows NT operating system. If
`you are not familiar with this product, refer to your Microsoft Windows NT documentation set.
`
`This introduction provides the following basic information:
`
`' What's new in this release
`
`' How to use this manual
`
`' Document conventions
`
`'
`
`Finding more information
`
`Page 3 of 278
`
`

`

`I Welcome
`
`What's New in This Release?
`
`20f5
`
`
`
`In this new version of Windows NT, TCP/IP capabilities have been expanded to include
`automatic TCP/IP configuration and powerful name resolution capabilities through the addition
`of new protocols and supporting administrative tools. New TCP/IP utilities plus the addition of
`performance counters for TCP/IP and related services will also help make administrative tasks
`easier. New elements include the following:
`
`Enhanced speed and performance
`
`Dynamic Host Configuration Protocol (DHCP)
`
`Microsoft TCP/IP supports automatic TCP/IP configuration through the new DHCP service.
`When DHCP servers are installed on the network, users can take advantage of dynamic IP
`address allocation and management.
`
`Windows Internet Name Service (WINS)
`
`Microsoft TCP/IP provides a powerful, new name resolution service for easy, centralized
`management of computer name-to-IP address resolution in medium and large
`internetworks.
`
`New TCP/IP utilities and commands
`
`This version includes a new Windows-based Telnet accessory for connecting to remote
`systems. The utilities provided with Microsoft TCP/IP have been expanded to include
`ipconfig for displaying current TCP/IP network configuration values, tracert for
`determining the route taken to a destination, lpq for showing print queue status for TCP/IP
`printing, and lpr for printing a file in TCP/IP printing.
`Performance counters
`
`You can use Performance Monitor to track performance of the IP protocols, FTP Server
`service traffic, and WINS servers. You can also use SNMP to monitor and manage WINS
`and DHCP servers.
`
`Multiple default gateways
`
`You can configure multiple default gateways for Windows NT computers. This ensures
`maximum reliability in networks that offer redundant routes.
`
`TCP/IP printing
`
`With TCP/IP printing installed on a single Windows NT computer on the network, other
`Windows networking computers can print to a direct-connect TCP/IP printer or a
`UNIXo-connected printer, without any special client software.
`
`Page 4 of 278
`
`

`

`I Welcome
`
`How to Use This Manual
`
`3of5
`
`
`
`This manual contains the following chapters and appendix:
`
`Chapter 1, "Overview of Microsoft TCP/IP for Windows NT"
`Describes the elements that make up Microsoft TCP/IP and provides an overview of how
`you can use Microsoft TCP/IP to support various networking solutions.
`
`Chapter 2, "Installing and Configuring Microsoft TCP/IP and SNMP"
`Describes the process for installing and configuring Microsoft TCP/IP, SN MP, and Remote
`Access Service (RAS) with TCP/IP on a computer running Windows NT.
`
`Chapter 3, "Networking Concepts for TCP/IP"
`Presents key TCP/IP networking concepts for network administrators interested in a
`technical discussion of the elements that make up Microsoft TCP/IP.
`
`Chapter 4, "Installing and Configuring DHCP Servers"
`Presents the procedures and strategies for setting up servers to support the Dynamic Host
`Configuration Protocol for Windows networks.
`
`Chapter 5, "Installing and Configuring WINS Servers"
`Presents the procedures and strategies for setting up Windows Internet Name Service
`servers.
`
`Chapter 6, "Setting Up LMHOSTS"
`Provides guidelines and tips for using LMHOSTS files for name resolution on networks.
`
`Chapter 7, "Using the Microsoft FTP Server Service"
`Describes how to install, configure, and administer the Microsoft FTP Server service.
`
`Chapter 8, "Using Performance Monitor with TCP/IP Services"
`Describes how to use the performance counters for TCP/IP, FTP Server service, DHCP
`servers, and WINS servers.
`
`Chapter 9, "Internetwork Printing and TCP/IP"
`Describes how to install TCP/IP printing and create TCP/IP printers on Windows NT
`computers with Microsoft TCP/lP.
`
`Chapter 10, "Troubleshooting TCP/IP"
`Describes how to troubleshoot lP connections and use the diagnostic utilities to get
`information that will help solve networking problems.
`
`Chapter 11, "Utilities Reference"
`Describes the TCP/IP utilities and provides syntax and notes.
`
`Appendix A, "LAN Manager MIB II for Windows NT Objects"
`Describes the LAN Manager MIB Il objects provided when you install SNMP with
`Windows NT.
`
`Appendix B, "Windows Sockets Application Vendors"
`Lists third-party vendors who have created software based on the Windows Sockets
`standard to provide utilities and applications that run in heterogeneous networks that use
`TCP/lP. This appendix also lists Internet sources for public-domain software based on
`Windows Sockets.
`
`The Glossary provides definitions of TCP/IP and networking technical terms used in this
`manual.
`
`You can get online Help by pressing F1 in all dialog boxes for installing and configuring TCP/lP
`and related components. You can also get online Help about the Microsoft TCP/IP networking
`solutions and for the TCP/IP utilities.
`
`Page 5 of 278
`
`

`

`i To get help on Microsoft TCPIIP networking solutions
`
`'
`
`In File Manager, double-click TCPIP.HLP in \systemrootlSYSTEM32 (this could be
`C:\W|NNT35\SYSTEM32, or wherever you installed the Windows NT system files).
`
`> To get help on TCPIIP utilities
`
`'
`
`At the command prompt, type a TCP/IP command name followed by the -? switch. For
`example, type ping -? and press Enter to get help on the ping command.
`
`Or
`
`1.|n the Program Manager Main group, double-click the Windows NT Help icon.
`
`2.|n the Windows NT Help window, click the Command Reference Help button.
`
`3.|n the Commands window, click a command name.
`
`Or
`
`In the Command Reference window, choose the Search button, and then type a command
`name in the box or select a command name from the list.
`
`Page 6 of 278
`
`

`

`I Welcome
`
`4of5
`
`Documentation Conventions
`
`This manual uses several type styles and special characters, described in the following list:
`
`Convention
`
`Use
`
`Represents commands, command options, and file entries. Type bold
`words exactly as they appear (for example, net use).
`
`Introduces new terms and represents variables. For example, the variable
`computer name indicates that you type the name of a workstation or a
`server.
`
`Represents filenames and paths. (You can, however, type such entries in
`uppercase or lowercase letters, or a combination of the two.)
`
`Represents keyboard names (for example, CTRL, ENTER, and F2).
`
`Encloses optional items in syntax statements. For example, [password]
`indicates that you can choose to type a password with the command. Type
`only the information within the brackets, not the brackets themselves.
`
`Indicates a command element may be repeated.
`
`Indicates a procedure.
`
`Refers to operating system and networking functionality that is available in
`both Windows NT Sewer and Windows NT Workstation.
`
`Refers to the Windows NT system tree. This can be \WINNT, \WINNT35,
`\WINDOWS, or whatever other directory name you specified when
`installing Windows NT.
`
`bold
`
`italic
`
`ALL UPPERCASE
`
`SMALL CAPITALS
`
`[brackets]
`
`...(ellipsis)
`
`> W
`
`indows NT
`
`\W I N NT or
`
`\systemroot
`
`Page 7 of 278
`
`

`

`Welcome
`
`
`5 of 5
`
`Finding More Information
`
`In addition to the standard ways for receiving technical support from Microsoft (as described in
`the Windows NT Server Installation Guide), you can get support for Windows NT via the
`Internet.
`
`
`Note
`Your computer must be connected to the Internet to take advantage of this service.
`
`} To get Windows NT support via the Internet
`
`'
`
`Start ftp and connect to ftp.microsoft.com
`
`This support service uses anonymous FTP under Windows NT to provide documentation,
`utilities, updated drivers, and other information for many Microsoft systems products.
`
`For a more technical discussion of the topics mentioned in this manual, refer to the following
`texts and articles:
`
`Allard, J. "DHCP-TCP/IP Network Configuration Made Easy," ConneXions, Volume 7, No. 8,
`August 1993.
`
`Allard, J., K. Moore, and D. Treadwell. "Plug into Serious Network Programming with the Windows
`Sockets API," Microsoft Systems Journal, July: 35 40, 1993.
`
`Comer, D. Internetworking with TCP/IP Volume 1: Principles, Protocols, and Architecture. Second
`edition. Englewood Cliffs, NJ: Prentice Hall, 1991.
`
`Comer, D. and D. Stevens. lntemetworlring with TCP/IP Volume II: Design, Implementation, and
`Internals. Englewood Cliffs, NJ: Prentice Hall, 1991.
`
`Comer, D. and D. Stevens. lntemetworlring with TCP/IP Volume Ill: Client-Server Programming and
`Applications. Englewood Cliffs, NJ: Prentice Hall, 1991.
`
`Hall, M., et al. Windows Sockets: An Open Interface for Network Programming Under Microsoft
`Vlfindows, Version 1.1, Revision A, 1993.
`
`Krol, E. The Whole lntemet Users Guide and Catalog. Sebastopol, CA: O'Reilly and Associates,
`1992.
`
`Rose, MT. The Simple Book. Englewood Cliffs, NJ: Prentice Hall, 1991.
`
`Page 8 of 278
`
`

`

`n Chapt_er 1_
`Overview of Microsoft TCP/IP for
`
`10$
`
`Windows NT
`
`Transmission Control Protocol/Internet Protocol (TCP/IP) is a networking protocol that provides
`communication across interconnected networks made up of computers with diverse hardware
`architectures and various operating systems. TCP/IP can be used to communicate with
`Windows NT systems, with devices that use other Microsoft networking products, and with
`non-Microsoft systems, such as UNIX.
`
`This chapter introduces Microsoft TCP/IP for Windows NT. The topics in this chapter include
`the following:
`
`' What is TCP/IP for Windows NT?
`
`' What does Microsoft TCP/IP include?
`
`' Windows NT solutions in TCP/IP internetworks
`
`For more detailed information on TCP/IP and its integration with Microsoft Windows NT and
`other networking products, see Chapter 3, "Networking Concepts for TCP/IP."
`
`Page 9 of 278
`
`

`

`n Overview of Microsoft TCPIIP for Windows NT
`
`2 of8
`
`
`
`What Is TCPIIP for Windows NT?
`
`The TCPIIP protocol family is a standard set of networking protocols, or rules, that govern how
`data is passed between computers on a network. TCPIIP is used to connect the Internet, the
`worldwide internetwork connecting over two million universities, research labs, U.S. defense
`installations, and corporations. (By convention, "Internet" is capitalized when referring to the
`worldwide internetwork.) These same protocols can be used in private internetworks that
`connect several local area networks.
`
`Microsoft TCP/lP for Windows NT enables enterprise networking and connectivity on
`Windows NT computers. Adding TCP/lP to a Windows NT configuration offers the following
`advantages:
`
`'
`
`'
`
`'
`
`'
`
`A standard, routable enterprise networking protocol that is the most complete and
`accepted protocol available. All modern operating systems offer TCP/lP support, and most
`large networks rely on TCP/lP for much of their network traffic.
`
`A technology for connecting dissimilar systems. Many standard connectivity utilities are
`available to access and transfer data between dissimilar systems, including File Transfer
`Protocol (FTP) and Terminal Emulation Protocol (Telnet). Several of these standard
`utilities are included with Windows NT.
`
`A robust, scalable, cross-platform client-server framework. Microsoft TCP/lP supports the
`Windows Sockets 1.1 interface, which is ideal for developing client-server applications that
`can run with Windows Sockets-com pliant stacks from other vendors. Many public-domain
`Internet tools are also written to the Windows Sockets standard. Windows Sockets
`
`applications can also take advantage of other networking protocols such as Microsoft
`NWLink, the Microsoft implementation of the IPX/SPX protocols used in Novell® NetWare®
`networks.
`
`The enabling technology necessary to connect Windows NT to the global Internet. TCP/lP,
`Point to Point Protocol (PPP), and Windows Sockets 1.1 provide the foundation needed to
`connect and use Internet services.
`
`Page 10 of 278
`
`

`

`n Overview of Microsoft TCPIIP for Windows NT
`
`3 of8
`
`
`
`What Does Microsoft TCPIIP Include?
`
`Microsoft TCPIIP provides all the elements necessaryto implement these protocols for
`networking. Microsoft TCP/IP includes the following:
`
`Core TCP/IP protocols, including the Transmission Control Protocol (TCP), Internet
`Protocol (IP), User Datagram Protocol (UDP), Address Resolution Protocol (ARP), and
`Internet Control Message Protocol (ICMP). This suite of Internet protocols provides a set of
`standards for how computers communicate and how networks are interconnected. Support
`is also provided for PPP and Serial-Line IP (SLIP), which are protocols used for dial-up
`access to TCP/IP networks, including the Internet.
`
`Support for application interfaces, including Windows Sockets 1.1 for network
`programming, remote procedure call (RPC) for communicating between systems, NetBIOS
`for establishing logical names and sessions on the network, and network dynamic data
`exchange (Network DDE) for sharing information embedded in documents across the
`network.
`
`Basic TCP/IP connectivity utilities, including finger, ftp, lpr, rcp, rexec, rsh, telnet, and
`tftp. These utilities allow Windows NT users to interact with and use resources on
`non-Microsoft hosts, such as UNIX workstations.
`
`TCP/IP diagnostic tools, including arp, hostname, ipconfig, Ipq, nbtstat, netstat, ping,
`route, and tracert. These utilities can be used to detect and resolve TCPIIP networking
`problems.
`
`Services and related administrative tools, including the FTP Server service for transferring
`files between remote computers, Windows Internet Name Service (WINS) for dynamically
`registering and querying computer names on an internetwork, Dynamic Host Configuration
`Protocol (DHCP) service for automatically configuring TCP/IP on Windows NT computers,
`and TCP/IP printing for accessing printers connected to a UNIX computer or connected
`directly to the network via TCPIIP.
`
`Simple Network Management Protocol (SN MP) agent. This component allows a
`Windows NT computer to be administered remotely using management tools such as Sun®
`Net Manager or HP® Open \fiew. SNMP can also be use to monitor and manage DHCP
`servers and WINS servers.
`
`The client software for simple network protocols, including Character Generator, Daytime,
`Discard, Echo, and Quote of the Day. These protocols allow a Windows NT computer to
`respond to requests from other systems that support these protocols. When these
`protocols are installed, a sample QUOTES files is also installed in the lsystemrootl
`SYSTEM32\DRIVERS\ETC directory.
`
`Path MTU Discovery, which provides the ability to determine the datagram size for all
`routers between Windows NT computers and any other systems on the WAN. Microsoft
`TCP/IP also supports the Internet Gateway Multicast Protocol (IGMP), which is used by
`new workgroup software products.
`
`The following diagram shows the elements of Microsoft TCPIIP alongside the variety of
`additional applications and connectivity utilities provided by Microsoft and other developers.
`
`Page 11 of 278
`
`

`

`
`
`
`
`
`
`
`De \al opment tool a
`mun. oucmecl
`nl‘amed
`
`connectivity
`
`auliaaliona
`
`
`—E
`
`Integrated with
`Windows NT
`
`D Developed by third pa'tiee or the research
`commnity
`
`Microsoft TCPIIP: Core Technology and Third-Party Add-one
`
`TCP/IP standards are defined in Requests for Comments (RFCs), which are published by the
`Internet Engineering Task Force (IETF) and other working groups. The relevant RFCs
`supported in this version of Microsoft TCP/IP (and for Microsoft Remote Access Service) are
`described in the following table.
`
`Requests for Comments (RFCs) Supported by Microsoft TCPIIP
`RFC
`Title
`
`768
`
`783
`
`791
`
`792
`
`793
`
`826
`
`854
`
`862
`
`863
`
`864
`
`865
`
`867
`894
`
`User Datagram Protocol (UDP)
`
`Trivial File Transfer Protocol (TFTP)
`
`Internet Protocol (IP)
`
`Internet Control Message Protocol (ICMP)
`
`Transmission Control Protocol (TOP)
`
`Address Resolution Protocol (ARP)
`
`Telnet Protocol (TELNET)
`
`Echo Protocol (ECHO)
`
`Discard Protocol (DISCARD)
`
`Character Generator Protocol (CHARGEN)
`
`Quote of the Day Protocol (QUOTE)
`
`Daytime Protocol (DAYTIME)
`IP over Ethernet
`
`919, 922
`
`IP Broadcast Datagrams (broadcasting with subnets)
`
`959
`
`File Transfer Protocol (FTP)
`
`Page 12 of 278
`
`

`

`1001, 1002
`
`NetBIOS Service Protocols
`
`1034, 1035
`
`Domain Name System (DOMAIN)
`
`1042
`
`1055
`
`1112
`
`[P over Token Ring
`
`Transmission of IP over Serial Lines (lP-SLIP)
`
`Intemet Gateway Multicast Protocol (IGMP)
`
`1122, 1123
`
`Host Requirements (communications and applications)
`
`1134
`
`1144
`
`1157
`1179
`
`1188
`
`1191
`1201
`
`1231
`
`1332
`1334
`
`1533
`
`1534
`
`1541
`
`1542
`
`1547
`
`1548
`
`1549
`
`1552
`
`1553
`
`1570
`
`Point to Point Protocol (PPP)
`
`Compressing TCPIIP Headers for Low-Speed Serial Links
`
`Simple Network Management Protocol (SNMP)
`Line Printer Daemon Protocol
`
`IP over FDDI
`
`Path MTU Discovery
`IP over ARCNET
`
`IEEE 802.5 Token Ring MIB (MIB-ll)
`
`PPP Internet Protocol Control Protocol (IPCP)
`PPP Authentication Protocols
`
`DHCP Options and BOOTP Vendor Extensions
`
`lnteroperation Between DHCP and BOOTP
`
`Dynamic Host Configuration Protocol (DHCP)
`
`Clarifications and Extensions for the Bootstrap Protocol
`
`Requirements for Point to Point Protocol (PPP)
`
`Point to Point Protocol (PPP)
`
`PPP in High-level Data Link Control (HDLC) Framing
`
`PPP Internetwork Packet Exchange Control Protocol (IPXCP)
`
`IPX Header Compression
`
`Link Control Protocol (LCP) Extensions
`
`Draft RFCs
`
`NetBIOS Frame Control Protocol (NBFCP); PPP over ISDN; PPP over X.25;
`Compression Control Protocol
`
`All RFCs can be found on the Internet via ds.internic.net.
`
`In this version of Windows NT, Microsoft TCP/IP does not include a complete suite of TCP/IP
`connectivity utilities, Network File System (NFS) support, or some TCP/IP server services
`(daemons) such as routed and telnetd. Many such applications and utilities that are available
`in the public domain or from third-party vendors work with Microsoft TCP/IP.
`
`Tip
`For Windows for Workgroups computers and MS-DOSbased computers on a Microsoft
`network, you can install the new version of Microsoft TCP/IP-32 for Windows for Workgroups
`and the Microsoft Network Client version 2.0 for MS-DOS from the Windows NT Server 3.5
`
`compact disc. This software includes the DHCP and WINS clients and other elements of the
`new Microsoft TCP/IP software. For information about installing these clients, see Chapter 9,
`"Network Client Administrator," in the Windows NT Server Installation Guide.
`
`Page 13 of 278
`
`

`

`
`
`Page 14 of 278
`
`

`

`n Overview of Microsoft TCPIIP for Windows NT
`
`4 of8
`
`Windows NT Solutions in TCPIIP Internetworks
`
`When TCPIIP is used as a transport protocol with Windows NT, Windows NT computers can
`communicate with other kinds of systems without additional networking software. Microsoft
`TCP/IP in combination with other parts of Windows NT provides a scalable solution for
`enterprise networks that include a mix of system types and software on many platforms.
`
`This section summarizes how TCP/IP works with Windows NT to provide enterprise networking
`solutions. For information about how the elements discussed in this section fit within the
`
`networking architecture, see "TCP/IP and Windows NT Networking" in Chapter 3, "Networking
`Concepts for TCPIIP."
`
`Page 15 of 278
`
`

`

`n Overview of Microsoft TCPIIP for Windows NT
`
`5 of8
`
`
`
`Windows NT Solutions in TCPIIP Internetworks
`
`Using TCPIIP for Scalability in Windows Networks
`
`TCPIIP delivers a scalable internetworking technology widely supported by hardware and
`software vendors.
`
`When TCPIIP is used as the enterprise networking protocol, the Windows networking solutions
`from Microsoft can be used on an existing internetwork to provide client and server support for
`TCPIIP and connectivity utilities. These solutions include:
`
`' Microsoft Windows NT Workstation 3.5, with enhancements to support wide area networks
`(WAN), TCPIIP printing, extended LMHOSTS, Windows Sockets 1.1, FTP Server service
`software, and DHCP and WINS client software.
`
`' Microsoft Windows NT Server 3.5, with the same enhancements as Windows NT, plus
`DHCP server and WINS server software to support the implementation of these new
`protocols.
`
`' Microsoft TCPIIP-32 for Windows for Workgroups 3.11, with Windows Sockets support,
`can be used to provide access for Windows for Workgroups computers to Windows NT,
`LAN Manager, and other TCPIIP systems. Microsoft TCPIIP-32 includes DHCP and WINS
`client software.
`
`' Microsoft LAN Manager, including both client and server support for Windows Sockets,
`and MS-DOS®based connectivity utilities. The Microsoft Network Client 2.0 software on the
`Windows NT Server compact disc includes new Microsoft TCPIIP support with DHCP and
`WINS clients.
`
`The current version of TCPIIP for Windows NT also supports IP routing in systems with
`multiple network adapters attached to separate physical networks (multihomed systems).
`
`To other
`
`networks
`
`
`Page 16 of 278
`
`

`

`n Overview of Microsoft TCPIIP for Windows NT
`
`6 of8
`
`
`
`Windows NT Solutions in TCPIIP Internetworks
`
`Using TCPIIP for Connectivity to the Internet
`
`Microsoft TCPIIP provides Windows networking with a set of internetworking protocols based
`on open standards.
`
`Microsoft TCPIIP for Windows NT includes many common connectivity applications such as
`ftp, rsh, and telnet that support file transfer, remote process execution, and terminal emulation
`for communication on the Internet and between non-Microsoft network systems.
`
`TCPIIP applications created by researchers and other users, such as Gopher and NCSA
`Mosaic, are in the public domain or are available through other vendors as both 16-bit and
`32-bit Windows-based applications. Any of these applications that follow the Windows Sockets
`1.1 standard are compatible with Windows NT. Such applications allow a Windows NT
`computer to act as a powerful Internet client using the extensive internetworking components
`with public-domain viewers and applications to access Internet resources.
`
`NCSA Mosaic for MS Windows
`
`Eile Edit
`
`thions
`
`flavigate Annotate
`
`Starting Points
`
`flood Kill
`
`simple model was intended to simulate medimn-scale atmospheric convection.
`
`EMiscellaneous Internet Resources on the [1.3. Congressflig
`Main USE
`SCienCEPFESEH Qommands
`thions Bookmarks
`flelp
`Researchers
`i:
`Hobil], David; ii g
`Visualization
`a Electronic Mail Addresses for Members of Congress
`YUSL Jeffery; I
`[5!" Government Manuel: Legislative Branch (UMich)
`Other ”cancers
`fif- List of Firsts for 103rd Congress (UMd)
`_1‘
`-"______,
`_,
`___,_
`__'
`
`The Lorenz Attractor is a solution to a set of differential equations which displays some rather
`remarkable behavior and represents one of the landmarks in the field of Chaos. The equations
`describe the 2D flow of fluid in a simple rectangular box which is heated along the bottom. This
`
`
`
`Tip
`Public-domain Windows-based utilities such as LPR and Gopher can be obtained on the
`Internet via ftp.cica.indiana.edu in the Ipub/win3/nt or lpub/win3/winsock directory, or via the
`same directories on ftp.cdrom.com.
`
`Page 17 of 278
`
`

`

`n Overview of Microsoft TCPIIP for Windows NT
`
`7 of8
`
`
`
`Windows NT Solutions in TCPIIP Internetworks
`
`TCPIIP for Heterogeneous Networking
`
`Because most modern operating systems (in addition to Windows NT) support TCPIIP
`protocols, an internetwork with mixed system types can share information using simple
`networking applications and utilities. With TCPIIP as a connectivity protocol, Windows NT can
`communicate with many non-Microsoft systems, including:
`'
`Internet hosts
`
`' Apples Macintosho systems
`'
`IBM® mainframes
`
`'
`
`UNIX systems
`
`' Open VMS® systems
`
`'
`
`Printers with network adapters connected directly to the network
`
`LAl-l
`Manager
`
`
`
`
`LAN lute-lager
`for UNIX host
`
`Windowa HT
`
`
`
`including RAS
`“mm” TCPI'F'
`/Windows for
`
`
`Workgroups
`
`Patl'imrka for VM
`
`Microsoft TCPIIP Connectivity
`
`Microsoft TCPIIP provides a framework for interoperable heterogeneous networking. The
`modular architecture of Windows NT networking with its transport-independent services
`contributes to the strength of this framework. For example, Windows NT supports these
`transport protocols, among many others:
`
`'
`
`'
`
`lPX/SPX for use in NetWare environments, using the Microsoft NWLink transport. Besides
`providing interoperability with NetWare networks, lPX/SPX is a fast LAN transport for
`Windows networking as well.
`
`TCPIIP for internetworks based on IP technologies. TCPIIP is the preferred transport for
`internetworks and provides interoperability with UNIX and other TCPIIP-based networks.
`
`' NetBEUl as the protocol for local area networking on smaller networks and compatibility
`with existing LAN Manager and Lan Server networks.
`
`' AppleTa|k® for connecting to and sharing resources with Macintosh systems.
`
`Other transport protocols provided by third-party vendors, such as DECnetw and OSI, can also
`be used by Windows NT networking services.
`
`Windows NT provides standard network programming interfaces through the Windows
`Sockets, RFC, and NetBlOS interfaces. Developers can take advantage of this heterogeneous
`
`Page 18 of 278
`
`

`

`client-server platform to create custom applications that will run on any system in the
`enterprise. An example of such a service is Microsoft SQL Server, which uses Windows
`Sockets 1.1 to provide access to NetWare, MS-DOSbased, Windows NT, and UNIX clients.
`
`Page 19 of 278
`
`

`

`n Overview of Microsoft TCPIIP for Windows NT
`
`3 of8
`
`
`
`Windows NT Solutions in TCPIIP Internetworks
`
`Using TCPIIP with Third-Party Software
`
`TCP/IP is a common denominator for heterogeneous networking, and Windows Sockets is a
`standard used by application developers. Together they provide a framework for cross-platform
`client-server development. TCPIIP-aware applications from vendors that comply with the
`Windows Sockets standards can run over virtually any TCP/IP implementation.
`
`The Windows Sockets standard ensures compatibility with Windows-based TCP/lP utilities
`developed by more than 30 vendors. This includes third-party applications for the X Window
`System, sophisticated terminal emulation software, NFS, electronic mail packages, and more.
`Because Windows NT offers compatibility with 16-bit Windows Sockets, applications created
`for Windows 3.x Windows Sockets will run over Windows NT without modification or
`
`recompilation.
`
`For example, third-party applications for X Window provide strong connectivity solutions by
`means of X Window sewers, database servers, and terminal emulation. With such
`applications, a Windows NT computer can work as an X Window server platform while
`retaining compatibility with applications created for Windows NT, Windows 3.1, and MS-DOS
`on the same system. Other third-party software includes X Window client libraries for
`Windows NT, which allow developers to write X Window client applications on Windows NT
`that can be run and displayed remotely on X Window server systems.
`
`The Windows Sockets API is a networking APl used by programmers creating applications for
`both the Microsoft Windows NT and Windows operating systems. Windows Sockets is an open
`standard that is part of the Microsoft Windows Open System Architecture (WOSA) initiative. It
`is a public specification based on Berkeley UNIX sockets, which means that UNIX applications
`can be quickly ported to Microsoft Windows and Windows NT. Windows Sockets provides a
`single standard programming interface supported by all the major vendors implementing
`TCP/IP for Windows systems.
`
`The Windows NT TCP/lP utilities use Windows Sockets, as do 32-bit TCP/IP applications
`developed by third parties. Windows NT also uses the Windows Sockets interface to support
`Services for Macintosh and lPX/SPX in NWLink. Under Windows NT, 16-bit Windows-based
`applications created under the Windows Sockets standard will run without modification or
`recompilation. Most TCP/IP users will use programs that comply with the Windows Sockets
`standard, such as ftp or telnet or third-party applications.
`
`The Windows Sockets standard allows a developer to create an application with a single
`common interface and a single executable that can run over many of the TCP/IP
`implementations provided by vendors. The goals for Windows Sockets are the following:
`
`'
`
`Provide a familiar networking API to programmers using Windows NT, Windows for
`Workgroups, or UNIX
`
`' Offer binary compatibility between vendors for heterogeneous Windows-based TCP/lP
`stacks and utilities
`
`'
`
`Support both connection-oriented and connectionless protocols
`
`Typical Windows Sockets applications include graphic connectivity utilities, terminal emulation
`software, Simple Mail Transfer Protocol (SMTP) and electronic mail clients, network printing
`utilities, SQL client applications, and corporate client-server applications.
`
`If you are interested in developing a Windows Sockets application, specifications for Windows
`Sockets are available on the Internet from ftp.microsoft.com, on CompuServeo in the MSL
`
`Page 20 of 278
`
`

`

`library, and in the Microsoft Win32® Software Developers Kit.
`
`’ To get a copy of the Windows Sockets specification via anonymous FTP
`
`1.
`
`9P?!”
`
`.0)
`
`Make sure you have write permission in your current working directory.
`
`Start ftp and connect to ftp.microsoft.com (or 198.105.232.1).
`
`Log on as anonymous.
`
`Type your electronic mail address for the password.
`
`Type cd \advsys\winsock\spec11 and press ENTER.
`
`Use the dir command to see the list of available file types. If you want binary data such as
`in the Microsoft Word version, type bin and press ENTER.
`
`Determine the file with the format you want [for example, ASCII (.TXT), PostScript® (.PS),
`or Microsoft Word (.DOC)], and then type get winsock.ext where ext is the format that you
`want, such as winsock.doc for the Microsoft Word version.
`
`} To get a copy of the Windows Sockets specification from CompuServe
`
`1.
`
`2.
`
`3.
`
`Type go msl and press ENTER.
`
`Browse using the keywords windows sockets.
`
`Choose the file with the format you want [ASCII (.TXT), PostScript (.PS), or Microsoft Word
`for Windows (.DOC)], and then type get winsock.ext.
`
`There is also an electronic mailing list designed for discussion of Windows Sockets
`programming.
`
`’ To subscribe to the Windows Sockets mailing list
`
`Send electronic mail to listserv@sunsite.unc.edu with a message body that contains
`subscribe winsock user's-email—address.
`
`You can use the same procedure to subscribe to two mailing lists called winsock-hackers
`and winsock-users.
`
`Page 21 of 278
`
`

`

`Bffii
`I Chapt_er g
`Installing and Configuring Microsoft
`TCP/IP and SNMP
`
`This

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket