I
`
`I
`
`Client Name:
`Client Comment:
`III
`
`In the Add Reserved Clients dialog box,
`2.
`the first reserved client:
`
`type information to identify
`
`A ;
`
`=IP Address specifies an address from the reserved address pool. You can
`specify any
`reserved, unused.IP address. DHCP Manager checks and.warns you if aduplieateg
`duplicate or
`nonreserved address is entered.
`
`-Is
`
`;=Unique Identifier usually specifies the media access control
`for the
`
`(MAC) address
`
`client computer's network adapter card. You can determine this address by
`typing net
`config wksta at the command prompt on the client computer.
`
`-Is
`
`;=Client Name specifies the computer name for this client. This is used for
`identification
`
`purposes only and does not affect the actual computer name for the client.
`This is not
`
`|Il|L
`1111IIII||||I||I111|I11||I||111 |:|| II .||||| IIII.|:II :.||| Il
`||||L
`Jl-||||= I III II ||||~|| II||I|| II |||||II|I|I|
`II|= ||||II|
`J||||||||||| 11:1:111.1111 111.11.111.111.11111 I|||||
`||
`|.|1|L1|
`|.| II
`111111111.1111111111111111.111. :|.| Il
`|||::||.L
`Installing and Configuring DHCP Sewers l7of33
`1. From the Scope menu, choose Add Reservations.
`l_I_ni
`unlllIr"l|'11'n1l1'||r' Hr—n'1|*\J»mln'n|"1F pmI"| wrl
`
`.
`. >>>>~~
`
`rlmnn 'wr r||*|ll
`
`llllll||llIIlil|I||IIi|lI|I|I ||l||||u||l|:L
`
`available for MS—B9S—basedDOSbased clients+£ in this case, only the Unique
`Identifieridentifier appears.
`
`as
`
`Client Comment is any optional text that you enter to describe this client.
`A:
`3.
`Choose the Add button to add the reservation.to the DHCP database. You
`can continue to
`
`add reservations without dismissing this dialog box.
`4.
`When you have added all reservations, choose the Close button.
`After the IP address is reserved in DHCP Manager,
`the client computer must
`be restarted to be
`
`configured with the new IP address.
`If you want to change a reserved.IP address for aelienta client, you have to
`remove the old reserved
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 91
`
`

