throbber
r.
`
`
`
`Installing and Configuring WINS Servers
`Configuring WINS Servers and Replication
`Partners
`
`7of27
`
`Configuring Replication Partners
`
`WINS sen/ers communicate among themselves to fully replicate their databases, ensuring that a
`name registered with one WINS server is eventually replicated to all other WINS servers within the
`intemetwork. All mapping changes converge within the replication period for the entire WINS
`system, which is the maximum time for propagating changes to all WINS sewers. All released
`names are propagated to all WINS servers after they become extinct, based on the inten/al
`specified in WINS Manager.
`
`Replication is carried out among replication partners, rather than each sen/er replicating to all
`other servers. In the following illustration, Senrerl has only Server2 as a partner, but Server2 has
`three partners. So, for example, Server1 gets all replicated information from Server2, but Server2
`gets information from Server1, Server3, and Sen/er4.
`
`
`
`Replication Configuration Example for WINS Servers
`
`Ultimately, all replications are pulled from the other WINS sen/ers on an intemetwork, but triggers
`are sent by WINS sen/ers to indicate when a replication should be pulled. To achieve replication,
`each WINS sewer is a push partner or pull partner with at least one other WINS server. A pull
`partner is a WINS server that pulls in database replicas from its push partner by requesting and
`then accepting replicas of new database entries in order to synchronize its own database. A push
`partner is a WINS server that sends notification of changes and then sends replicas to its pull
`partner upon receiving a request. When the server's pull partner replicates the information, it pulls
`replicas by asking for all records with a higher version number than the last record stored from the
`last replication for that server.
`
`Choosing whether to configure another WINS server as a push partner or pull partner depends on
`several considerations, including the specific configuration of servers at your site, whether the
`partner is across a wide area network (WAN), and how important it is to propagate the changes.
`
`I
`
`I
`
`If Server2, for example, needs to perform pull replications with ServerB, make sure it is a push
`partner of Server3.
`
`If Server2 needs to push replications to Server3, it should be a pull partner ofW|NS ServerB.
`
`Replication is triggered when a WINS server polls another server to get a replica. This can begin at
`system startup and can also be at a specific time, and it can then repeat at the time interval
`specified for periodic replication. Replication is also triggered when a WINS server reaches a
`threshold set by the administrator, which is an update count for registrations and changes. In this
`case, the sewer notifies its pull partners that it has reached this threshold, and the other servers
`may then decide to pull replicas.
`
`Page 159 of 315
`
`Verizon Exhibit 1006
`
`

