Re: Global catalog server died before completing replication to new GC server
- From: Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>
- Date: Sun, 29 Mar 2009 10:25:33 +0000 (UTC)
Hello MickBurke,
Please post an unedited ipconfig /all from the DC and a problem machine.
What about the DNS zones,are all machines listed there?
What zones are listed there?
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
On Mar 28, 9:39 pm, Meinolf Weber [MVP-DS] <meiweb(nospam)@gmx.de>
wrote:
Hello MickBurke,Yup, the new server has all the FSMO roles set to it, I transferred
If no DNS is installed on the existing DC:
Install DNS role and create a forward lookup zone for your complete
domainname,
mydomain.local for example. Make it an AD integrated zone and also
create
a reverse lookup zone for your ip range, also AD integrated.
Then make sure all servers are listed in the zones, configure all
machines
to thenewDNSserveron the NIC, then run ipconfig /registerdns on them
after that. The DHCP client service has to run for DNS registration.
If all machines are listed in DNS, seize the 5 FSMO roles according
to this article:http://support.microsoft.com/kb/255504
Make itGlobalcatalogserver:http://support.microsoft.com/?id=313994
Cleanup the AD database from the crashed
DC:http://support.microsoft.com/kb/216498
Remove the crashed DC from AD sites and services, just delete the
servername there.
In the Exchange system manager reconfigure the "Recipient update
service" to the running DC for both entries.
After all run dcdiag /v and netdiag /v to check for errors.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
We had an old 2000serverthat was theglobalcatalogthat was making
drive noise, so we assigned anotherserveras theglobalcatalogand
moments later, the firstserverdied. NNow we've got all sorts of
trouble. From the clients we can't get to the roaming profiles, when
we connect to exchange (which is on thenewserver) it prompts for the
user password.
From tehnewserveritself, which had been a domain controller for
several months, we are getting problems when we run netdiag:
Domain membership test . . . . . . : Failed
[WARNING] Ths system volume has not been completely replicated to
the local machine. This machine is not working properly as a DC.
DC discovery test. . . . . . . . . : Failed
[FATAL] Cannot find DC in domain 'DWWINC'.
[ERROR_NO_SUCH_DOMAIN]
DC list test . . . . . . . . . . . : Failed
'DWWINC': Cannot find DC to get DC list from [test skipped].
LDAP test. . . . . . . . . . . . . : Failed
Cannot find DC to run LDAP tests on. The error occurred was: The
specified domain either does not exist or could not be contacted.
[WARNING] Cannot find DC in domain 'DWWINC'. [ERROR_NO_SUCH_DOMAIN]
And with DCDiag:
Starting test: frsevent
There are warning or error events within the last 24 hours after
the SYSVOL has been shared. Failing SYSVOLreplicationproblems may
cause Group Policy problems. DWWSERVER01 failed test frsevent
Starting test: FsmoCheck
Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error
1355
AGlobalCatalogServercould not be located - AllGC'sare
down.
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A TimeServercould not be located.
Theserverholding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed,
error 1355
A Good TimeServercould not be located.
Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... dwwinc.com failed test FsmoCheck
We're also getting all sorts of Userenv errors:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1006
Date: 3/28/2009
Time: 8:19:20 PM
User: NT AUTHORITY\SYSTEM
Computer: DWWSERVER01
Description:
Windows cannot bind to dwwinc.com domain. (Local Error). Group
Policy
processing aborted.
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 3/28/2009
Time: 8:19:20 PM
User: NT AUTHORITY\SYSTEM
Computer: DWWSERVER01
Description:
Windows cannot query for the list of Group Policy objects. Check the
event log for possible messages previously logged by the policy
engine
that describes the reason for this.
And MSExchangeAL Errors:
Event Type: Error
Event Source: MSExchangeAL
Event Category: Service Control
Event ID: 8231
Date: 3/28/2009
Time: 8:23:19 PM
User: N/A
Computer: DWWSERVER01
Description:
Permanent failure reported by policy group provider for 'CN=System
Policies,CN=DWWInc,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=dwwinc,DC=com':'MAD.EXE',
error=80040103. Taking provider offline.
Got to get this figured out by monday AM, so I need help BAD!
Thanks for any input.
Mick
them before the the old one went down. I also removed reference to the
old server in sites and servers as well as from the ntdsutil. The DNS
and DHCP servers are both on the new server and have been for the last
several months. I didn't have a reverse lookup zone as it's a 5 user
office, but did now just in case. Everything seems to resolve OK. I
ping the server from the client just fine, it resolves and pings, but
if I try to enter \\dwwserver\ in the my computer window, it takes a
while and then prompts me for ID and password. Once we put it in it
works and doesn't appear to prompt again.I also checked the two MS
articles and I had run through both procedures already, and I did
update the 'recipient update service' for the exchange settings.
I've run through this before with other clients when servers failed or
were retired (and I had missed oen step or another and had to do
manual cleanup), but this one is just being beligerent. No idea where
to go from here. Any other recommendations?? Thanks for your help.
Mick
.
- Follow-Ups:
- References:
- Prev by Date: Re: Global catalog server died before completing replication to new GC server
- Next by Date: Re: changing ip addres of my dc
- Previous by thread: Re: Global catalog server died before completing replication to new GC server
- Next by thread: Re: Global catalog server died before completing replication to new GC server
- Index(es):
Relevant Pages
|