`
`address and.add.a new reservation. You.can change any other information about
`a reserved
`
`client while keeping the reserved IP addressefi
`llJe~—To change the reserved IP address
`1.
`Make sure the reserved client is not using the old IP address. To do
`this, shut down the
`client computer immediately after issuing the ip
`eenfiglreleaseconfiggrelease command on that client
`computer.
`2.
`In the Active Leases dialog box, select the reserved IP address in the
`Client list, and
`choose the Delete button. ¥heHTnen choose the OK button.
`
`Fronithe Scopeinenu, choose Add Reservations, and.then.enter information
`3.
`for a new
`
`reservation as described earlier in this sectionefi
`llae~—To change basic information for areserveda resewed client
`1.
`From the Scope menu, choose Active Leases.
`2.
`In the Client list of the Active Leases dialog box, select the address
`of thetime reserved client
`
`that you want to change, and then choose the Properties button.
`3.
`In the Client Properties dialog box, change the unique identifier,
`client name, or comment,
`and then choose the OK button.
`Note
`
`You can only change values in the Client Properties dialog box for reserved
`clients.
`
`You can also view and change the options types that define configuration
`parameters for
`selected reserved clients by choosing the Options button in the Client
`Properties dialog box.
`Changing options for a reserved client follows the same procedure as use to
`originally define
`options, as described in "DefmingDefining Options for Reservations" earlier
`in this chapter.
`
`Managing the DHCP Database Files
`The following files are stored in the \systemreetsystemroof\SYSTEM32\DHCP
`directory that is created
`when you set up a DHCP server:
`
`A B
`
`HQPTMBBI DHCPMDB is the DHCP database file.
`
`as
`
`DHGPT$MPDHCPTMP is a temporary file that DHCP creates for temporary database
`information.
`
`A l
`
`JET.LOG and the JET*.LOG files contain logs of all transactions done with
`the database.
`
`These files are used by DHCP to recover data if necessary.
`
`as
`
`S¥S¥EMTMeBl SYSTEMMDE3 is used by DHCP for holding information about the
`structure of its database.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 92
`
`

`
`Caution
`
`The DHCP . TMP . DHCPMDB .
`should not be removed or
`
`JET . LOG, and SYSTEMMDB files
`
`tampered with.
`The DHCP database and related Registry entries are backed up automatically
`at a specific
`interval
`(15 minutes by default), based on the value of Registry parameters
`(as described later
`
`in this chapter). You can also forced database backup while working in DHCP
`Manager.
`Installing and Configuring DHCP Servers l8of 33
`
`Troubleshooting DHCP
`The following error conditions can appear to indicate potential
`preblemsprobiems with the DHCP server:
`gi
`
`l The administrator can't connect for a DHCP server using DHCP Manager. The
`message
`
`that appears might be,
`
`"The RPC serverser§[er is unavailable."
`
`gi
`
`l DHCP clients cannot renew the leases for their IP;§ addresses. The message
`ihat appears
`on the client computer is, "The DHCP client eeuldcouid not renew the IP address
`leaselease."
`
`gi
`
`l The DHCP Client service or Microsoft DHCP Server service may be down and
`cannot be
`restarted.
`
`The first task is to make sure the DHCP services are running.
`Tw7———To ensure the DHCP servieessewices are running
`1.
`Use the Services option.inJ3ontrol Panel to verify that the DHCP services
`are runnmgrunning.
`Inig the Services dialog box for the client computer, Started should appear
`in the Status
`
`column for the DHCP Client service. For the DHCP server itself, the Started
`should appear
`in the Status column for the Microsoft DHCP Server servteeservice.
`
`If a necessary service is not started on either computer, start the
`2.
`service.
`
`In rare circumstances,
`occur. If the DHCP
`
`the DHCP server may not boot or aST9Pa STOP error may
`
`server is down,
`H
`
`follow these steps to restart.
`3;.
`3
`E
`E.
`.
`E
`E
`
`77¢———To restart a DHCP serversewer that is down
`1.
`TamTurn off the power to the server and wait one minute.
`2. TemTurn.on.the power, start Windows NT Server, and.log on under an account
`with
`
`Administrator rights.
`3.
`At the command prompt,
`Note
`
`type net start dhcpserver and press ENTEREnter.
`
`Use Event Viewer to find the possible source of problems with.DHCP services.
`Installing and Configuring DHCP Servers 19 of33
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 93
`
`

`
`Troubleshooting DHCP
`Restoring the DHCP Database
`Tfyeelf you ascertain that the DHCP servieessewices are running on both the
`elientciient and server computers
`but the error conditions described earliereariier persist,
`database is not available or
`
`then the DHCP
`
`has becomes corrupted”-$f;£eaDHCP server fails for'any'reason4 you.can.restore
`the database
`
`from the automatic backup filesfiies.
`T7w———To restore a DHCP database
`
`Restart the DHCP server. If the;=g DHCP database has become corrupted,
`0
`it is automatically
`restored from the DHCP backup directory specified in the Registry, as
`described later in
`
`this chapter.
`T7w———To force the restoration of a DHCP database
`4—————Set the value of RestoreFlag in the Registry to 1, and then.restart the
`computer. For
`information.about this parameter, see "Registry Parameters for DHCP Servers"
`later in this
`
`chapter.
`T7¢———To manually restore a DHCP database
`0 —$ftheIf the two restore methods described earlier do not work, manually
`copy all DHCP
`database files from.the backup directory to the \DHCP working directory. Then
`restart the
`Microsoft DHCP Server service.
`
`installing and Configuring DHCP Servers 20 of 33
`
`Troubleshooting DHCP
`Backing up the DHCP Database onto Another Computer
`You may also find a situation where you need to backup aDHGPa DHCP database
`to another
`
`follow these steps.
`computer. To do this,
`T7w———To move a DHCP database
`0
`Use the Replicator service to copy the contents of the DHCP backup
`directory to the new
`computervy
`Installing and Configuring DHCP Servers 21 of 33
`
`Installing and Configuring DHCP Servers 22 of33
`Advanced Configuration Parameters for DHCP
`This section presents configuration parameters that affect the behavior of
`DHCP servers and
`
`clients , and that can be modified only through Registry Editor . For the changes
`to take effect
`
`after you modify any of these value entries, you must restart the Microsoft
`DHCP Serversenger
`service for server parameters or the DHCP Client service for client
`parameters.
`€aatienCauUon
`
`You can impair or disable Windows NT if you make incorrect changes in the
`Registry while
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 94
`
`