`
`I To add a replication partner for a WINS sewer
`
`1.
`
`From the Server menu, choose the Replication Partners command.
`
`This command is available only if you are logged on as a member of the Administrators group
`for the local server.
`
`
`
`2.
`
`3.
`
`In the Replication Partners dialog box, choose the Add button.
`
`In the Add WINS Server dialog box, type the name or IP address of the WINS server that you
`want to add to the list, and then choose the OK button. If WINS Manager can find this server,
`it will add it to the WINS Sewer list in the Replication Partners dialog box.
`
`4. From the WINS Server list in the Replication Partners dialog box, select the server you want
`to configure, and then complete the actions described in "Configun'ng Replication Partner
`Properties" later in this chapter.
`
`5.
`
`If you want to limit which WINS servers are displayed in the Replication Partners dialog box,
`check or clear the options as follows:
`
`I Check Push Partners to display push partners for the current WINS server.
`
`I Check Pull Partners to display pull partners for the current WINS server.
`
`I Check Other to display the WINS servers that are neither push partners nor pull partners
`for the current WINS server.
`
`6. To specify replication triggers for the partners you add, follow the procedures described in
`"Tn'ggering Replication Between Partners" later in this chapter.
`
`7. When you finish adding replication partners, choose the OK button.
`
`I To delete replication partners
`
`1.
`
`2.
`
`From the Server menu, choose the Replication Partners command.
`
`In the Replication Partners dialog box, select one or more servers in the WINS Sewer list, and
`then choose the Delete button, or press DEL.
`
`WINS Manager asks you to confirm the deletion if you checked the related confirmation option
`in the Preference dialog box, as described in "Setting Preferences for WINS Manager" later in
`this chapter.
`
`Page 160 of 315
`
`

`
`Configuring Replication Partner Properties
`When you designate replication partners, you need to specify parameters for when replication will
`begin.
`
`I To configure replication partners for a WINS server
`
`1.
`
`In the WINS Sewer list of the Replication Partners dialog box, select the server you want to
`configure.
`
`2. Check either Push Partner or Pull Partner or both to indicate the replication partnership you
`want, and then choose the related Configure button.
`
`3. Complete the entries in the appropriate Properties dialog box, as described in the following
`procedures.
`
`I To define pull partner properties
`
`1.
`
`In the Start Time box of the Pull Partner Properties dialog box, type a time to indicate when
`replication should begin.
`
`You can use any separator for hours, minutes, and seconds. You can type AM or PM, for
`example, only if these designators are part of your time setting, as defined using the
`International option in Control Panel.
`
`Ept Default Value:
`
`2.
`
`In the Replication Interval box, type a time in hours, minutes, and seconds to indicate how
`often replications will occur, or use the spin buttons to set the time you want.
`
`If you want to return to the values specified in the Preferences dialog box, choose the Set
`Default Values button.
`
`3. Choose the OK button to return to the Replication Partners dialog box.
`
`I To define push partner properties
`
`1.
`
`In the Update Count box of the Push Partner Properties dialog box, type a number for how
`many additions and updates made to records in the database will result in changes that need
`replication. (Replications that have been pulled in from partners do not count as insertions or
`updates in this context.)
`
`The minimum value for Update Count is 5.
`
`‘fie! Default Value ‘
`
`Page 161 of 315
`
`

`
`If you want to return to the value specified in the Preferences dialog box, choose the Set
`Default Values button.
`
`2. Choose the OK button to return to the Replication Partners dialog box.
`
`Triggering Replication Between Partners
`You can also replicate the database between the partners immediately, rather than waiting for the
`start time or replication interval specified in the Preference dialog box, as described in "Setting
`Preferences for WINS Manager" later in this chapter.
`
`You will probably want to begin replication immediately after you make a series of changes such
`as entering a range of static address mappings.
`I To send a replication trigger
`I In the Replication Partners dialog box, select the WINS servers to which you want to send a
`replication trigger, and then choose the Push or Pull button, depending on whether you want
`to send the trigger to push partners or pull partners.
`
`Optionally, you can check the Push With Propagation box if you want the selected WINS
`server to propagate the trigger to all its pull partners.
`
`If Push With Propagation is not checked, the selected WINS server will not propagate the
`trigger to its other partners.
`I If Push With Propagation is checked, the selected WINS server sends a propagate push
`trigger to its pull partners after it has pulled in the latest information from the source WINS
`server. If it does not need to pull in any replicas because it has the same or more
`up-to-date replicas than the source WINS server, it does not propagate the trigger to its
`pull partners.
`
`start replication immediately
`
`In the Replication Partners dialog box, choose the Replicate Now button.
`
`Page-«—5
`
`

