Discussion Locked

Wins Rebuild - Nbtstat -RR

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

BACKGROUND:
Our Wins is corrupt and we are going to start from scratch. We plan to stop all wins services, backup and delete %systemroot%\wins\*.* and restart. We have 200+ servers and Exchange running in a multiple master domain. Many servers are either at remote locations or should run 24/7. Instead of rebooting all servers to reregister with wins, We have a script the will start the schedule service remotely and run NBTSTAT -RR to reregister. TechNet Q228453 states NBTSTAT -RR does not increment the WINS ID and NTSP 6A fixes this.
However about 1/2 the servers are running NTSP5.

Question: If we wipe out the entire WINS database, is reregistering with the same WINS ID going to cause a problem?

My Take: It is my understanding that the ID is for consistency checking. Once deleted, nothing will be replicated to conflict. I don't think this will hurt us, however we want to do this right the first time.

Advise/experiences extremely welcome.

7 replies

by calves

I've done it more than a few times and I will give you my input.
After deleting the WINS and reboot, apply the SP b4 you re-install WINS. When re-installing WINS you'll receive an error message that WINS cannot find a certain folder (just don't remember exactly which), just go ahead and manually recreate the folder and WINS will work fine. As far as the servers, I strong recommend you to re-boot each and everyone of them for proper registration. Even you 24/7 servers needs a regular reboot tooperate properly, just make it now.

Good luck!

by singhjunk

If you wish to delete and recreate your WINS database, type the following at a command prompt:
net stop WINS
ren %SystemRoot%\System32\WINS\Wins.mdb %SystemRoot%\System32\WINS\Wins.old
net start WINS

But since you said you had computers at remote location it is quite sure that you were backing up your primary WINS server on
another Secondary Wins server and for that you have to be sure When a WINS server is removed from the replication network, its' entry is not removed from the WINS database of the other WINS servers. These entries are replicated indefinetly. You will need to remove them from there before you built a new wins server on the same machine.

Secondly are you absolutely sure that your data is corrupt because sometimes it is that
WINS does not start consistently and most of us assume that it is corrupt and which is very easy to troubleshoot.

Thanks

by aekland

We wiped ours because of possible corruption at Microsofts Suggestion. We have only two and wiped both and started fresh. All the servers are local and have the same primary wins, all were running SP5 at the time. There were no issues with the wipe and refres. We didn't reboot any of them at the time.

This discussion is closed to new replies.