To resolve "duplicate name" error messages
· Check the WINS database for the entries for that name that have a static name -to-IP-address mapping. If there is a static address record, delete it from the WINS server database.
Or, set the value of MigrateOn in the Registry equal to 1, so that the static records in the database can be updated by dynamic registrations (after the WINS server successfully challenges the old address).
To locate the source of "network path not found" error messages on a WINS client
· Check the WINS database for the name. If the name is not present in the database, check whether the destination or target computer uses b-node name resolution. If so, add a static mapping for it in the WINS database.
If the computer is configured as p-node, m-node, or h-node, and if its IP address is different from the one in the WINS database, then it may be that its address changed recently and the new address has not yet replicated to the local WINS server. To get the latest records, ask the WINS server that registered the address to perform a push replication with propagation to the local WINS server.
To discover why a WINS server cannot pull or push replications to another WINS server
1. Use the ping utility to verify that each WINS server is running and can be connected to.
2. Ensure that each server is correctly configured as both a pull and push partner.
To determine the configuration of a replication partner, check the values under the Pull and Push keys in the Registry.
To determine why WINS backup fails
· Make sure the path for the WINS backup directory is on a local disk on the WINS server.
WINS cannot back up its database files to a remote drive.