Solved

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

Posted on 2012-03-13
2
8,954 Views
Last Modified: 2012-06-27
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
Comment
Question by:d_melnyk
2 Comments
 
LVL 118

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE) earned 500 total points
ID: 37717496
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
 

Author Closing Comment

by:d_melnyk
ID: 37763722
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

Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

Join & Write a Comment

Suggested Solutions

Last article we focus in how to VMware: How to create and use VMs TAGs – Part 1 so before follow this article and perform the next tasks, you should read the first article how to create the TAG before using them in Veeam Backup Jobs.
HOW TO: Upload an ISO image to a VMware datastore for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere Host Client, and checking its MD5 checksum signature is correct.  It's a good idea to compare checksums, because many installat…
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

760 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now