Re: RENDOM /end fails
- From: "Ace Fekay [Microsoft Certified Trainer]" <firstnamelastname@xxxxxxxxxxx>
- Date: Sat, 1 Nov 2008 11:15:01 -0400
In news:4A1CCE55-5A5E-49BC-8339-819D5766331F@xxxxxxxxxxxxx,
bytenik <bytenik@xxxxxxxxxxxxxxxxxxxxxxxxx> requesting assistance, typed the following:
I just noticed that desktop computers are getting errors as well in
the event log, referring to the old domain:
"Windows cannot connect to wtg.com domain. (Server Down). Group Policy
processing aborted. "
and also
"CN=David Pfeffer,OU=IT Department,DC=centralholidays,DC=com from a
different forest logged onto this machine. Cross Forest Group Policy
processing is disabled and loopback processing has been enforced in
this forest for this user account."
(This is from my desktop computer, and my name is David Pfeffer.)
Following is ipconfig /all from the domain controller. I only have one
actively running. The other one is gone and needs to be purged (which
I can't do until the domain rename is completed, because the forest
is currently frozen).
---
Windows IP Configuration
Host Name . . . . . . . . . . . . : WTGDC01
Primary Dns Suffix . . . . . . . : centralholidays.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : centralholidays.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
GigE (NDIS VBD Client)
Physical Address. . . . . . . . . : 00-19-B9-E5-F9-87
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.17.1.10
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.17.1.254
DNS Servers . . . . . . . . . . . : 10.17.1.7
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5708C NetXtreme II
GigE (NDIS VBD Client) #2
Physical Address. . . . . . . . . : 00-19-B9-E5-F9-89
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.247.241
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
Hi David,
I see two things amis. There are two NICs on a DC, which will cause issues, and the other DC has to be removed from AD's NTDS database.
1. You will need to disable the second NIC. In DNS, delete any reference you see to the 169.254.x.x addresses for the DC for host entries, the (same as parent) entries, and under the _gc._msdcs.centralholidays.com zone.
2. Go into Sites and Services, make sure this DC is a GC. Click on the current DC name, on the right you will see "NTDS" whcih you want to right-click on it choosing properties, make sure the checkbox is checked that it is a GC. If you see the old DC name in the list of servers, delete it.
2. After completing step 1, to properly re-register the SRVs, in a CMD prompt, run the following:
ipconfg /registerdns
net stop netlogon
net start netlogon
3. Follow the following article on how to check to see if the old DC is gone, and if not, how to remove it.
How to remove data in Active Directory after an unsuccessful domain controller demotion:
http://support.microsoft.com/kb/216498
Let me know how you make out. Also post any Event log errors (eventID # and the source Name) that exist under any of the logs.
Thanks.
--
Ace
.
- Follow-Ups:
- Re: RENDOM /end fails
- From: bytenik
- Re: RENDOM /end fails
- Prev by Date: RE: RODC Using VPN
- Next by Date: RE: RODC Using VPN
- Previous by thread: RE: RODC Using VPN
- Next by thread: Re: RENDOM /end fails
- Index(es):
Relevant Pages
|
Loading