Using static mappings

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2, Windows Server 8 Beta

Using static mappings

Mapped name-to-address entries can be added to WINS in either of two ways:

• Dynamically, by WINS-enabled clients directly contacting a WINS server to register, release, or renew their NetBIOS names in the server database.

• Manually, by an administrator using the WINS console or command-line tools to add or delete statically mapped entries in the server database.

Static entries are only useful when you need to add a name-to-address mapping to the server database for a computer that does not directly use WINS. For example, in some networks, servers running other operating systems cannot register a NetBIOS name directly with a WINS server. Although these names might be added to and resolved from an Lmhosts file or by querying a DNS server, you might consider using a static WINS mapping instead.

Migrating static mappings to dynamic mappings

Unlike dynamic mappings, which can age and be automatically removed from WINS over time, static mappings can remain in WINS indefinitely unless administrative action is taken.

By default, if during an update process WINS is presented with both a static and dynamic-type entry for the same name, it preserves the static-type entry. You can, however, use the Overwrite unique static mappings at this server (migrate on) feature provided with WINS to change this behavior.

For example, the following graphic shows the default migration behavior for a WINS server, WINS-A, when presented with a registration request by a WINS client, Host C, that challenges a static mapping already in the server database.

In this example, WINS-A prevents the client from registering and updating the statically mapped information for Host C. In the next graphic, the same situation is repeated but in this example, the Migrate feature has been turned on at WINS-A.

As shown in the revised graphic, enabling the Migrate feature at WINS-A permits previously entered static mappings for Host B and C to be overwritten by WINS client computers that attempt to register dynamically and update entries for these same names. This feature is useful in simplifying the update of legacy NetBIOS b-node (broadcast-only) type clients that are later upgraded to support WINS.

Important

• Never add static mappings for computers that can directly use WINS. Doing so can cause undesirable problems, such as demanding additional work to migrate, delete, or tombstone these mappings in a replicated WINS environment.

Notes

• You can add static entries either interactively using the WINS console or command-based tools, or by importing an Lmhosts file.

• The Overwrite unique static mappings at this server (migrate on) feature was designed primarily to migrate records for older non-WINS clients that do not dynamically register themselves in WINS. Some special group names, such as domain [1Ch] names are not affected by this setting.