• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 11163
  • Last Modified:

SSL verification failure due to a host "host name" thumbprint mismatch

Hi folks,

     I am new to using ESXi and VSphere. I have setup my ESXi server everything seems to be working fine. I installed VSphere on an XP system and it properly connects and everything works fine.

    I allocated resource pools and set up a user to access only one VM. This seems to work fine from the XP machine with VSPhere.

    I then Installed VSphere on another system (Windows 7, 32bit) and Went through the same process as the other XP system when certificate info poped up i.e. check marked install the certificate and clicked ignore, as per instructions from youTube tutorial.

    The user can login to Vsphere properly and it shows the vm they are allowed to use, and they can power it up, except on this machine when they try and open the concole I get the error "SSLverification failure due to a host "[host name]" thumbprint mistmatch.

Any info on how to deal with this would be greatly appreciated. I have tried uninstalling CSphere and reinstalling it on the system to no avail. Same problem exists if I login as "root" to the ESXi server.

VSPhere version is 5.0.0 - 455964
ESXi 5.0 version - build 469512

The VM trying to be accessed is Windows 7 (64bit)

Best regards, Dave Melnyk

P.S. As I am new to dealing with ESXi I am afraid I will need the "ESXi for Dummies" type of instructions to implement any fix. Thanks again!
0
d_melnyk
Asked:
d_melnyk
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
try creating a hosts file on the Windows 7 workstation

with server hostname and IP address

e.g.

servername.company.com 192.168.1.1

turn off Windows 7 firewall

run the Client as Administrator

also check this forum link

http://communities.vmware.com/thread/334675
0
 
d_melnykAuthor Commented:
Thanks for the reply. This issue became moot as accessing the VM this way removed some features required for a virtual desktop - i.e. sound. I think the issue is realted to the low level hardware of the workstation - early pentium. Now using RDP to access the VM on a system sharing the VM under workstation 8. Provides the functionality required for the user.

haven't been able to reslove the issue, but want to award the points as I always appreciate a fast response from someone to a question so that there is at least something I can try to attempt to solve the problem.
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Tackle projects and never again get stuck behind a technical roadblock.
Join Now