Question Locked

Users can no longer login after AD GC failure

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I can "see" the users in AD, but none can log in except the domain admin. The GC was running on a DC in a bladecenter which failed. It's back up, but will not replicate. Seizing FSMOs has made no difference.

dcdiag reports no GCs are up, no matter how many other DCs I assign to the role

DNS names of hardware seem to be functioning (i.e. I can 'ping by name' etc). All machines I try to log in with seem to have accounts in the domain as well, but report bad username/password, even when I use AD to reset the password. I don't want to recreate all of these accounts, if possible.

Any suggestions?

Matt Sullivan
Maine

15 replies

by p.j.hutchison

Open Sites and Services console, expand it until you get the NTDS Settings and open Properties, then tick the box to make it a Global Catalog server!

by mtsx1us

Did that. No matter how many DCs I bring up, and no matter how many (or how few) GCs I select, dcdiag still reports all GCs are down and users still cannot log in, except the domain admin account

by dumphrey

or over several? I AD Sites and Services, expand your new server, and check that there is an NTDS connection present, and that the properties on that ntds connection mark it as a GC.

by mtsx1us

No help with any of those. Single site/domain, each DC sees the others and thinks it can replicate, but still no logins, and no GC in dcdiag

by dumphrey

have you rebooted servers since adding the GC role?

by dumphrey

would be to remove the GC role from all servers, demote on DC, then re dcpromo it back to a DC. This might force a GC and working GC at that... dunno really. And a vaguely drastic step, but may be less work then rebuilding entire AD from scratch, or even the accounts...

by mtsx1us

I did try that once, though not dcpromo'ing out one DC afterwards, but I have a feeling I'll have to dcpromo them all, right? It seems drastic to me too, but then my options are pretty limited at this point.

Also thought about rendom to a new domain, to see if that would also create a new (hopefully working) GC. Any thoughts on that?

by cg it

if your global catalog server went down, do you have a relatively recent backup of the system state of that server?

if so, then do a restore from the backup.

I don't think you can create a new Global Catalog server on an existing network. What the global catalog role is, is a copy of all objects in an AD domain so if you lose it, don't think AD will just automatically create it again.

Are you sure you only lost the Global catalog role? what about operations master and also the sysvol and netlogon shares? were they on that server as well.

by mtsx1us

When it came back up later, it would not replicate to the rest of the DCs, and no more logins allowed but admin. I don't have a good backup that I trust to restore either. Hence the need to recreate or rename the domain to create a new one. Don't know if that will help though?

I would prefer to figure out why the GC won't respond in the first place to dcdiag, but failing that I need to move the user accounts somehow so they're accessible again.

by cg it

to be accessible to the users.

Even if your backup might be unreliable, it's probably the best way. restore to some hardware, put online, let replication take place, then make another on another server.

once again, you need the sysvol and netlogon shares to be accessable to users for them to logon. Even if you have a global catalog server on the network, without those shares, users won't be able to logon.

by mtsx1us

Since my backup (Symanetec) used old sys credentials, not sure I can even get it to restore. I did try copying the sysvol and netlogon shares from another DC that had seemed to survive the initial "hit", but that didn't seem to make any difference.

I find it odd that I can "see" the old accounts, too. I will probably try restoring various versions of sysvol and netlogon if I can get back into a backup to do so, but I don't hold much hope out for that, given the credential issue. Might be able to get the service to restart in Symantec for that, but it doesn't seem to even recognize the Domain Admin login when trying to access job lists/media??

by cg it

but can't live without good backups, ones you successfully restored as a test..

by mtsx1us

So now I'll have to try ot resotre without domain credentials I guess, and hope for the best

This discussion is closed to new replies.