• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 347
  • Last Modified:

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).
0
Lisaa_G
Asked:
Lisaa_G
  • 8
  • 3
1 Solution
 
Santosh GuptaCommented:
Hi,

If SBS is not recoverable then

1. run the metadata cleanup (http://support.microsoft.com/kb/216498)
2. make sure that in DNS, ADUC and "Site & services" donot has SBS server records.
3.run DCDIAG /V and see the error.
0
 
Lisaa_GAuthor Commented:
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
0
 
SommerblinkCommented:
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.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Santosh GuptaCommented:
for metadata cleanup you donot need the ADUC. see the url  (http://support.microsoft.com/kb/216498) and follow it.
0
 
Lisaa_GAuthor Commented:
DCdiag output attached
DCdiag-log-March28.txt
0
 
Lisaa_GAuthor Commented:
My apologies.... does (http://support.microsoft.com/kb/216498) apply to Server 2008?
0
 
Lisaa_GAuthor Commented:
Netdom query FSMO  results in the specified domain either does not exist or could not be contacted.  The command failed to complete successfully
0
 
Santosh GuptaCommented:
yes,
0
 
Lisaa_GAuthor Commented:
OK - I will try the METADATA cleanup
0
 
Lisaa_GAuthor Commented:
METADATA Cleanup complete
proceeding on with the remainder of your instructions
0
 
Lisaa_GAuthor Commented:
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
0
 
Lisaa_GAuthor Commented:
This corrected some of my AD issues but did not ultimately leave the server in a functional state
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

  • 8
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now