Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

WINS Problems - Help!!

Status
Not open for further replies.

GSC

MIS
Joined
Mar 27, 2001
Messages
464
Location
EU
Hi,
Got a WINS issue with Event ID 4243.
Here's the story behind it. 3 days ago we had a router problem at one of our hubsites where the wins2 server resides. Today I have a lot of Admins calling regarding PC's that can't access the network due to duplicate name on the network.
Wins servers have been rebooted but still the issue is there.
What can I do??
Thanks in Advance
GSC
 
I'm not sure whats causing the error. Only thing I can think of is a screwed up WINS database. There may be another solution out there that could resolve your issue, but the only thing I can think of off the top of my head is to uninstall-reinstall WINS at the secondary site. I'd do this last, and see what some other people on the board have to say.

Out of curiosity, what name is in conflict on the client machines? (Run nbtstat -n from the command prompt

Take a look at this link. Its from It looks like you may have any overloaded WINS server. Hopefully this will help you out.

 
Thanks for the info SgtB,
I have actually already found out the root cause of the problem.
Our primary WINS servers WINS1 and WINS2 are replicating with hub sites in each country. Somebody added two additional WINS replication partners to our WINS1 and set the replication time to 30 minutes..........
Say no more huh??
Boy do I wish I was the BIG boss today, so i could kick some butt!!!
Thanks anyway.
GSC
 
As to the cause of the problem ?!?!?!

As to the cure, If you are at least SP6a on the WINS server, you can view the entries in the database and delete the offending entries with the GUI. If you do this, do not tombstone them, delete them, and do it on all WINS servers at the same time. You can then (if needed) as a static WINS entry on each machine to compensate short term. To keep yourself safe with the static entries, there is an option called "migrate on" that can be found under advanced options for each WINS server. When enabled this feature will allow you to create a static entry and have the device overwrite the static with an acive entry as soon as it tries to re-register with the WINS server.

If you are not at least SP6a (yuck) you will have to delete the entries from the command line on each server (I cannot remember how, but there is a Q article on Microsoft).

Hope that is helpful,
Jay Mosser
jaym@optymgroup.com
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top