Microsoft Windows NT Server
`TCP/IP
`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
`
`Samsung - Exhibit 1012 - Page 1
`
`

`

`Microsoft Windows NT Server
`TCP/IP
`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
`
`Samsung - Exhibit 1012 - Page 2
`
`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`Microsoft TCP/IP: Core Technology and Third-Party Add-ons
`
`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 TCP/IP
`RFC
`Title
`768
`User Datagram Protocol (UDP)
`783
`Trivial File Transfer Protocol (TFTP)
`791
`Internet Protocol (IP)
`792
`Internet Control Message Protocol (ICMP)
`793
`Transmission Control Protocol (TCP)
`826
`Address Resolution Protocol (ARP)
`854
`Telnet Protocol (TELNET)
`862
`Echo Protocol (ECHO)
`863
`Discard Protocol (DISCARD)
`864
`Character Generator Protocol (CHARGEN)
`865
`Quote of the Day Protocol (QUOTE)
`867
`Daytime Protocol (DAYTIME)
`894
`IP over Ethernet
`919, 922
`IP Broadcast Datagrams (broadcasting with subnets)
`959
`File Transfer Protocol (FTP)
`
`Samsung - Exhibit 1012 - Page 12
`
`

`

`1001, 1002
`1034, 1035
`1042
`1055
`1112
`1122, 1123
`1134
`1144
`1157
`1179
`1188
`1191
`1201
`1231
`1332
`1334
`1533
`1534
`1541
`1542
`1547
`1548
`1549
`1552
`1553
`1570
`Draft RFCs
`
`NetBIOS Service Protocols
`Domain Name System (DOMAIN)
`IP over Token Ring
`Transmission of IP over Serial Lines (IP-SLIP)
`Internet Gateway Multicast Protocol (IGMP)
`Host Requirements (communications and applications)
`Point to Point Protocol (PPP)
`Compressing TCP/IP 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-II)
`PPP Internet Protocol Control Protocol (IPCP)
`PPP Authentication Protocols
`DHCP Options and BOOTP Vendor Extensions
`Interoperation 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
`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.
`
`Samsung - Exhibit 1012 - Page 13
`
`

`

`
`
`Samsung - Exhibit 1012 - Page 14
`
`Samsung - Exhibit 1012 - Page 14
`
`

`

`

`

`

`

`

`

`

`

`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.
`
`Samsung - Exhibit 1012 - Page 19
`
`

`

`

`

`library, and in the Microsoft Win32® Software Developers Kit.
`
`

`

`

`

`

`

`

`