`
`Installing and Configuring WINS Servers
`Managing Static Mappings
`
`8of27
`
`Static mappings are permanent lists of computer name-to-lP address mappings that cannot be
`challenged or removed, except when the administrator removes the specific mapping. You use the
`Static Mappings command in WINS Manager to add, edit, import, or delete static mappings for
`clients on the network that are not WINS enabled.
`
`Important
`If DHCP is also used on the network, a reserved (or static) IP address will override any WINS
`server settings. Static mappings should not be assigned to WINS-enabled computers.
`
`I To view static mappings
`
`1.
`
`From the Mappings menu, choose the Static Mappings command.
`
`Close
`
`Efll Filler...
`
`Elnar Fillul
`
`‘.I_‘ll_du;l.i_aI‘apni'nga.“..i
`
`7
`
`I1
`
`lgplrl Mappings...
`
`gdil llapping... _.
`
`Quinta flapping
`
`Caution
`
`You cannot cancel changes made to the WINS database while working in the Static
`Mappings dialog box. You must manually delete any entries that are added in error or
`manually add back any entries that you mistakenly delete. This is because all changes to the
`WINS database made in this dialog box take effect immediately.
`
`2.
`
`In the Static Mappings dialog box, select a Sort Order option, either by IP address or by
`oomputer name. This selection determines the order in which entries appear in the list of
`static mappings.
`
`3. To edit or add a mapping, follow the procedures described in "Adding Static Mappings" and
`"Editing Static Mappings" later in this chapter.
`
`4. To remove existing static mappings, select the mappings you want to delete from the list, and
`then choose the Delete Mapping button.
`
`Page 163 of 315
`
`

`
`5. To limit the range of mappings displayed in the list of static mappings, choose the Set Filter
`button and follow the procedure in "Filtering the Range of Mappings" later in this chapter. To
`turn off filtering, choose the Clear Filter button.
`
`6. When you finish viewing or changing the static mappings, choose the Close button.
`
`
`
`Page—I3I6
`
`

`
`Installing and Configuring WINS Servers
`Managing Static Mappings
`
`Adding Static Mappings
`
`9of2T
`
`You can add static mappings to the WINS database for specific IP addresses using two methods:
`
`I
`
`I
`
`Type static mappings in a dialog box
`
`Import files that contain static mappings
`
`I To add static mappings to the WINS database by typing entries
`
`1.
`
`In the Static Mappings dialog box, choose the Add Mappings button.
`
`
`
`2.
`
`In the Name box of the Add Static Mappings dialog box, type the computer name of the
`system for which you are adding a static mapping. (If you want, you do not need to type two
`backslashes, because WINS Manager will add these for you.)
`
`3.
`
`In the IP Address box, type the address for the computer.
`
`If Internet Group or Multihomed is selected as the Type option, the dialog box shows
`additional controls for adding multiple addresses. Use the down-arrow button to move the
`address you type into the list of addresses for the group. Use the up-arrow button to change
`the order of a selected address in the list.
`
`4. Select a Type option to indicate whether this entry is a unique name or a kind of group with a
`special name, as described in the following list.
`
`Type option
`
`Meaning
`
`Unique
`
`Group
`
`Internet group
`
`Unique name in the database, with one address per
`name.
`
`Normal group, where addresses of individual members
`are not stored. The client broadcasts name packets to
`normal groups.
`
`Groups with NetB|OS names that have 0x1C as the
`16th byte. An intemet group stores up to 25 addresses
`for members. The maximum number of addresses is
`
`25. For registrations after the 25th address, WINS
`overwrites a replica address or, if none is present, it
`overwrites the oldest registration.
`
`Page 165 of 315
`
`

`
`Multihomed
`
`Unique name that can have more than one address
`(multihomed computers). The maximum number of
`addresses is 25, For registrations afler the 25th
`address, WINS overwrites a replica address or, if none
`is present, it overwrites the oldest registration.
`
` group names defined in this dialog box (that is, added statically), make sure that
`
`the primary domain controller (PDC) for that domain is defined in the group if the PDC is
`running Windows NT Advanced Server version 3.1.
`
`For more information, see "Managing Special Names" later in this chapter.
`
`5. Choose the Add button.
`
`The mapping is immediately added to the database for that entry, and then the boxes are
`cleared so that you can add another entry.
`
`6. Repeat this process for each static mapping you want to add to the database, and then
`choose the Close button.
`
` h static mapping is added to the database when you choose the Add button, you
`
`cannot cancel work in this dialog box. if you make a mistake in entering a name or address
`for a mapping, you must return to the Static Mappings dialog box and delete the mapping
`there.
`
`You can also import entries for static mappings for unique and special group names from any file
`that has the same format as the LMHOSTS file (as described in Chapter 6, "Setting Up
`LMHOSTS"). Scope names and keywords other than #DOM are ignored. However, normal group
`and multihomed names can be added only by typing entries in the Add Static Mappings dialog
`box.
`
`. To import a file containing static mapping entries
`1.
`In the Static Mappings dialog box, choose the Import Mappings button.
`
`2.
`
`In the Select Static Mapping File dialog box, which is similarto the standard Windows NT
`Open dialog box, specify a filename for a static mappings file by typing its name in the box, or
`select one or more filenames in the list, and then choose the OK button to import the tile.
`
`The specified file is read, and a static mapping is created for each computer name and address. If
`the #DOM keyword is included for any record, an internet group is created (if it is not already
`present), and the address is added to that group.
`
`
`
`Page—l3I5
`
`

