5.5.2

Troubleshooting
If you encounter problems when running or using PowerShell plug-in, you can use a troubleshooting topic
to understand and solve the problem, if there is a workaround.
Servers Not Found in Kerberos Database
After you add servers with Kerberos authentication, the servers might not be found because they are not
added correctly.
Problem
When you try to connect to a server, the server is not found in Kerberos database.
No valid credentials provided (Mechanism level: No valid
credentials provided (Mechanism level: Server not found in Kerberos
database (7)))
Cause
This error might be caused by domain or mapping problems, or because of a DNS problem where the
service principal name is not built correctly. Kerberos authentication does not workwhen the destination is
an IP address.
Solution
When you add a PowerShell host using the Kerberos authentication type a DNS or NetBIOS destination.
Unable to Obtain a Kerberos Ticket
When you provide wrong credentials, the plug-in fails to obtain a Kerberos ticket.
Problem
You are unable to add a host to the plug-in's inventory and the result is the following error message.
Pre-authentication information was invalid (24)
Cause
You have provided wrong credentials.
Solution
Provide the correct credentials.
Kerberos Authentication Fails Due to Time Differences
System time differences in the environment that uses Kerberos configuration might lead to authentication
failure.
Problem
Attempts to use Kerberos for initial authentication of a host or for resource access fail and the following
error message appears.
Clock Skew
Cause
If the system time on the computers in the environment deffers with more than 5 minutes from the client
computer or from one another, the Kerberos authentication fails.
Chapter 20 Using the PowerShell Plug-In
VMware, Inc. 127