`configuration procedures described in "Configuring TCP/IP Manually" later in this chapter.
`TCP/IP must be configured in order to operate.
`
`Connectivity Utilities
`
`SNMP Service
`
`TCP/IP Network Printing
`Support
`
`FTP Server Service
`
`If you checked the DHCP Server Service or WINS Server Service options, you must
`complete the configuration steps described in Chapters 4 and 5.
`Windows NT TCP/IP Installation Options
`Option
`Usage
`TCP/IP Internetworking
`Includes the TCP/IP protocol, NetBIOS over TCP/IP and Windows
`Sockets interfaces, and the TCP/IP diagnostic utilities. These
`elements are installed automatically.
`Installs the TCP/IP utilities. Select this option to install the
`connectivity utilities described in Chapter 11, "Utilities Reference."
`Installs the SNMP service. Select this option to allow this computer
`to be administered remotely using management tools such as Sun
`Net Manager or HP Open View. This option also allows you to
`monitor statistics for the TCP/IP services and WINS servers using
`Performance Monitor, as described in Chapter 8, "Using
`Performance Monitor with TCP/IP Services."
`Allows this computer to print directly over the network using
`TCP/IP. Select this option if you want to print to UNIX print queues
`or TCP/IP printers that are connected directly to the network, as
`described in Chapter 9, "Internetwork Printing with TCP/IP."
`This option must be installed if you want to use the Lpdsvr service
`so that UNIX computers can print to Windows NT printers.
`Allows files on this computer to be shared over the network with
`remote computers that support FTP and TCP/IP (especially
`non-Microsoft network computers). Select this option if you want to
`use TCP/IP to share files with other computers, as described in
`Chapter 7, "Using the Microsoft FTP Server Service."
`Provides the client software for the Character Generator, Daytime,
`Discard, Echo, and Quote of the Day services. Select this option to
`allow this computer to respond to requests from other systems that
`support these protocols.
`Installs the server software to support automatic configuration and
`addressing for computers using TCP/IP on your internetwork. This
`option is available only for Windows NT Server. Select this option
`if this computer is to be a DHCP Server, as described in Chapter
`4, "Installing and Configuring DHCP Servers."
`If you select this option, you must manually configure the IP
`address, subnet mask, and default gateway for this computer.
`Installs the server software to support WINS, a dynamic name
`resolution service for computers on a Windows internetwork. This
`option is available only for Windows NT Server. Select this option
`if this computer is to be installed as a primary or secondary WINS
`server, as described in Chapter 5, "Installing and Configuring
`WINS Servers."
`Do not select this option if this computer will be a WINS proxy
`agent.
`Turns on automatic configuration of TCP/IP parameters for this
`computer. Select this option if there is a DHCP server on your
`internetwork to support dynamic host configuration. This is the
`preferred method for configuring TCP/IP on most Windows NT
`computers.
`This option is not available if the DHCP Server Service or WINS
`Server Service option is selected.
`
`Enable Automatic DHCP
`Configuration
`
`Simple TCP/IP Services
`
`DHCP Server Service
`
`WINS Server Service
`
`Samsung - Exhibit 1012 - Page 25
`
`

`

`If you have trouble installing Microsoft TCP/IP on your computer, follow the suggestions in the
`error messages. You can also use diagnostic utilities such as ping to isolate network hardware
`problems and incompatible configurations. For information, see Chapter 10, "Troubleshooting
`TCP/IP."
`
`After TCP/IP is installed, the \systemroot\SYSTEM32\DRIVERS\ETC directory contains several
`files, including default HOSTS, NETWORKS, PROTOCOLS, QUOTES, and SERVICES files
`plus a sample LMHOSTS.SAM file that describes the format for this file.
`
`Samsung - Exhibit 1012 - Page 26
`
`

`

`

`

`

`

`

`

`2.
`
`In the Adapter list of the TCP/IP Configuration dialog box, select the network adapter for
`which you want to set IP addresses.
`
`The Adapter list contains all network adapters to which IP is bound on this computer. This
`list includes all adapters installed on this computer.
`
`You must set specific IP addressing information for each bound adapter with correct
`values provided by the network administrator. The bindings for a network adapter
`
`Samsung - Exhibit 1012 - Page 30
`
`

`

`determine how network protocols and other layers of network software work together.
`
`3. For each bound network adapter, type values in the IP Address and Subnet Mask boxes.
`
`

`

