krabores target resolution error

karbores target resolution error
ganesh puriAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Shaun VermaakTechnical Specialist/DeveloperCommented:
Does the name translate via DNS?
0
David Johnson, CD, MVPOwnerCommented:
Do you mean Kerberos? is your dns up to date? For windows try an ipconfig /flushdns and retry the failing operation.
0
Blue Street TechLast KnightCommented:
Hi ganesh,

There are a few possibilities for this error. Lookup your specific error & match accordingly:

Issue Category: Client-side authentication error: KerbResolutionError
Underlying Source Message from WinRM or Providers (shown in Task Details pane):
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer <computer name>. Verify that the computer exists on the network and that the name provided is spelled correctly.

Error <computer name>: Refresh failed with the following error: Call was canceled by the message filter.
Possible Causes and Suggested Resolutions:
Client is in Domain1 and the target server is in an untrusted Domain2. A Kerberos error occurs because the Kerberos TGS cannot find the target server. Explicit credentials must be used to manage the target server. Right-click the target server in the Servers tile of the All Servers page, and then click Manage As to provide explicit credentials.


Underlying Source Message from WinRM or Providers (shown in Task Details pane):
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot find the computer <computer name>. Verify that the computer exists on the network and that the name provided is spelled correctly.

Error <computer name>: Refresh failed with the following error: Call was canceled by the message filter.
Possible Causes and Suggested Resolutions:
Client is in a domain and the target server is in the same domain, but the domain name provided for the target server is incorrect or misspelled.


Underlying Source Message from WinRM or Providers (shown in Task Details pane):
Error <computer name>: Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config.
Possible Causes and Suggested Resolutions:
Client is in a domain, but the domain controller for the client computer is not accessible. Try adding the target server to the client computer’s trusted host list. For information about how to add a managed server to the trusted host list, see Add Servers to Server Manager.


Issue Category: Client-side authentication error: Kerb0x80090311Error
Underlying Source Message from WinRM or Providers (shown in Task Details pane):
Configuration refresh failed with the following error: The metadata failed to be retrieved from the server, due to the following error: WinRM cannot process the request. The following error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains.After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config.
Possible Causes and Suggested Resolutions:
Client is in a domain, and the target server is in the same domain (using the NetBIOS name or FQDN, and explicit but local-only administrator credentials for the target, or other non-domain credentials): A Kerberos error occurs because the credentials are unknown on the domain. The user must add the target server to the trusted host list on the client computer to allow the Default authentication mechanism to use Negotiate authentication instead of Kerberos. For information about how to add a managed server to the trusted host list, see Add Servers to Server Manager.

Let me know if you have any other questions!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.