About Me

My photo
TsooRad is a blog for John Weber. John was a Skype for Business MVP (2015-2018) - before that, a Lync Server MVP (2010-2014). My day job is titled "Technical Lead, MS UC" - I work with an awesome group of people at CDW, LLC. I focus on collaboration and infrastructure. This means Exchange of all flavors, Skype, LCS/OCS/Lync, Windows, business process, and learning new stuff. I have a variety of interests - some of which may rear their ugly head in this forum. I have a variety of certifications dating back to Novell CNE and working up through the Microsoft MCP stack to MCITP multiple times. FWIW, I am on my third career - ex-USMC, retired US Army. I have a fancy MBA. One of these days, I intend to start teaching. The opinions expressed on this blog are mine and mine alone.


Oh my aching brain cell, or, dcpromo u gotta be kidding me!


Stupidly, I attempted to join a new 2008 R2 DC to our domain the other day.  I was doing it from a different site, but heck, should be no sweat, right?


DNS was good, name resolution worked, and the machine could join the domain, but why the dcpromo errors?

“failed to examine the active directory forest.  the error was: the operation cannot conitnue because the ldap connect/bind operation failed: error: 58” 


“the operation cannot continue because ldap connect/bind operation failed: error: 1326”

I tried various fixes and whatnots…and then stumbled across a little tidbit here that implied that the computer administrator (pre-domain) password might need to match the forest root domain administrator password. 

Having exhausted all my other possibilities, I tried this - and did not expect any success.

But, WTFO!  It worked.  So now the question is, why?


Wildblue said...

Thanks for the tip. I accomplished the same thing by just disabling the local admin account. Weird... shouldn't have worked, but that's what seemed to fix it.

Victor Amram said...

I was getting the same error 58 while running DCPROMO on a W2012R2 server on an IPV4-only network. Looking at the logs, I found errors in the system log that IPV6 adapters were failing to register. I resolved this by disabling the IPV6 transitional adapters:

netsh interface 6to4 set state disabled
netsh interface teredo set state disabled
netsh interface isatap set state disabled

That done, DCPROMO ran w/out any errors.

StiX said...

The tip from victor was the good one for me.
Thanks for sharing your experience. :)

Landis Contact Center

Now, this is significant.  MVP Matt Landis and his merry band of mavens is getting their contact center out to the world. This is a happy ev...