`5.
`
`If there are WINS servers installed on your network and you want to use WINS in
`combination with broadcast name queries to resolve computer names, type IP addresses
`in the boxes for the primary and, optionally, the secondary WINS servers. The network
`administrator should provide the correct values for these parameters. These are global
`values for the computer, not just individual adapters.
`
`If an address for a WINS server is not specified, this computer will use name query
`broadcasts (the b-node mode for NetBIOS over TCP/IP) plus the local LMHOSTS file to
`resolve computer names to IP addresses. Broadcast resolution is limited to the local
`network.
`
`Note
`WINS name resolution is enabled and configured automatically for a computer that is
`configured with DHCP.
`On a WINS server, NetBIOS over TCP/IP (NETBT.SYS) uses WINS on the local computer
`as the primary name server, regardless of how name resolution may be configured. Also,
`NetBIOS over TCP/IP binds to the first IP address on a network adapter and ignores any
`additional addresses.
`
`6.
`
`7.
`
`8.
`
`For overview information about name resolution options, see "Name Resolution for
`Windows Networking" in Chapter 3. For detailed information about installing and
`configuring WINS servers, see Chapter 5.
`
`If you want to configure the advanced TCP/IP options for multiple gateways and other
`items, choose the Advanced button, and continue with the configuration procedure, as
`described in "Configuring Advanced TCP/IP Options" later in this chapter.
`
`If you want to use DNS for host name resolution, choose the DNS button, and continue
`with the configuration procedure, as described in the next section.
`
`If you do not want to configure DNS or advanced options, or if you have completed the
`other configuration procedures, choose the OK button. When the Network Settings dialog
`box reappears, choose the OK button.
`
`Microsoft TCP/IP has been configured. If you are installing TCP/IP for the first time, you
`
`Samsung - Exhibit 1012 - Page 32
`
`

`

`must restart the computer for the configuration to take effect. If you are changing your
`existing configuration, you do not have to restart your computer.
`After TCP/IP is installed, the \systemroot\SYSTEM32\DRIVERS\ETC directory contains a
`default HOSTS file and a sample LMHOSTS.SAM file. The network administrator may require
`that replacement HOSTS and LMHOSTS files be used instead of these default files.
`
`Samsung - Exhibit 1012 - Page 33
`
`

`

`

`

`3.
`
`In the DNS Configuration dialog box, you can, optionally, type a name in the Host Name
`box (usually your computer name).
`
`The name can be any combination of AZ letters, 09 numerals, and the hyphen (-) plus the
`period (.) character used as a separator. By default, this value is the Windows NT
`computer name, but the network administrator can assign another host name without
`affecting the computer name.
`
`Note
`Some characters that can be used in Windows NT computer names, particularly the
`underscore, cannot be used in host names.
`
`The host name is used to identify the local computer by name for authentication by some
`utilities. Other TCP/IP-based utilities, such as rexec, can use this value to learn the name
`of the local computer. Host names are stored on DNS servers in a table that maps names
`to IP addresses for use by DNS.
`
`4. Optionally, type a name in the Domain Name box. This is usually an organization name
`followed by a period and an extension that indicates the type of organization, such as
`microsoft.com.
`
`The name can be any combination of AZ letters, 09 numerals, and the hyphen (-) plus the
`period (.) character used as a separator.
`
`This DNS Domain Name is used with the host name to create a fully qualified domain
`name (FQDN) for the computer. The FQDN is the host name followed by a period (.)
`followed by the domain name. For example, this could be corp01.research.trey.com,
`where corp01 is the host name and research.trey.com is the domain name. During DNS
`queries, the local domain name is appended to short names.
`
`Note
`A DNS domain is not the same as a Windows NT or LAN Manager domain.
`
`5.
`
`In the Domain Name System (DNS) Search Order box, type the IP address of the DNS
`server that will provide name resolution. Then choose the Add button to move the IP
`address to the list on the right. The network administrator should provide the correct values
`for this parameter.
`
`You can add up to three IP addresses for DNS servers. The servers running DNS will be
`queried in the order listed. To change the order of the IP addresses, select an IP address
`to move, and then use the up- and down-arrow buttons. To remove an IP address, select it
`and choose the Remove button.
`
`6.
`
`In the Domain Suffix Search Order box, type the domain suffixes to add to your domain
`suffix search list, and then choose the Add button.
`
`This list specifies the DNS domain suffixes to be appended to host names during name
`resolution. You can add up to six domain suffixes. To change the search order of the
`domain suffixes, select a domain name to move, and use the up- and down-arrow buttons.
`To remove a domain name, select it and choose the Remove button.
`
`7. When you are done setting DNS options, choose the OK button.
`
`8. When the TCP/IP Configuration dialog box reappears, choose the OK button. When the
`Network Settings dialog box reappears, choose the OK button.
`
`Samsung - Exhibit 1012 - Page 35
`
`

`

