asked on

Server 2008 Active Directory Issues

Had two servers running one SBS 2003 one Server 2008.

SBS 2003 crashed and is beyond recovery - users started reporting problems logging into domain.

Attempted to seize all FSMO roles on Server 2008 (not sure if it worked) but still seeing significant AD issues.

When attempting to open AD Users and Computers from Admin Tools - receive the following error...

Naming information cannot be located because:-
The specified domain either does not exist or could not be contacted.

Contact your system administrator to to verify that your domain is properly configured and is currently online.

Is there any way I can (a) diagnose just what is wrong with AD and (b) fix it without wiping out the server (we are also running Exchange on this server).

ASKER CERTIFIED SOLUTION

Santosh Gupta

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Lisaa_G

ASKER

How do I run metadata cleanup?

Cannot access ADUC and Sites and Services (see error in post)

Trying to capture full DCdiag output for you

Sommerblink

Attempted to seize all FSMO roles on Server 2008 (not sure if it worked) but still seeing significant AD issues.

From the 2008 machine you can see who the FSMO owner(s) are by executing the following command "netdom query fsmo"

In addition to the advice above, also make sure that you've updated the DNS records for all the computers that are members of the domain, removing the failed SBS IP address.

Santosh Gupta

for metadata cleanup you donot need the ADUC. see the url (http://support.microsoft.com/kb/216498) and follow it.

Lisaa_G

ASKER

DCdiag output attached
DCdiag-log-March28.txt

Lisaa_G

ASKER

My apologies.... does (http://support.microsoft.com/kb/216498) apply to Server 2008?

Lisaa_G

ASKER

Netdom query FSMO results in the specified domain either does not exist or could not be contacted. The command failed to complete successfully

Santosh Gupta

yes,

Lisaa_G

ASKER

OK - I will try the METADATA cleanup

Lisaa_G

ASKER

METADATA Cleanup complete
proceeding on with the remainder of your instructions

Lisaa_G

ASKER

Ok - I seem to have restored at least some of the AD

I have Exchange errors and Group Policy errors that are AD related but I will open a separate question for those

Lisaa_G

ASKER

This corrected some of my AD issues but did not ultimately leave the server in a functional state