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

re- connect server/active directory

Cannot get Active Directory back online.  Does not "bind" with LDAP using SPN when running dcdiag tests.  on netdiag test it can't find the server, but does register the DNS & Gateway properly.
I  founf something from MS 329887 about 'cannot interact with active direcotry mmc snap-ins and tried to do those commands
Secedit /configure /cfg c:\winnt\repair\secsetup.inf /db secsetup.sdb
Secedit /configure /cfg c:\winnt\repair\secdc.inf /db secdc.sdb

but they did not complete successfully, but I have attached the Scesrv.log for help.
Which looks like I need to go into registry and change settings?
0
ARservice
Asked:
ARservice
  • 9
  • 8
  • 2
1 Solution
 
ARserviceAuthor Commented:
Do I need to use the 'seize' command for FSMO to get AD working again?
I could sure use some help on this pesky issue.
Thank-you
0
 
pwindellCommented:
Did you make sure that the clocks are all the same on all the machine,...including Time Zones being correct and DST being considered?
0
 
ARserviceAuthor Commented:
Yes, also verified with "netdom time workstations" then "netdom time server" then"netdom time with name of server.
I am thinking I just need to delete active directory and reinstall as I am getting no where with any fix and keep getting the same error message.  It is very very frustrating as I am sure it is probably a simple few keystrokes somewhere but don't know where.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
pwindellCommented:
Nothing is ever "just a few keystrokes" with AD problems.
0
 
compdigit44Commented:
Has anything change in your enviroment recently?
0
 
compdigit44Commented:
Have you checked to make sure all of the required DNS A.D records in present? If they are missing you can run the following command from the Windows 2000 Resource Kit to rebuild the DNS SRV records...

nltest /dsregdns
0
 
ARserviceAuthor Commented:
the dsregdns command is not a valid command for server 2000, works on 2003 server.

I did run  most of the other commands available with success

In running netdiag.exe - failure to bind LDAP

Same binding failure (passwrod etc) when running dcdiag.exe.

Tried to seize roles using ntdsutil.tool. but could not get past trying to get the 'connect to server" as it would keep back invalid credentials/password.

I just need to figure out how to change the password for ldap to bind

If there is not a way to change this password (in registry?) or an .ini file? then do I just delte AD using dcpromo and reinstall?
0
 
compdigit44Commented:
in order to run nltest on WIndows 2000 you need to download the resource tool kit
0
 
ARserviceAuthor Commented:
I HAVE HAD IT DOWNLOADED for over a couple years now and that command is not listed on the listing when you type
nltest /?

I will go online and Redownload it and see if the command options change to include the
 nltest /dsregdns
thanks
0
 
compdigit44Commented:
0
 
ARserviceAuthor Commented:
No that command is not there, but I can dsderegdns the dns - Isn't that wierd; can not register it but can deregister it!  Go figure.
0
 
ARserviceAuthor Commented:
The link is for Widnows 2003 Server, I am running Windows 2000.  I can try and see if they will work for this system.
0
 
compdigit44Commented:
I know the link was for 2003 but some tools and work on 2000.. some not all..

Can you send a snap shot of some of core DNS AD records so we can if if they look correct
0
 
compdigit44Commented:
also try to the dcdiag with the follow switches and paste your results... dcdiag /e /v
0
 
ARserviceAuthor Commented:
I downloaded the 2003 and it would not install said it needed Windows XP or newer to run.

But I have attached more than I think you wanted on DNS screenshots and dcdiag /e /v along with a netdiag.log.

The whole issue is that AD is not being allowed back to the DNS via LDAP bind error.
Should I just call it a a day and reinstall AD via DCpromo?

I really do appreciate the help, I'm just frustrated that I can not get this corrected - how DNS magically disappeared from the server 3 weeks ago is still a mystery and no one is talkin'!  But this whole thing is a result of having to reinstall DNS then, then I ended up with 2 TCP/IP addresses for it which was fouling it up, so I had to delete that and reinstall a 2nd time, at that point AD would not connect to DNS and this is where I'm at today.
dnstabs.pdf
forwardzoneproperties-ns1.pdf
fileinfpbytabs.pdf
dcdiag-run-twice.pdf
NetDiag.log
0
 
compdigit44Commented:
Have you tried the fix in this KB article: http://support.microsoft.com/kb/826902
0
 
ARserviceAuthor Commented:
well that was exciting just in the anticipation that it would work, but still cannot open AD, same error message of logon failure
Ran dcdiag with same error code 31 via LDPD bind error.
0
 
compdigit44Commented:
Have you read this KB article yet: http://support.microsoft.com/kb/837513
0
 
ARserviceAuthor Commented:
AT LAST!  I had read and been referred to similar articles, but no other articles had the Method #5 Fix the Derberos realm which took all of 2 minutes, rebooted and voila'..  4 weeks of agony, dispair and half -baked system running on bandaid fixes.  THANK-YOU!
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

Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

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