`The settings take effect after you restart the computer.
`
`Samsung - Exhibit 1012 - Page 36
`
`

`

`

`

`4.
`
`In the IP Address and SubnetMask boxes, type an additional IP address and subnet mask
`for the selected adapter. Then choose the Add button to move the IP address to the list on
`the right. The network administrator should provide the correct values for this parameter.
`
`Optionally, if your network card uses multiple IP addresses, repeat this process for each
`additional IP address. You can specify up to five additional IP addresses and subnet
`masks for identifying the selected network adapter. This can be useful for a computer
`connected to one physical network that contains multiple logical IP networks.
`
`5.
`
`In the Default Gateway box, type the IP address for an additional gateway that the selected
`adapter can use. Then choose the Add button to move the IP address to the list on the
`right. Repeat this process for each additional gateway. The network administrator should
`provide the correct values for this parameter.
`
`This list specifies up to five additional default gateways for the selected network adapter.
`
`To change the priority order for the gateways, select an address to move and use the up-
`or down-arrow buttons. To remove a gateway, select it and choose the Remove button.
`
`6.
`
`If you want to use DNS for DNS name resolution on Windows networks, check the Enable
`DNS For Windows Name Resolution option.
`
`If this option is checked, the system finds the DNS server by using the IP address specified
`in the DNS Configuration dialog box, as described earlier in this chapter. Checking this
`option enables DNS name resolution for use by Windows networking applications.
`
`7.
`
`If you want to use the LMHOSTS file for NetBIOS name resolution on Windows networks,
`check the Enable LMHOSTS Lookup option. If you already have a configured LMHOSTS
`file, choose the Import LMHOSTS button and specify the directory path for the LMHOSTS
`file you want to use. By default, Windows NT uses the LMHOSTS file found in \systemroot
`\SYSTEM32\DRIVERS\ETC.
`
`For any method of name resolution used in a Windows NT network, the LMHOSTS file is
`consulted last after querying WINS or using broadcasts, but before DNS is consulted.
`
`8.
`
`In the Scope ID box, type the computer's scope identifier, if required on an internetwork
`that uses NetBIOS over TCP/IP.
`
`To communicate with each other, all computers on a TCP/IP internetwork must have the
`same scope ID. Usually this value is left blank. A scope ID may be assigned to a group of
`computers that will communicate only with each other and no other systems. Such
`computers can find each other if their scope IDs are identical. Scope IDs are used only for
`communication based on NetBIOS over TCP/IP.
`
`The network administrator should provide the correct value, if required.
`
`9. To turn on static IP routing, check the Enable IP Routing option.
`
`This option allows this computer to participate with other static routers on a network. You
`should check this option if you have two or more network cards and your network uses
`static routing, which also requires the addition of static routing tables. For information
`about creating static routing tables, see the route utility in Chapter 11, "Utilities Reference."
`
`This option is not available if your computer has only one network adapter and one IP
`address. Also, this option does not support routers running the Routing Information
`Protocol (RIP).
`
`10. If you want this computer to be used to resolve names based on the WINS database,
`
`Samsung - Exhibit 1012 - Page 38
`
`

`

`check the Enable WINS Proxy Agent option.
`
`This option allows the computer to answer name queries for remote computers, so other
`computers configured for broadcast name resolution can benefit from the name resolution
`services provided by a WINS server.
`
`This option is available only if you entered a value for a primary WINS server in the TCP/IP
`Configuration dialog box, as described in "Configuring TCP/IP" earlier in this chapter.
`However, the proxy agent cannot be run on a computer that is also a WINS server.
`
`Consult with the network administrator to determine whether your computer should be
`configured as a WINS proxy agent, as only a few computers on each subnetwork should
`be configured for this feature.
`
`11. When you are done setting advanced options, choose the OK button. When the TCP/IP
`Configuration dialog box reappears, choose the OK button. When the Network Settings
`dialog box reappears, choose the OK button to complete advanced TCP/IP configuration.
`
`You must restart the computer for the changes to take effect.
`
`Samsung - Exhibit 1012 - Page 39
`
`

