Kerberos error from a non-DC machine
One of my desktops (Desktop A) is showing the following error:
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server (Desktop B)$. The target name used was cifs/(Desktop C). This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (DOMAIN.COM) is different from the client domain (DOMAIN.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
None of the involved machine names are AD servers, they're all workstations running wither Windows 7 or Windows 10.
The Kerberos client received a KRB_AP_ERR_MODIFIED error from the server (Desktop B)$. The target name used was cifs/(Desktop C). This indicates that the target server failed to decrypt the ticket provided by the client. This can occur when the target server principal name (SPN) is registered on an account other than the account the target service is using. Ensure that the target SPN is only registered on the account used by the server. This error can also happen if the target service account password is different than what is configured on the Kerberos Key Distribution Center for that target service. Ensure that the service on the server and the KDC are both configured to use the same password. If the server name is not fully qualified, and the target domain (DOMAIN.COM) is different from the client domain (DOMAIN.COM), check if there are identically named server accounts in these two domains, or use the fully-qualified name to identify the server.
None of the involved machine names are AD servers, they're all workstations running wither Windows 7 or Windows 10.
Sarang Tinguria
If these machines are domain member client machines then this event makes sense
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.