`
`using Registry Editor. Whenever possible, use DHCP Manager to make
`configuration changes,
`rather than using Registry Editor. Tflg you make errors while changing values
`with Registry Editor,
`you will not be warned, because Registry Editor does not recognize semantic
`errors.
`
`£JJ+e—To make changes to the DHCP serversewer or client configuration using
`Registry Editor
`1.
`Run REGEDT32.EXE from File Manager or Program Manager, or at a command
`prompt,
`
`type start regedt32 and press ENTERT£
`When the Registry Editor window appears, you can press Flgg to get Help on
`hewpgg to make
`changes in Registry EditOr?£
`2.
`In.Registry Editor, click the window titled.HKEY_LOCAL_MAGH$NE MACHlNE
`on Local Machine, and then—eliek
`tnen Click the icons for the SYSTEM subtree until you reach the subkey for
`the specific
`parameter, as described in the following sections.
`The following sections describe the value entries for parameters for DHCP
`servers and clients
`
`that can be set only by adding an entry or changing their values in Registry
`Editor.
`
`Ghapter—4—lnstalling—and—Genfiguring—BH€P—Servers—Advanced Configuration
`Parameters for DHCP
`
`Registry Parameters DHCP Servers
`WhenWrren.you change any of these parameters except RestereFiagRestoreFIag,
`you must restart the
`computer for the changes to take effect. For the RestoreFlag parameter, you
`must restart the
`Microsoft DHCP Server service.
`
`The Registry parameters for DHCP servers are specified under the following
`key:
`
`SYSTEM\current\eurrenteentrelsetcul'rentcontrolset\services\DHCPServer\Pa
`rameters
`
`AP$PreteeeiSappert—AP ProtocoISu ort
`Data type = REG_DWORD
`
`Range = Gxl7—9x0xl
`0x2, G*g§4, Gx2§5, 9x227 Befaalt—=G*l
`Defauit
`: 0x1
`
`Specifies the supported protocols for the DHCP server. You can change this
`value to
`
`ensure that different computers running different protocols can access the
`DHCP server.
`
`The values for this parameter can be the following:
`
`
`
`BackupDatabasePath
`Data type = REG_EXPAND_SZ
`Range =filename— Hlename
`Default = %SystemRoot%\system32\dhcp\backup
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 95
`
`