`

`

`

`2. To identify each community to which you want this computer to send traps, type the name
`in the Community Names box. After typing each name, choose the Add button to move the
`name to the Send Traps With Community Names list on the left.
`
`Typically, all hosts belong to public, which is the standard name for the common
`community of all hosts. To delete an entry in the list, select it and choose the Remove
`button.
`
`Note
`Community names are case sensitive.
`
`3. To specify hosts for each community you send traps to, after you have added the
`community and while it is still highlighted, type the hosts in the IP Host/Address Or IPX
`Address box. Then choose the Add button to move the host name or IP address to the
`Trap Destination for the selected community list on the left.
`
`You can enter a host name, its IP address, or its IPX address.
`
`To delete an entry in the list, select it and choose the Remove button.
`
`4. To enable additional security for the SNMP service, choose the Security button. Continue
`with the configuration procedure, as described in the next section, "Configuring SNMP
`Security."
`
`5. To specify Agent information (comments about the user, location, and services), choose
`the Agent button. Continue with the configuration procedure, as described in "Configuring
`SNMP Agent Information" later in this chapter.
`
`6. When you have completed all procedures, choose the OK button. When the Network
`Settings dialog box reappears, choose the OK button.
`
`The Microsoft SNMP service has been configured and is ready to start. It is not necessary
`to reboot the computer.
`
`Samsung - Exhibit 1012 - Page 41
`
`

`

`

`

`5. Select an option to specify whether to accept SNMP packets from any host or from only
`specified hosts.
`
`

`

`

`

