Sunday
Feb082009
AD LDS Instance fails to start, throws 0x8007041d
Sunday, February 8, 2009 at 11:53AM Just throwing this out there so that it's more Google-able.
There was a Windows Update that fracks with the way ephemeral ports are handled on a DNS server, so if you're installing an LDS instance on a DC that's running DNS, and using the default ports of LDAP/50000 and LDAPS/50001, you can get unpredictable errors. Description of the issue here:
http://support.microsoft.com/kb/959215
Solution is to reghack the DC and reserve the high-level ports that you want, as listed here:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;812873
Reader Comments