Re: *** AGAIN [1CH] record of 1st domain controller in WINS after seizure operation !!!! ANY ONE ??

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 02/10/04


Date: Mon, 9 Feb 2004 20:47:04 -0500

This post is EXTREMELY confusing to read.

It sounds like you have

1. a domain controller (DC1) that is also running the WINS Service.
2. Other domain controllers that point at some WINS Server (WINS1)

Is DC1 pointing to itself for its WINS entries or is it pointing at WINS1?

Is WINS1 and DC1 replicating WINS records between them with a push/pull?

If DC1 is not pointing at itself, point it at itself because it will NOT
register anywhere else if it is running WINS.

If you don't replicate the database between WINS1 and DC1 then you need to
turn off WINS on DC1 and point DC1 at WINS1.

-- 
www.joeware.net
"J.H" <jpthsd@hotmail.com> wrote in message
news:e6LDw717DHA.2480@TK2MSFTNGP10.phx.gbl...
> Dear All,
> (David - MSFT, might you help ?)
> (Briefing the old issue:
> After the seizure operation of downed 1st DC, another DC was seized to
> be taking over 5 roles, it has its own WINS & replicated WINS data from
> down 1st DC, but the seized DC has never registered itself [1ch] in its
> WINS.
> Any solutions ?, ,,, Thanks)
>
> I am recalling this issue, because it still had been an ISSUE !!
>
> So, is there any solution for re-registering [1ch] record 'Domain
> Controller' of our seized DC to the WINS ?
>
> MSFT said there can be 24 record of [1ch], the very first one will be the
> 1st DC, the rest of them will be other domain controllers.
>
> In my case, the seized domain controller can not register itself [1ch] to
> the WINS (WINS is running on this seized domain controller, perhaps, it is
> the reason, but I checked my lab server, the 1st dc with WINS always has
> [1ch] registerred itself).
>
> If I add additional domain controllers, the new domain controller will be
> registerred itself with [1ch] record domain controller in the seized
domain
> controller's WINS. That's strange.
>
> Do you have any solution for this typical issue David (or the other MSS
> forum online ?)
> Thankssssssssss !!!
>
> Any suggestion will be appreciated !!!!!
> Thanks,
> J.H
>
>


Relevant Pages

  • Re: Second domain controller does not take over in case the first fail
    ... Recently I did a test shutting down first our primary domain controller, ... which is both GC server and holds all the FSMO roles. ... local service credentials. ... DC1 was running perfectly at ...
    (microsoft.public.windows.server.active_directory)
  • Re: Demoting a DC in W2003
    ... forrest / single domain with three DCs. ... It's only role is being a DC and our primary internal DNS server. ... transfered the FSMO roles from DC1 to DC2 using the MS KB article 324801. ... The local domain controller has attempted to replicate the following object from the following source domain controller. ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain Mess - Problem promoting second server to DC
    ... > I was able to bring up a second domain controller on an old PC ... but DC1 died before I was able ... > the AD that was now running on DC2. ... > I installed DNS on DC2, and configured DC2 to use itself for DNS. ...
    (microsoft.public.windows.server.dns)
  • Re: Domain controller name -rename issue
    ... Because you did not know what your predecessor have done with the DC1 renaming, i would make sure that the correct existing DC2 have all 5 FSMO roles and is GC server and DNS with AD integrated zones only for the correct old named "domain" domain. ... AD users and computers and AD sites and services is cleaned up you can now promote the old DC1 again to domain controller. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Admin Account locked out every hour.
    ... The lockout originates from the domain controller DC1. ... I have checked schedule jobs in the ...
    (microsoft.public.windows.server.active_directory)