`
`Specifies the location of the backup database file where the database is backed
`UP
`
`periodicallyu The best-leeatienlocation.for the backup file is on another hard
`drive,
`so that the
`database can be recovered in case of asystema system drive crash. Do not
`specify anetwerk—a network
`drive, because DHCP Manager cannot access a network drive for database backup
`and
`
`recovery.
`Baekup$nterval—Backuplnterval
`Data type = REG_DWORD
`Range = no limit
`Default = 15 minutes
`
`Specifies the interval for backing up the database.
`USD (‘T SDU‘SD U) (D Q i—' (D SD:3S:‘U i—' :3('1' (D H<1SD i—'
`
`Data type = REG_DWORD
`‘PUSDD(Q(D
`= No limit
`Default = 9xg§15180 (864,000 minutes — 24 hours)
`Specifies the interval for cleaning up expired client records from the DHCP
`database,
`Installing and Ccnfiguring DHCP Sewers 23 of 33
`
`ESE RPC over TCPIP protocols
`For RPC over named pipes protocols
`(LPC) protocols
`For RPC over local procedure call
`For RPC over TCPIP and RPC over LPC
`
`For RPC over all three protocols (TCP/IP, named pipes, and LPC)
`
`freeing up those IP addresses for reuse.
`DatabaseLo
`in Fla
`
`i ‘
`
`Data type = REG:;DwoRD
`PUSDD(Q(D
`= 0 or 1
`(true—that is, database logging is enabled)
`Default = 1
`Specifies whet%&H+4Nhether to record the database changes in.theuE§%4i¥3JETLOG
`file. This log file is used
`after asystema.system.crash.to recover changes that have not been made to the
`database file
`
`defined by DatabaseName. Database logging affects system performance, so
`Batabaselwwegging
`DatabaseLogging can be turned.off if you believe the system is highly stable
`and ifleggingif
`logging is adversely affecting system performance.
`DatabaseName
`
`Data type = REG_S%§;
`Range = filename
`Default zdhepvmdb dhcpmdb
`Specifies the name of the database file to be used for the DHCP client
`information
`database.
`DatabasePath
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 96
`
`

`
`Data type = REG_=EXPAND_SZ
`Range = pathname
`Default = %SystemRoot%\System32\dhcp
`Specifies the location of the database files that have been created and opened.
`RestereFiag—RestoreFlag
`Data type = REG_BW9RBDwoRD
`Range = Gero or 1
`Default = 0
`(false—thattlwat is, do not restore)
`Specifies whetherwhether to restore the database from the backup directory.
`This flag is reset
`automatically after the successful restoration of the database.
`
`Advanced Configuration Parameters for DHCP
`Registry Parameters for DHCP Clients
`The Registry parameters for DHCP clients are specified under the following
`key:
`SYSTEM\current\currentcontrolset\services\DHCP\Parameter\<option#>
`The GptienOpt[on# keys are a list of DHCP options that the client can.request
`from the DHCP server.
`
`For each of the default options,
`RegLocation
`Data type = REG_=SZ
`Default = Depends on the Registry location for the specific option
`Specifies the location in the Registry where the option value is written when
`it is obtained
`
`the following values are defined:
`
`fronithe DHCP server. The ";?" character expands to the adapter name for which
`this
`
`option value is obtained.
`KeyType
`Data type = REG_DWORD
`Default 29*: 0x7
`
`Specifies the type of Registry keyggy for the option.
`2
`.3 J.
`E
`E
`.
`J
`J.
`.
`
`Installing and Configuring DHCP Servers 24 of 33
`
`This section provides some suggestions for setting lease options, dividing
`the free address
`
`pool among DHCP servers, and avoiding DNS naming problems.
`Installing and Configuring DHCP Sewers
`Guidelines for Setting Local Policies
`25 of 33
`
`Guidelines for Setting Local Policies
`Guidelines for Managing DHCP Addressing Policy
`Allocation of IP addresses for distribution by DHCP servers can be done
`dynamically or
`manually. These methods use the same DHCP elient—olient~server protocol, but
`the network
`
`administrator manages them differently at the DHCP server.
`Dynamic Allocation of IP Addresses
`Dynamic allocation allows aelienta client to be assigned an IP address from
`the free address pool.
`The lease for the address has a lease duration.(expiration.date), before which
`the client must
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 97
`
`

`
`renew the lease to continue using that address. Depending on the local lease
`policies defmeddefined
`by the administrator, dynamically allocated addresses can be returned to the
`free address pool
`if the client computer is not being used, if it is moved to another subnet,
`or if its lease expires.
`Any IP addresses that are returned to the free address pool can be reused by
`the DHCP server
`
`when allocating an IP address to a new client . Usually the local policy ensures
`that the same IP
`
`address is assignedtu3a.client each time that systenistarts and.that addresses
`returned to the
`
`pool are reassigned.
`After the renewal time of the lease time has passed,
`the renewing state
`(as described in Chapter 3, "Networking Concepts for TCP/£P;§"). The client
`sends a request
`message to the DHCP server that provided its configuration information.
`Tfthelf the request for a
`lease extension fits the local lease policy,
`acknowledgment that
`contains the new lease and.configuration.parameters. The client then updates
`its configuration
`values and returns to the bound state.
`
`the DHCP server sends an
`
`the DHCP client enters
`
`When the DHCP client is in the renewing state, it must release its address
`immediately in the
`rare event that the DHCP server sends a negative acknowledgment. The DHCP
`server sends
`
`this message to inform aelienta client that it has incorrect configuration
`information, forcing it to
`release its current address and acquire new information.
`Tfthelf the DHCP client cannot successfully renew its lease, the client enters
`arebindinga rebinding state. At
`this stage, the client sends a request message to all DHCP servers in its range,
`attempting to
`renew its lease. Any server that can extend the lease sends an acknowledgment
`containing the
`extended lease and updated configuration information. Tfehelf the lease
`expires or if a DHCP server
`responds with a negative acknowledgment,
`configuration and
`return to the initializing state.
`for aeemputera computer that is
`moved from one subnet to another.)
`
`(This happens automatically, for example,
`
`the client must release its current
`
`Efehelf the DHCP client uses more than one network adapter to connect to
`multiple networks,
`this
`protocol is followed for each adapter that the user wants to configure for
`TCP/lP;§. Windows NT
`allows multihomed systems to selectively configure any combination of the
`system's interfaces.
`You can use theggg ipconfig utility to view the local IP configuration for
`aelienta client computer.
`When a DHCP—enabled computer is restarted, it sends a message to the DHCP
`server with its
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 98
`
`

`
`current configuration information. The DHCP server either confirms this
`configuration or sends
`a negative reply so that the client must begin the initializing stage again.
`System startup might
`therefore result in.a11ew IP address for aelien%a.client computer, but neither
`the user nor the network
`
`administrator has to take any action in the configuration process. Chapter
`4—$nstalling—and—Genfiguring—DH€P—Servers
`Manual Allocation of IP Addresses
`
`Manual allocation follows the policy used in most current TCP/$P;§
`implementations. With this
`method,
`the network administrator defines the IP address and other
`configuration options that
`Installing and Configuring DHCP Sewers 26 of 33
`
`the DHCP servers will provide for a particular computer. The DHCP servers
`respond based on
`the client's unique identifier, which is the network adapter's MAC—layer
`address. Any IP
`addresses assigned in this way cannot be allocated by DHCP servers to other
`clients using
`either automatic or dynamic allocation” The address has apeim%a&enea.permanent
`lease.
`
`For example, for the range of IP addresses to be provided.ehreeghtnrough.RAS
`servers,
`these
`addresses should.be manually excluded.from.the range of dynamically allocated
`addresses.
`
`Installing and Configuring DHCP Sewers 27 Of33
`Guidelines for Setting Local Policies
`Guidelines for Lease Options
`To define appropriate values for lease duration, you should consider the
`frequency of the
`following events for your network:
`
`A '
`
`Changes to DHCP options aridand default values
`
`1 '
`
`Network interface failures
`
`i 1
`
`Computer removals for any purpose
`
`-Ia
`
`;=Subnet changes by users because of office moves,
`at different
`
`laptop computers docked
`
`workstations7£ and so on
`Allgg of these types of events cause IP addresses to be released.by the client
`or cause the
`
`leases to expire at the DHCP server. Consequently,
`be returned to the
`
`the £P;§ addresses will
`
`free address pool to be reused.
`Tfmanylf many changes occur on your internetwerkintemetwork, you should
`assign short lease times, such as two
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 99
`
`

`
`weeks. This wayflgy,
`can be reassigned
`quickly to new DHCP client computers requesting TCP/IP configuration
`information.
`
`the addresses assigned to systems that leave the subnet
`
`Another important factor is the ratio between connected computers and
`available IP addresses.
`
`the demand for reusing addresses is low in a network where 40
`For example,
`systems share a
`classGaddressCaddress(with254availableaddresses).A&engAlongleasetime
`such as two months would
`
`be appropriate in such a situation. However, if 230 computers share the same
`address pool,
`demand for available addresses is much greater, so a lease time of a few days
`or weeks is
`
`more appropriate.
`Notice, however, that short lease durations require that the DHCP server be
`available when the
`
`client seeks to renew the lease. So backup servers are especially important
`when short lease
`
`durations are specified.
`
`Guidelines for Setting Local Policies
`Guidelines for Partitioning the Address Pool
`You will probably decide to install more than.one DHCP server, so the failure
`of any individual
`server will not prevent DHCP clients from starting. However, DHCP does not
`provide awaya way for
`DHCP servers to cooperate in ensuring that assigned addresses are unique.
`Therefore, you
`must divide the available address pool among the DHCP servers to prevent
`duplicate address
`assignment.
`AtypiealA typical scenario is a local DHCP server that maintains TCP/IP
`configuration information for
`two subnets. For each DHCP server,
`percent of the IP
`address pool for local clients and 30 percent for clients from the remote
`subnet, and then
`configures a relay agent to deliver requests between the subnets.
`This scenario allows the local DHCP server to respond to requests from local
`DHCP clients
`
`the network administrator allocates 70
`
`most of the time. The remote DHCP server will assign addresses to clients on
`the other subnet
`
`only when the local server is not available or is out of addresses. This same
`method of
`
`partitioning among subnets can be used.in.a multiple subnet s:e£&fi}Eiescenario
`to ensure the availability
`of a responding server when a DHCP client requests configuration.information.
`J Installing and Configuring DHCP Ser\/ers 28 of 33
`
`Guidelines for Setting Local Policies
`Guidelines for Avoiding DNS Naming Conflicts
`DNS can be used to provide names for network resources, as described in Chapter
`3,
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 100
`
`

`
`"Networking Concepts for TCP/IPIE." However, DNS configuration is static.
`With DHCP, a host
`can easily have a different IP address if its lease expires or for other
`reasons, but there is no
`standard for updating DNS servers dynamically when IP address information
`changes.
`Therefore, DNS naming conflicts can occur if you are using DHCP for dynamic
`allocation of IPIE
`addresses.
`
`This problem will primarily affect systems that extend internetworking
`services to local network
`
`users. For example, a server acting as an anonymous FTP server or as an e—mail
`gateway
`might require users to contact it using DNS names. In.such.cases, such.clients
`should have
`reserved leases with an unlimited duration..
`
`For workstations in environments that do not require the computers to register
`in the DNS
`
`name space, DHCP dynamic allocation can be used without problems.
`Ghapter—4—Installing and Configuring DHCP Servers 29 of 33
`
`Guidelines for Setting Local Policies
`Using DHCP with Diskless Workstations
`Ifyearlf your network includes diskless workstations or Xterminalx terminal
`BOOTP clients that need
`
`configuration information to use TCP/IP, you must build profiles.
`the intemetwerking
`internewvorking Bootstrap Protocol used to configure systems across
`intemeewerksinternetworks. DHCP is
`
`(BOOTP is
`
`an extension of BOOTP.)
`
`You.might decide to continue to manage these workstations using your existing
`BOOTP
`
`servers. If so, you must be sure to exclude these addresses from the free
`address pool
`maintained by the DHCP server.
`Installing and Configuring DHCP Servers 30 of 33
`
`Planning astraeegya Strategy for DHCP
`This section describes how to develop strategies for placing DHCP servers on
`small—scale and
`
`large—scale installations. Most network administrators implementing DHCP
`will also be planning
`a strategy for implementing WINS servers. The planning tasks described here
`also apply for
`WINS servers, and in fact,
`DHCP and WINS
`
`the administrator willwill probably want to plan
`
`implementation in tandem.
`The following describes the general planning tasks:
`1.
`Compile a list of a requirements,
`including:
`._____
`
`' Client support
`
`(numbers and kinds of systems to be supported)
`
`a—————
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 101
`
`

`
`;=Interoperability with existing systems, especially requirements for
`mission—;critical
`accounting, personnel, and similar information systems
`
`as
`
`;=Hardware support and related software compatibility (including routers,
`switehesswitciwes, and
`servers)
`
`i ;
`
`including SNMP requirements and other tools
`=Network monitoring software,
`2.
`Isolate the areas of the network wherewhere processes must continue
`uninterrupted, and target these
`tnese areas for the last stages of implementation.
`3.
`Review theggg geographic and physical structure of the network to
`determine the best plan for
`defining logical subnets as segments of the internetwork.
`4. BefmeDefine the components in the new system that require testing, and
`develop a phase plan
`for testing and adding components.
`For example, the plan.could.defmedefine units of the organization to be phased
`into using DHCP,
`and the order for types of computers to be phased in (including Windows NT
`servers and
`
`workstations, Microsoft RAS servers and clients, Windows for Workgroups
`computers, and
`MS—DOS clients).
`
`Create a pilot project for testing. Be sure that the pilot project
`5.
`addresses all the
`
`requirements identified in Task #lT;i
`6.
`Create a second test phase,
`including tuning the DHCP (and WINS)
`server—;client
`configuration for efficiency. This task can include determining strategies
`for backup servers
`and for partitioning the address pool at each server to be provided to local
`versus remote
`clients.
`7.
`Document all architecture and administration issues for network
`administrators.
`
`remember that the actual placement of the servers in the
`
`Implement a final phase for bringing allali organizational units into
`8.
`using DHCP.
`While planning,
`physical network
`need not be a major planning issue. DHCP servers (and WINS servers) do not
`participate in
`the Windows NT Server domain model, so domain membership is not an issue in
`planning for
`server placement. Because most routers can forward DHCP configuration
`requests, DHCP
`servers are not required on every subnet in the internetwork. Also, because
`these servers can
`
`be administered remotely from any Windows NT Server computer that is DHCP-
`or
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 102
`
`

`
`WINS—enabled,
`placement.
`Installing and Configuring DHCP Sewers 31 of 33
`
`location is not amaéera major issue in planning for server
`
`3 P
`
`lanning asmalla Strategy for DHCP
`Planning a Small—Scale Strategy for DHCP Servers
`For asmalla.small LAN that does not include routers and.subnetting, the server
`needs for the network
`
`can probably be provided with asinglea single DHCP server.
`Planning in this case includes determining the following:
`._____
`
`' The hardware and storage requirements for the DHCP server
`
`-Is
`
`;=Which.computers can immediately become DHCP clients for dynamic addressing
`and
`
`which should keep their static addresses
`
`-Ia
`
`;=The DHCP option types and.their values to be predefined for the DHCP clients
`DHCP wwf
`address
`d3a e
`Local
`Netuuo
`~§~
`‘r DHCP climts
`
`ASingleA.Single Local Network Using.Automatic TCPIIP Configuration with DHCP
`€hapter—4—Installing
`and Configuring DHCP Servers 32 of 33
`
`Planning aLargea Strategy for DHCP
`Planning a Large—Scale Strategy for DHCP Servers
`The network administrator can use relay agents implementing RFC 1542 (usually
`IP routers)
`
`so that DHCP servers located on one node of the internetwork can respond to
`TCP/IP
`configuration requests from remote nodes. The relay agent forwards requests
`from local DHCP
`
`clients to the DHCP server and subsequently relays responses back to the
`clients.
`
`El
`§lble‘ "Qi/" IP rodef
`if
`DHCP clieffs
`
`An.Tnternetwerklnternetwork'Using.Automatic TGP%£PTCPIIP Configuration with
`DHCP
`
`The additional planning issues for a large enterprise network includes:
`T; Compatibility of hardware and software routers with.DHCP, as described at
`the beginning
`of this chapter.
`&; Planning the physical subnetting of the network and relative placement of
`DHCP servers.
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 103
`
`

`
`This includes planning for placement of DHCP (and.WINS servers) among subnets
`in awayg
`way that reduces b—node broadcasts across routers.
`
`1-; Specifying the DHCP option types and their values to be predefined per scope
`for the
`
`DHCP clients. This may include planning for scopes based on the needs of
`particular
`groups of users. For example, for a marketing group that uses portable
`computers docked
`at different stations, or for a unit that frequently moves computers to
`different locations,
`shorter lease durations can be defined for the related scopes. This way,
`frequently
`changed IP;§ addresses can be freed for reuse.
`As one example,
`the segmenting of theWANthe WAN into logical subnets could
`match the physical
`structure of the internetwork. Then.one-IP;§ subnet can serve as the backbone,
`and off this
`
`backbone each physical subnet would maintain a separate IP subnet address.
`In this case, for each subnet asinglea single computer running Windows NT
`Server could be
`
`configured as both the DHCP and WINS server. Each server would administer a
`defined
`
`number of IP addresses with.aspeeifiea specific subnet mask, and would also
`be defined as the default
`
`gateway. Because the server is also acting as the WINS server, it can respond
`to name
`
`resolution requests from all systems on its subnet.
`These DHCP and WINS servers can.in.eemturn.be backup servers for each other.
`The
`
`administrator can partition the address pool for each server to provide
`addresses to remote
`clients.
`
`There is no limit to the maximum number of clients that can be served by
`asinglea single DHCP
`server. However, your network may have practical constraints based on the IP
`address class
`
`and server configuration issues such as disk capacity and CPU speed.
` 5
`
`Installing and Configuring WINS—ServersDHCP Sewers 33 of 33
`8 clients
`
`primary saver
`_ _>>.~..
`_>>_
`
`.55
`
`£ I
`
`P address
`database
`
`Installing and Configuring WINS
`Sewers
`
`AWINS—serverA WINS sewer is awindewsa Windows NT Server computer running
`Microsoft TGPIIPTCPZIP and the Windows
`Internet Name Service (WINS) server software. WINS servers maintain a database
`
`that maps
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 104
`
`

`
`computer names to IP addresses, allowing users to easily communicate with
`other computers
`while gaining all the benefits efTGPof TCP/IP.
`This chapter describes how to install WINS servers and.how to use WINS Manager
`to manage
`these servers. The topics include the following:
`I——' WINS benefits
`
`l——i:Installing and administering WINS servers
`&——;_Configuring WINS serverssewers and replication partners
`I——;_Managing static mappings
`&——;=Setting preferences for WINS Manager
`&——;=Managing the WINS database
`&——;=Troubleshooting WINS
`&——;=Advanced configuration parameters for WINS
`I——;=Planning astrategya strategy for WINS servers
`For an overview of how WINS works, see "Windows Internet Name-Servieesengice
`and Broadcast
`
`Name ReselutienResoiution" in Chapter 3, "Networking Concepts for TCP/IP."
`Note
`
`WINS can also be configured and monitored using SNMP. All configuration
`parameters can be
`set using SNMP,
`including configuration parameters that can
`etherwiseothenivise only be set by editing
`the Registry. For alista list of WINS MIB object types, see Appendix A,
`Object Types for
`Windows NT."
`
`"MIB
`
`You can also use Performance Monitor to track WINS server performance, as
`described in
`
`Chapter 8, "Using Performance Monitor with.TGPIIP—ServieesTCP[IP Sengices."
`Chapter 5 lof27
`
`WINS Benefits
`
`Using WINS servers can offer these benefits on your
`internetwerk+internetworkz
`
`i ;
`
`=Dynamic database maintenance to support computer name registration and.name
`resolution” Although WINS provides dynamic name services, it offers a NetBIOS
`namespace, making it much more flexible than DNS for name resolution.
`
`A '
`
`Centralized management of the computer name database and the database
`replication
`policies, alleviating the need for managing LMHOSTS files.
`
`A l
`
`Dramatic reduction of IP broadcast traffic in Microsoft
`
`ifltemetwerksinternetworks, while allowing client
`computers to easily locate remote systems across local or wide area networks.
`
`as
`
`;=The ability for clients on awindewsa Windows NT Serversewer network
`(including Windows NT, Windows
`for Workgroups, and LAN Manager 2.x)
`router
`
`to browse domains on the far side of a
`
`Petitioner Sipnet EU S.R.O. - Exhibit 1018 - Page 105
`
`

`
`without a local domain controller being present on the other side of the
`router.
`
`-Ia
`
`Asealable' A scalable design, making it a good choice for name
`reselaeienresoiution for medium to very large iaeemeewerks
`internetworks.
`Note
`
`WINS client software is part of the Microsoft TCP/IP—32 for Windows for
`Workgroups and the
`Microsoft Network Client 2 . 0