_kerberos._tcp.Default-First-Site-Name._. When I look at the DNS zone for my Windows domain controller, I see the A record and then all of these SRV records: You are a saint.I've been searching for a resolution to this issue for some time! Hopefully this post will stop others from going through my pain! A very simple fix for such a painful problem. Removed these entries and the problem was resolved. I decided to revisit my name resolution even though DNS was working correctly. There were so many forum posts on the Internet leading to DNS as being the cause for this error. I was confident it was nothing to do with authentication! SC_QUERY: - Query secure channel for Domain on ServerName This error code description from Microsoft completely threw me off track diagnosing the computer account passwords, rejoining PC's to the domain and diagnosing the Kerberos Key Distribution Center (KDC) service.Īll tests against the domain using nltest for the computer account were passing successfully! Verify the password in service configuration is correct for the user account. Check if there are any system services running as the user account.Ĥ. This error code might indicate that the user's password expired while the user is still logged on the computer.ģ. The following TechNet article from Microsoft says Error Code 49 is the following: On the details tab I was getting ErrorCode 49. Look in the details tab for error code and description. Windows could not authenticate to the Active Directory service on a domain controller. I had a very frustrating issue today with group policy at a client on a few member servers running Windows Server 2008 R2.Ī quick google showed DNS as a cause - I checked my DNS configuration and it was correct so I discarded this as the reason.Ī few member servers were receiving the following error:
0 kommentar(er)