`Applications
`
`Select this option if this Windows NT computer includes any
`applications that use TCP/IP, such as electronic mail. This option
`should be selected for all Windows NT installations.
`
`5. Choose the OK button.
`
`6. When the SNMP Service Configuration dialog box reappears, choose the OK button.
`When the Network Settings dialog box reappears, choose the OK button.
`
`SNMP is now ready to operate without rebooting the computer.
`
`Samsung - Exhibit 1012 - Page 45
`
`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`

`16,384
`y.z
`w.x
`128191
`B
`2,097,1 51
`z
`w.x.y
`192223
`C
`1 Inclusive range for the first octet in the IP address.
`2 The address 127 is reserved for loopback testing and interprocess
`communication on the local computer; it is not a valid network address.
`Addresses 224 and above are reserved for special protocols (IGMP
`multicast and others), and cannot be used as host addresses.
`A network host uses the network ID and host ID to determine which packets it should receive
`or ignore and to determine the scope of its transmissions (only nodes with the same network ID
`accept each other's IP-level broadcasts).
`
`65,534
`254
`
`Because the sender's IP address is included in every outgoing IP packet, it is useful for the
`receiving computer system to derive the originating network ID and host ID from the IP address
`field. This is done by using subnet masks, as described in the following section.
`
`Subnet Masks
`Subnet masks are 32-bit values that allow the recipient of IP packets to distinguish the network
`ID portion of the IP address from the host ID. Like an IP address, the value of a subnet mask is
`frequently represented in dotted decimal notation. Subnet masks are determined by assigning
`1's to bits that belong to the network ID and 0's to the bits that belong to the host ID. Once the
`bits are in place, the 32-bit value is converted to dotted decimal notation, as shown in the
`following table.
`
`Default Subnet Masks for Standard IP Address Classes
`Address
`Bits for subnet mask
`class
`Class A
`
`Class B
`
`Class C
`
`11111111 00000000 00000000
`00000000
`11111111 11111111 00000000
`00000000
`11111111 11111111 11111111
`00000000
`
`Subnet
`mask
`255.0.0.0
`
`255.255.0.0
`
`255.255.255.0
`
`The result allows TCP/IP to determine the host and network IDs of the local computer. For
`example, when the IP address is 102.54.94.97 and the subnet mask is 255.255.0.0, the
`network ID is 102.54 and the host ID is 94.97.
`
`Although configuring a host with a subnet mask might seem redundant after examining the
`previous tables (since the class of a host is easily determined), subnet masks are also used to
`further segment an assigned network ID among several local networks.
`
`For example, suppose a network is assigned the Class-B network address 144.100. This is
`one of over 16,000 Class-B addresses capable of serving more than 65,000 nodes. However,
`the worldwide corporate network to which this ID is assigned is composed of 12 international
`LANs with 75 to 100 nodes each. Instead of applying for 11 more network IDs, it is better to
`use subnetting to make more effective use of the assigned ID 144.100. The third octet of the IP
`address can be used as a subnet ID, to define the subnet mask 255.255.255.0. This splits the
`Class-B address into 254 subnets: 144.100.1 through 144.100.254, each of which can have
`254 nodes. (Host IDs 0 and 255 should not be assigned to a computer; they are used as
`broadcast addresses, which are typically recognized by all computers.) Any 12 of these
`network addresses could be assigned to the international LANs in this example. Within each
`LAN, each computer is assigned a unique host ID, and they all have the subnet mask
`255.255.255.0.
`
`The preceding example demonstrates a simple (and common) subnet scheme for Class-B
`addresses. Sometimes it is necessary to segment only portions of an octet, using only a few
`
`Samsung - Exhibit 1012 - Page 56
`
`

`

`bits to specify subnet IDs (such as when subnets exceed 256 nodes). Each user should check
`with the local network administrator to determine the network's subnet policy and the correct
`subnet mask. For all systems on the local network, the subnet mask must be the same for that
`network ID.
`
`Important
`All computers on a logical network must use the same subnet mask and network ID; otherwise,
`addressing and routing problems can occur.
`
`Samsung - Exhibit 1012 - Page 57
`
`

`

`

`

`

`

`internetwork. Each DHCP server that receives the discover message responds with an offer
`message containing an IP address and valid configuration information for the client that sent
`the request.
`
`The DHCP client collects the configuration offerings from the servers and enters a selecting
`state. When the client enters the requesting state, it chooses one of the configurations and
`sends a request message that identifies the DHCP server for the selected configuration.
`
`The selected DHCP server sends a DHCP acknowledgment message that contains the
`address first sent during the discovery stage, plus a valid lease for the address and the TCP/IP
`network configuration parameters for the client. After the client receives the acknowledgment, it
`enters a bound state and can now participate on the TCP/IP network and complete its system
`startup. Client computers that have local storage save the received address for use during
`subsequent system startup. As the lease approaches its expiration date, it attempts to renew
`its lease with the DHCP server, and is assigned a new address if the current IP address lease
`cannot be renewed.
`
`DHCP Client State Transition During System Startup
`
`In Windows NT Server, the network administrator uses DHCP Manager to define local policies
`for address allocation, leases, and other options. For information about using this tool, see
`Chapter 4, "Installing and Configuring DHCP Servers." For information about the steps for
`setting up TCP/IP using DHCP, see "Configuring TCP/IP" in Chapter 2, "Installing and
`Configuring Microsoft TCP/IP and SNMP." For information about setting up DHCP relaying, see
`the documentation for your router.
`
`Samsung - Exhibit 1012 - Page 60
`
`

`

`

`

`

`

`of the WINS server.
`
`In this environment, when NT_PC1 wants to communicate with NT_PC2, it queries the WINS
`server for the address of NT_PC2. When NT_PC1 gets the appropriate address from the
`WINS server, it goes directly to NT_PC2 without broadcasting. Because the name queries go
`directly to the WINS server, p-node avoids loading the network with broadcasts. Because
`broadcasts are not used and because the address is received directly, computers can span
`routers.
`
`The most significant problems with p-node are the following:
`
`

`

`some extensions have been added to this file to make it easier to manage (as described in
`Chapter 6, "Setting Up LMHOSTS"), but modified b-node is not an ideal solution.
`
`Some sites may need to use both b-node and p-node modes at the same site. Although this
`configuration can work, administrators must exercise extreme caution in doing so, using it only
`for transition situations. Because p-node hosts disregard broadcasts and b-node hosts rely on
`broadcasts for name resolution, the two hosts can potentially be configured with the same
`NetBIOS name, leading to unpredictable results. Notice that if a computer configured to use
`b-node has a static mapping in the WINS database, a computer configured to use p-node
`cannot use the same computer name.
`
`Windows NT computers can also be configured as WINS proxy agents to help the transition to
`using WINS. For more details, see the next section.
`
`Samsung - Exhibit 1012 - Page 64
`
`

`

`

`

`Example of an Internetwork with WINS Servers
`
`The proxy communicates with the WINS server to resolve names (rather than maintaining its
`own database) and then caches the names for a certain time. The proxy serves as an
`intermediary, by either communicating with the WINS server or supplying a name-to-IP
`address mapping from its cache. The following illustration shows the relationships among
`WINS servers and clients, including proxies for non-WINS computers and the replication
`between WINS servers.
`
`Example of Clients and Servers Using WINS
`
`In the above illustration, ClientA can resolve names by first querying the WINS server and, if
`that fails, then using broadcast name queries. ClientB, which is not WINS-enabled, can only
`resolve names using broadcast name queries, but when ClientC receives the broadcast, it
`forwards the request to the WINS server and returns the address to ClientB.
`
`However, a complex environment presents additional problems. For example, an internetwork
`might consist of two subnets, with all the computers belonging to DomainA attached to
`Subnet1, all the computers in DomainB attached to Subnet2, and computers from DomainC
`attached to either of the subnets. In this case, without WINS, DomainA computers can browse
`Subnet1, DomainB computers can browse Subnet2, and DomainC computers can browse both
`subnets as long as the primary domain controller for DomainC is available. With WINS,
`computers from all domains can browse all subnets if their WINS servers share databases.
`
`Samsung - Exhibit 1012 - Page 66
`
`

`

