Troubleshooting WINS Servers
Troubleshooting WINS server problems can be largely avoided by making sure you understand and correctly set up and configure your WINS database topology. Following are a few key clues that you may come across that point to a server-side WINS problem. All of these were discussed throughout the chapter, so we just reference them here as things to be aware of when troubleshooting your WINS server. To go over the configuration steps refer back to the related section of the chapter.
■ WINS replication problems WINS replications problems can exist if you have incorrectly configured your replication partners. Remember that by default you must set up replication partners as two-way partners or replication will not work in either direction. Problems can occur if this is initially set up and then by accident someone deletes just one of the replication partners.
■ Static record issues Remember, static records should be used only for non-WINS related client information. By default, they are configured to overwrite the same dynamic records in replication if they exist. This can appear to be a replication or server problem, when it really is a design and configuration issue. If you want to make static records appear to act as dynamic records you can do so by enabling the Overwrite unique static mappings at this server (migrate on) setting option.
■ WINS server load problems When faced with an issue ofWINS server load, you must reconsider the default burst handling mode discussed earlier in this chapter. Burst handling should be set to a value that is tuned for the number of WINS clients each WINS server will be handling. If you are seeing issues where clients are unable to successfully register with WINS because the server is too busy, consider lowering your burst handling value. On the same note if you are experiencing problems with WINS clients not being able to successfully resolve NetBIOS names because a majority ofWINS clients are being deferred by the burst handling functionality, consider raising your burst handling value.
■ Rogue WINS servers Be careful of rogue WINS servers on your network when using the Automatic partner configuration option. If using this option, take advantage of the Accept records only for these owners option to narrow your chances of running into a rogue WINS server. Once replication happens with a rogue WINS server, your next step may be to restore from backup.
■ WINS Database problems Make sure you use one of the methods described in this chapter to back up your WINS database.You do not want to have 1500 WINS clients have to reregister with your new WINS server because you lost the database and had to create a new one from scratch. Be prepared and plan ahead. Backing up the database is not a tedious task and should be the second thing you set up after initial installation.
Post a comment