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

  • Thread starter Thread starter J.H
  • Start date Start date
J

J.H

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
 
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.
 
Hi Joe,

Thanks for your reading,

Here the original posted (it was posted 2 or 3 times, but not finding any
solution yet!!!)
****************************************************************
After the seizure operation to replace the 1st DC downed by 2nd DC,
The WINS on 2nd DC does not have the [1ch] Domain Controller record type
any more (can not be automatically created, but not prefer to manually
created)
I had to add another DC to the domain and install the WINS, so the WINS on
3rd DC now has the record [1ch] Domain Controller record type.
DC the 2nd DC is supposed to have [1ch] Domain Controller record type in its
WINS, but it won't. Now the new added 3rd DC has [1ch] Domain Controller
record type, it is weird to me that [1ch] can never be created on 2nd DC's
WINS (automatically)
****************************************************************

As the MSFT support site states that there are up to 24 [1ch] record can be
registered,
very 1st one will be the DC holding 5 FSMO roles, the rests of 23 x [1ch]
will be additional
domain controllers. I could not find any solution to get back [1ch] record
to register in its wins
even it was pointed to itself already (tried nbtstat -RR, not working, refer
not manually created
the [1ch] record!!).

Thanks all,
J.H

Joe Richards said:
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 said:
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
Click to expand...
Click to expand...
 
I wasn't asking for you to post again. This is what I read before and it is
still confusing. Answer the specific questions asked.



--
www.joeware.net


J.H said:
Hi Joe,

Thanks for your reading,

Here the original posted (it was posted 2 or 3 times, but not finding any
solution yet!!!)
****************************************************************
After the seizure operation to replace the 1st DC downed by 2nd DC,
The WINS on 2nd DC does not have the [1ch] Domain Controller record type
any more (can not be automatically created, but not prefer to manually
created)
I had to add another DC to the domain and install the WINS, so the WINS on
3rd DC now has the record [1ch] Domain Controller record type.
DC the 2nd DC is supposed to have [1ch] Domain Controller record type in its
WINS, but it won't. Now the new added 3rd DC has [1ch] Domain Controller
record type, it is weird to me that [1ch] can never be created on 2nd DC's
WINS (automatically)
****************************************************************

As the MSFT support site states that there are up to 24 [1ch] record can be
registered,
very 1st one will be the DC holding 5 FSMO roles, the rests of 23 x [1ch]
will be additional
domain controllers. I could not find any solution to get back [1ch] record
to register in its wins
even it was pointed to itself already (tried nbtstat -RR, not working, refer
not manually created
the [1ch] record!!).

Thanks all,
J.H

Joe Richards said:
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 said:
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,
Click to expand...
Click to expand...
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
Click to expand...
Click to expand...
Click to expand...
 
Back
Top