`If the Windows NT client computer is also DHCP-enabled and the administrator specifies
`WINS server information as part of the DHCP options, the computer will usually be
`automatically configured with WINS server information. You can manually configure WINS
`settings, as described in Chapter 2, "Installing and Configuring Microsoft TCP/IP and SNMP":
`
`

`

`3.
`
`If querying the WINS server does not succeed and if the client computer is configured as
`an h-node, the computer broadcasts name query request packets in the same manner as
`a non-WINS-enabled computer.
`
`4. Finally, if other methods fail, the local LMHOSTS file is checked. This also includes a
`search of any centralized LMHOSTS files referred to in #INCLUDE statements, as
`described in Chapter 6, "Setting Up LMHOSTS."
`WINS servers accept and respond to UDP name queries. Any name-to-IP address mapping
`registered with a WINS server can be provided reliably as a response to a name query.
`However, a mapping in the database does not ensure that the related device is currently
`running, only that a computer claimed the particular IP address and it is a currently valid
`mapping.
`
`WINS Name Registration
`Name registration ensures that the computer's name and IP address are unique for each
`device.
`
`If WINS is enabled The name registration request is sent directly to the WINS server to be added
`to the database. A WINS server accepts or rejects a computer name registration depending on
`the current contents of its database. If the database contains a different address for that name,
`WINS challenges the current entry to determine whether that device still claims the name. If
`another device is using that name, WINS rejects the new name registration request.
`Otherwise, WINS accepts the entry and adds it to its local database together with a timestamp,
`an increment