Configuring Replication Across LANs

  • Article

Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2

When configuring WINS replication across LANs, the issues are similar to those that occur in WAN environments, although less critical.

Because the data throughput of the underlying network links for LANs is much greater than for WANs, it might be acceptable to increase the frequency of WINS database replication by specifying push and pull parameters for LAN-based replication partners. For push/pull partners, you can do this by decreasing the Number of changes in version ID before replication and Replication interval settings from what you use for WAN-based partners on slower links.

For example, between LAN-based replication partners it often works to enable WINS to use a persistent connection between the servers. Without a persistent connection, the normal update count threshold defaults to a minimum of 20. You can specify a smaller update count with a persistent connection.

Next, you can specify a much smaller number, such as a value of one to three in the Number of changes in version ID before replication setting before WINS sends a push replication trigger to the other partner. For pull partners, you might also consider setting the Replication interval setting to a value in minutes, instead of hours.

As in WAN replication planning, the WINS server database must replicate frequently enough to prevent the downtime of a single WINS server from affecting the reliability of the mapping information in other WINS servers. However, the time interval between replications cannot be so small that it interferes with network throughput.

In environments with a large amount of network traffic it is a good idea to use a network monitoring tool, such as Network Monitor, to help measure and determine how to optimize your WINS replication strategy.

For more information about WINS configuration across LANs, see "Configuring WINS replication" in Help and Support Center for Windows Server 2003. For more information about the Network Monitor tool, see "Network Monitor" in Help and Support Center for Windows Server 2003.