deeburp
asked on
Duplicate names in AD causing kerberos errors
I get this error twice every hour or so on all my dcs.
The KDC encountered duplicate names while processing a Kerberos authentication request. The duplicate name is MSSQLSvc/servername.domain .com:1433 (of type DS_SERVICE_PRINCIPAL_NAME) . This may result in authentication failures or downgrades to NTLM. In order to prevent this from occuring remove the duplicate entries for MSSQLSvc/servername.domain .com:1433 in Active Directory.
when i ran a listing of all SPN entries. I see the server itself has the principal name listed as well as the sql administrator account.
all other talk of this error suggests removing the bad server SPN but not sure which isn't supposed to have the entry. Server or AdminAccount?
i tried rebinding to AD but that didn't resolve the errors.
any help would be great.
The KDC encountered duplicate names while processing a Kerberos authentication request. The duplicate name is MSSQLSvc/servername.domain
when i ran a listing of all SPN entries. I see the server itself has the principal name listed as well as the sql administrator account.
all other talk of this error suggests removing the bad server SPN but not sure which isn't supposed to have the entry. Server or AdminAccount?
i tried rebinding to AD but that didn't resolve the errors.
any help would be great.
Try deleting the AdminAccount
ASKER
delete the admin account itself or just the SPN information about the server service that is on the account?
ie this below:
dn: CN=adminaccountsql,OU=Admi nistrators ,DC=domain ,DC=com
changetype: add
servicePrincipalName: MSSQLSvc/devserver.domain. com:1433
servicePrincipalName: MSSQLSvc/servername.domain .com:1433
ie this below:
dn: CN=adminaccountsql,OU=Admi
changetype: add
servicePrincipalName: MSSQLSvc/devserver.domain.
servicePrincipalName: MSSQLSvc/servername.domain
So, you are using Admin account multiple SQL servers?
ASKER
correct we have one used on both our production and dev servers
Alright try using a different account for the other SQL service that might clear the dup up
ASKER
well we actually don't have the dev server anymore.. so perhaps i can just delete that entry from the admin account?
Yeah give that a shot
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
looks like this worked.. i have just the adminaccount running as the service so i've removed the spn for the server itself. so far no errors in the dc logs