none
Stale WINS 1C IP Address Entries

    Question

  • We used to have 16 domain controllers in our environment. Over the years, all but 4 have been decommissioned using dcpromo. Most are physically gone, but some do remain as regular domain member servers. We recently brought in some new hardware (EMC NAS devices) that appear to be getting domain controller information from WINS 1C records - the entries for the 12 now gone domain controllers are not in DNS. I can configure the NAS devices to use DNS, not WINS, but clearly these WINS entries should not be there to begin with.

    My question is, how can I edit/refresh the dynamic 1C entries in WINS for our domain to remove the stale IP Address entries? If I delete them, will they be re-created automatically? I have read that static WINS entries are not a good idea, especially for 1C records, so I would obviously like to avoid that route. Forgot to mention that our domain is 2003 domain functional level.

    Thanks for any guidance anyone can offer.

    • Edited by HillJack Monday, March 07, 2011 9:38 PM Forgot to mention 2003 domain
    Monday, March 07, 2011 9:34 PM

Answers

  • I have had a similar situation.  You should most definately NOT create static 1C records.  Please note while you make these changes, you WILL impact NETBIOS services on your network that depend on the 1C record so proceed during a scheduled maintenance window.  Quickest way to handle this is as follows:

    1) if you have more than 1 WINS server, you will need to break replication.
    2) Delete the 1C record from each WINS server
    3) Once you have verified that 1C is gone from each local DB, re-establish replication topology in WINS
    4) Make sure that your DCs have the correct WINS client configuration
    5) you should be able to force each DC to register by opening a command prompt and typing "nbtstat -RR".
    6) As long as you get at least one DC to register, you'll be good, the rest will update as time passes.


    Visit: anITKB.com, an IT Knowledge Base.
    • Proposed as answer by AwinishModerator Tuesday, March 08, 2011 6:14 AM
    • Marked as answer by HillJack Friday, March 11, 2011 3:44 PM
    Tuesday, March 08, 2011 2:28 AM

All replies

  • Are these 1C records are tombstoned?  When this record becomes tombstoned, ownership will change to that of the tombstoning WINS server. 

    Please test the following procedure in the lab first:

    ·       Delete the bad 1C record

    ·       Stop and start the Netlogon service on the WINS server – this will re-register the 1C entry. 


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX

    Blogs - http://blogs.sivarajan.com/
    Articles - http://www.sivarajan.com/publications.html
    Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara

    This posting is provided AS IS with no warranties, and confers no rights.
    Tuesday, March 08, 2011 1:35 AM
    Moderator
  • I have had a similar situation.  You should most definately NOT create static 1C records.  Please note while you make these changes, you WILL impact NETBIOS services on your network that depend on the 1C record so proceed during a scheduled maintenance window.  Quickest way to handle this is as follows:

    1) if you have more than 1 WINS server, you will need to break replication.
    2) Delete the 1C record from each WINS server
    3) Once you have verified that 1C is gone from each local DB, re-establish replication topology in WINS
    4) Make sure that your DCs have the correct WINS client configuration
    5) you should be able to force each DC to register by opening a command prompt and typing "nbtstat -RR".
    6) As long as you get at least one DC to register, you'll be good, the rest will update as time passes.


    Visit: anITKB.com, an IT Knowledge Base.
    • Proposed as answer by AwinishModerator Tuesday, March 08, 2011 6:14 AM
    • Marked as answer by HillJack Friday, March 11, 2011 3:44 PM
    Tuesday, March 08, 2011 2:28 AM
  • Thank you for the assistance. I've got an outage window for Thursday evening. I'll try to update on Friday or shortly thereafter. Hopefully there are no issues (our WINS environment is pretty rough as-is and is only still around for ancient legacy applications).

     

    Tuesday, March 08, 2011 6:25 PM
  • Again, the only thing I forsee is that you may impact systems looking for that 1C record if its not there.  I would try to get it all completed during that Thursday evening window.
    Visit: anITKB.com, an IT Knowledge Base.
    Tuesday, March 08, 2011 8:22 PM
  • Try the procedure on one WINS server first.  Please let us know the result. 


    Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX

    Blogs - http://blogs.sivarajan.com/
    Articles - http://www.sivarajan.com/publications.html
    Twitter: @santhosh_sivara - http://twitter.com/santhosh_sivara

    This posting is provided AS IS with no warranties, and confers no rights.
    Wednesday, March 09, 2011 2:32 AM
    Moderator
  • I followed the steps outlined above by JM and it appears to have worked; 1C records now contain the correct IP addresses (of only our 4 domain controllers). My changes seems to have passed the scream-test too. Hopefully this will cease the warning messages from the NAS servers. Thank you both for your help.
    Friday, March 11, 2011 3:44 PM