`
`Installing and Configuring WINS Servers
`
`10 of27
`
`Managing Static Mappings
`
`Editing Static Mappings
`
`You can change the IP addresses in static mappings owned by the WINS server you are currently
`administering.
`
`I To edit a static mapping entry
`
`1.
`
`in the Static Mappings dialog box, select the mapping you want to change and choose the
`Edit Mapping button, or double-click the mapping entry in the list.
`
`
`
`You can view, but not edit, the Computer Name and Mapping Type option for the mapping in
`the Edit Static Mappings dialog box.
`
`2.
`
`In the IP Address box, type a new address for the computer, and then choose the OK button.
`
`The change is made in the WINS database immediately.
`
`Note
`
`If you want to change the computer name or group type related to a specific IP address, you must
`delete the entry and redefine it in the Add Static Mappings dialog box.
`
`
`
`Page 167 of 315
`
`

`
`l‘
`
`Installing and Configuring WINS Servers 11 of27
`
`Managing Static Mappings
`
`Filtering the Range of Mappings
`
`You may want to limit the range of IP addresses or computer names displayed in the Static
`Mappings or Show Database dialog boxes.
`
`You can specify a portion of the computer name or IP address or both when filtering the list of
`mappings.
`
`I To filter mappings by address or name
`
`1.
`
`In the dialog box for Static Mappings or Show Database, choose the Set Filter button.
`
`
`
`2.
`
`In the Set Filter dialog box, type portions of the computer name, address, or both in the
`Computer Name or IP Address boxes.
`
`You can use the asterisk (*) wildcard for poltions of the name or address or both. For
`example, you could type \\acct* to filter all computers with names that begin with acct.
`However, for the address, a wildcard can be used only for a complete octet. That is, you can
`type 11.101.*.*, but you cannot enter 11.1*.1.1 in these boxes.
`
`3. Choose the OK button.
`
`The selected range is displayed in the Static Mappings or Show Database dialog box. The
`filtered range will remain until you clear the filter.
`
`A message will tell you if no mappings are found to match the range you specified, and the
`list of mappings will be empty.
`
`If a filter is in effect for the range of mappings, the Clear Filter button is available for restoring the
`entire list.
`
`I To clear the filtered range of mappings
`
`I
`
`In the Static Mappings or Show Database dialog box, choose the Clear Filter button.
`
`The list now shows all mappings found in the database.
`
`Page 168 of 315
`
`

`
`
`
`Page‘ ('3!
`
`

`
`
`
` anaging tatlc Mappings
`Managing Special Names
`
`WINS recognizes special names for several types of groups, including a normal group,
`multihomed, and internet group. This section describes these groups and presents some
`background details to help you understand how WINS manages these groups.
`
`Normal Group Names
`A group name does not have an address associated with it. It can be valid on any subnet and can
`be registered with more than one WINS server. A group's timestamp shows the last time for any
`change received for the group. If the WINS server receives a query for the group name, it returns
`FFFFFFFF (the limited broadcast address). The client then broadcasts on the subnet. The group
`name is renewed when any member of the group renews the group name.
`
`Multihomed Names
`
`A multihomed name is a single, unique name storing multiple addresses. A multihomed device is
`a computer with multiple network cards and/or multiple IP addresses bound to NetB|OS over
`TCP/IP. A multihomed device with multiple IP addresses can register one or more addresses by
`sending one address at a time in a special name registration packet. A multihomed name in a
`WINS database can have one or more addresses. The timestamp for the record reflects any
`changes made for any members of the name.
`
`Each multihomed group name can contain a maximum of 25 IP addresses.
`
`When you configure TCP/IP manually on a Windows NT computer, you use the Advanced
`Microsoft TCP/IP dialog box to specify the IP address and other information for each adapter on a
`multihomed computer.
`
`Internet Group Names
`The internet group name is read as configuration data. When dynamic name registrations for
`internet groups are received, the actual address (rather than the subnet broadcast address) is
`stored in the group with a timestamp and the owner ID, which indicates the WINS server
`registering that address.
`
`The internet group name (which has a 16th byte ending in 0x1C reserved for domain names, as
`described in the following section) can contain a maximum of 25 IP addresses for primary and
`backup domain controllers in a domain. Dynamically registered names are added if the list is not
`static and has fewer than 25 members. If the list has 25 members, WINS removes a replica
`member (that is, a member registered by another WINS server) and adds the new member. If all
`members are owned by this WINS server, the oldest member is replaced by the new one.
`
`WINS gives precedence over remote members to members in an internet group name that
`registered with it. This preference means that the group name always contains the geographically
`closest Windows NT Server computers. To establish the preference of members of internet groups
`registered with other WINS servers under the \Partners\Pu|| key in the Registry, a precedence is
`assigned for each WINS partner as a value of the MemberPrec Registry parameter. Preference
`should be given to WINS servers near the WINS server you are configuring. For more information
`about the value of this parameter, see its entry in "Advanced Configuration Parameters for WINS"
`later in this chapter.
`
`The internet group name is handled specially by WINS, which returns the 24 closest Windows NT
`Server computers in the domain, plus the domain controller. The name ending in 1C is also used
`to discover a Windows NT Server computer in a domain when a computer running Windows NT
`Workstation or Windows NT Server needs a server for pass-through authentication.
`
`Page—l3I5
`
`

`
`If your network still has domain controllers running Windows NT Advanced Server version 3.1 to be
`included in the Internet group name, you must add these to the group manually using WINS
`Manager. When you manually add such a computer to the internet group name, the list becomes
`static and no longer accepts dynamic updates from WINS-enabled computers.
`
`For information about related issues in LMHOSTS for #DOM entries, see "Designating Domain
`Controllers Using #DOM" in Chapter 6, "Setting Up LMHOSTS."
`
`How WINS Handles Special Names
`Special names are indicated by a 16th byte appended to the computer name or domain name.
`The following table shows some special names that can be defined for static entries in the Add
`Static Mappings dialog box.
`
`Special Names for Static Mappings
`Name
`Usage
`ending
`
`How WINS handles queries
`
`WINS always returns the limited
`broadcast address (FFFFFFFF).
`
`0x1E
`
`0x1D
`
`A normal group. Browsers
`broadcast to this name and
`listen on it to elect a master
`browser. The broadcast is
`done on the local subnet and
`should not cross routers.
`
`Clients resolve this name to WINS always returns a negative
`access the master browser
`response. If the node is h-node or
`for server lists. There is one
`m-node, the client broadcasts a
`master browser on a subnet.
`name query to resolve the name.
`For registrations, WINS returns a
`positive response even though the
`names are not put into the
`database.
`
`0x1C
`
`The internet group name,
`which contains a list of the
`
`specific addresses of
`systems that have registered
`the name. The domain
`
`controller registers this name.
`
`WINS treats this as an internet
`group, where each member of the
`group must renew its name
`individually or be released. The
`internet group is limited to 25
`names. (Note, however, that there
`is no limit for #DOM entries in
`LMHOSTS.)
`
`WINS returns a positive response
`for a dynamic registration of a static
`1C name, but the address is not
`added to the list. When a static 1C
`
`name is replicated that clashes
`with a dynamic 1C name on
`another WINS server, a union of the
`members is added, and the record
`is marked as static.
`
`The following illustrates a sample NetBlOS name table for a Windows NT Server domain controller,
`such as the list that appears if you type nbtstat -n at the command prompt. This table shows the
`16th byte for special names, plus the type (unique or group).
`NetBIOS Local Name Table
`
`Name
`<OC29870B>
`
`ANNIEP5
`
`ANNIEP5
`
`<Z0>
`
`<00>
`
`ANNIEPDOM <00>
`
`ANNIEPDOM <I(>
`
`Type
`UNIQUE
`
`UNIQUE
`
`UNIQUE
`
`GROUP
`
`GROUP
`
`Status
`Registered
`
`Rcgistcrcd
`
`Registered
`
`Registered
`
`Registered
`
`Page—I3I5
`
`

`
`ANNIEPDOM <1B>
`
`ANNIEP5
`
`ANNLEP5
`
`ANNLEP5
`
`<O3>
`
`<1 E>
`
`<1 D>
`
`.._MSBROWSE<O l>
`
`UNIQUE
`
`UNIQUE
`
`GROUP
`
`UNIQUE
`
`GROUP
`
`Registered
`
`Registered
`
`Registered
`
`Registered
`
`Registered
`
`Example NetBlOS Name Table for a Windows NT Domain Controller
`
`As shown in this example, several special names are identified for both the computer and the
`domain. These special names include the following:
`
`0x0 (shown as <0O> in the example), the redirector name, which is used with net view.
`
`0x3, the Messenger service name for sending messages.
`
`_MSBROWSE_, the name master browsers broadcast to on the local subnet to announce
`their domains to other master browsers. WINS handles this name by returning the broadcast
`address FFFFFFFF.
`I Ox1B, the domain master browser name, which clients and browsers use to Contact the
`domain master browser. A domain master browser gets the names of all domain master
`browsers. When WINS is queried for the domain master browser name, it handles the query
`like any other name query and returns its address.
`
`WINS assumes that the computer that registers a domain name with the 1B character is the
`domain controller. This name is registered by the browser running on the domain controller.
`This ensures that the domain controller is in the internet group name list that is returned when
`a 1C name is queried, for which WINS always returns the address of the 1B name along with
`the members of a 1C name.
`
`
`
`Page—<I3I5
`
`

`
`.1‘.
`
`Installing and Configuring WINS Servers 13 of27
`
`Setting Preferences for WINS Manager
`
`You can configure several options for administration of WINS servers. The commands for
`controlling preferences are on the Options menu.
`
`I To display the status bar for help on commands
`I
`From the Options menu, choose the Status Bar command.
`
`When this command is active, its name is checked on the menu, and the status bar at the
`bottom of the WINS Manager window displays descriptions of commands as they are
`highlighted in the menu bar.
`
`I To set preferences for WINS Manager
`
`1.
`
`From the Options menu, choose the Preferences command.
`
`2. To see all the available preferences, choose the Partners button in the Preferences dialog box.
`
`1
`
`3. Select an Address Display option to indicate how you want address information to be
`displayed throughout WINS Manager-as computer name, IP address, or an ordered
`combination of both.
`
`Note
`
`Remember that the kind of address display affects how a connection is made to the WINS
`server - for IP addresses, the connection is made via TCP/IP; for computer names, the
`connection is made via named pipes.
`
`4. Check Auto Refresh if you want the statistics in the WINS Manager window to be refreshed
`automatically. Then enter a number in the Interval box to specify the number of seconds
`
`Page 173 of 315
`
`

`
`between refresh actions.
`
`WINS Manager also refreshes the statistical display automatically each time an action is
`initiated while you are working in WINS Manager.
`
`5. Check the LAN Manager-Compatible check box if you want computer names to adhere to the
`LAN Manager naming convention.
`
`LAN Manager computer names are limited to 15 characters, as opposed to 16-character
`NetB|OS names used by some other sources, such as Lotus Notes®. In LAN Manager
`names, the 16th byte is used to indicate whether the device is a server, workstation,
`messenger, and so on. When this option is checked, WINS adds and imports static
`mappings with 0, 0x03, and 0x20 as the 16th byte.
`
`All Windows networking, including Windows NT, follows the LAN Manager convention. So this
`box should be checked unless your network accepts NetB|OS name from other sources.
`
`6. Check Vaiidate Cache Of Known WINS Servers At Startup Time if you want the system to
`query the list of servers each time the system starts to find out if each server is available.
`
`7.
`
`8.
`
`9.
`
`If you want a warning message to appear each time you delete a static mapping or the
`cached name of a WINS server, check the Confirm Deletion Of Static Mappings And Cached
`WINS Servers option.
`
`In the Start Time box, type a time to specify the default for replication start time for new pull
`partners. Then specify values for the Replication interval to indicate how often data replicas will
`be exchanged between the partners.
`
`The minimum value for the Replication Interval is 40 minutes.
`
`In the Update Count box, type a number to specify a default for how many registrations and
`changes can occur locally before a replication trigger is sent by this server when it is a push
`partner. The minimum value is 5.
`
`10. When all options are set for your preferences, choose the OK button.
`
`
`
`Page—I3I6
`
`

`
`
`
` Managing the WINS Database
`
`The following files are stored in the \systemroot\SYSTEM32\W|NS directory that is created when
`you set up a WINS server:
`I JET.LOG is a log of all transactions done with the database. This file is used by WINS to
`recover data if necessary.
`
`SYSTEM.MDB is used by WINS for holding information about the structure of its database.
`W|NS.MDB is the WINS database file.
`
`WINSTMP.MDB is a temporary file that WINS creates. This file may remain in the \WlNS
`directory after a crash.
`
`You should back up these files when you back up other files on the WINS server.
`
`“e
`
`I .|:OG. SYSTEM.MDB, WINSMDB, and W|NSTMP.MDB files should not be removed or
`
`tampered with in any manner.
`
`Like any database, the WINS database of address mappings needs to be cleaned and backed up
`periodically. WINS Manager provides the tools you need for maintaining the database. This
`section describes how to scavenge (clean), view, and back up the database. For information on
`restoring and moving the WINS database, see "Troubleshooting WINS" later in this chapter.
`
`
`
`Pagel <I3I5
`
`

`
` Managing the WINS Database
`
`Scavenging the Database
`
`The local WINS database should periodically be cleared of released entries and old entries that
`were registered at another WINS server but did not get removed from this WINS database for
`some reason. This process, called scavenging, is done automatically over intervals defined by the
`relationship between the Renewal and Extinct intervals defined in the Configuration dialog box.
`You can also clean the database manually.
`
`For example, if you want to verify old replicas immediately instead of waiting the time interval
`specified for verification, you can manually scavenge the database.
`
`scavenge the WINS database
`
`From the Mappings menu, choose the Initiate Scavenging command.
`
`The database is cleaned, with the results as shown in the following table.
`
`State before scavenging
`Owned active names for which
`
`State after scavenging
`Marked released
`
`the Renewal interval has expired
`Owned released name for which
`
`the Extinct interval has expired
`Owned extinct names for which
`
`the Extinct timeout has expired
`
`Replicas of extinct names for which
`the Extinct timeout has expired
`
`Marked extinct
`
`Deleted
`
`Deleted
`
`Replicas of active names for which
`the Verify interval has expired
`Replicas of extinct or deleted names Deleted
`For information about the intervals and timeouts that govern database scavenging, see
`"Configuring WINS Servers" earlier in this chapter.
`
`Revalidated
`
`After WINS has been running for a while, the database may need to be compacted to improve
`WINS performance.
`
`. To compact the WINS database
`
`1. At the WINS server, stop the Windows Internet Name Service using the Control Panel
`Services option or by typing net stop wins at the command prompt.
`
`2. Run COMPACT.EXE (which is found in the \systemroot\SYSTEM32 directory).
`
`3. Restart the Windows Internet Name Service on the WINS server.
`
`Pagel <I3I5
`
`

`
`
`
`Page -3!
`
`

`
`.
`r
`
`
`Installing and Configuring WINS Servers
`Managing the WINS Database
`
`16of27
`
`Viewing the WINS Database
`
`You can view the actual active and static mappings stored in the WINS database, based on the
`WINS server that owns the entries.
`
`I To view the WINS database
`
`1.
`
`From the Mappings menu, choose the Show Database command.
`
`-IllHI-
`
`‘I
`
`|i.1hq, 1.
`
`Display 0ptions
`Ur-mer
`
`0 15_how All I-v|anig_ir_ngr_§_____
`'5}§'Show
`Mappings
`'-
`.
`Select Qwnet
`
`Filter: None
`
`Mgppings
`\\--_MSBFIOWSE__[01h] 11 103.41.12
`Vi‘ \\A-ANNIEP2[00h]
`11.103.41.12
`\'IA—ANN|EP2[03h]
`11.103.41.12
`
`\\.A-ANNIEP2[20h]
`
`11.103.41.12
`
`. VIA-A.NN|EPDt]H[00h|
`\'t.A-ANNlEPI)l]H[1Bh]
`guui-ANN|EPDUH[1Ch]
`‘@,\\.A-ANNIEPI)0H[1Eh]
`
`11.103.41.12
`11.103.41.12
`11.10141 12
`11.103.41.12
`
`Sort Order
`
`‘
`
`C) Sort by l_P Address
`(Q So“ by Compute! Name—
`0 Sort by limestamp
`
`0 Sort by ‘iersion ID
`C) Sort by Type
`
`S Timestamp
`5I20l84 4:14:49 PM
`5/20/94 4:14:50 PM
`5/20/94 4:14:49 PM
`5120/94 4:14:50 PM
`5/20/94 4:14:49 PM
`5l20!S4 4:14:49 PM
`5!20!S4 4:14:49 PM
`5a'20!El4 4:14:49 PM
`
`Kflkkkkkkh
`
`5_et I-‘liter. ..
`— 7 —_
`l_in:.n I-rllur
`. _-_
`__-_-_..-.
`’l'',' h
`L
`flan“ '
`Qelele Owner - 1
`
`Version ID
`
`-iwr~a.i-.m-Luca
`
`2.
`
`In the Show Database dialog box, to view the mappings in the database for a specific WINS
`server, select Show Only Mappings From Specific Owner, and then from the Select Owner
`list, select the WINS server whose database you want to view.
`
`By default, the Show Database dialog box shows all mappings for the WINS database on the
`currently selected WINS server.
`
`3. Select a Sort Order option to sort by IP address, computer name, timestamp for the mapping,
`version ID, or type. (For information about types, see "Adding Static Mappings" earlier in this
`chapter.)
`
`4.
`
`If you want to view only a range of mappings, choose the Set Filter button and follow the
`procedures described in "Filtering the Range of Mappings" earlier in this chapter. To turn off
`filtering, choose the Clear Filter button.
`
`5. Use the scroll bars in the Mappings box to view entries in the database. Then choose the
`
`Page 178 of 315
`
`

`
`Close button when you are finished viewing.
`
`As shown in the Mappings list, each registration record in the WINS database includes these
`elements:
`
`Item
`
`Meaning
`
`Unique
`
`Group, intemet group, or multihomed
`
`Computer name The NetBIOS computer name.
`IP address
`The assigned lnternet Protocol address.
`
`A or 3
`
`Timestamp
`
`Version ID
`
`Whether the mapping is

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