- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Can't connect to ESXi5 server using vSphereClient ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2011 11:57 AM
09-12-2011 11:57 AM
When trying to connect with vSphere Client I get the following error message, see screenshot:
Connection Error:The client did not receive a complete response from the server '10.5.5.74'. (The underlying connection was closed: An unexpected error occurred on a receive.) Error Stack Call "ServiceInstance.RetrieveContent" for object "ServiceInstance" on Server "10.5.5.74" failed.
I get a different but related message when trying to connect via vCenterServer 5, see screenshot.
I'm installing my ESX5 server onto an HP Blade 460 G7 and I am using the HP ISO, a colleague has tried the standard VMWare one too, we both get the same error.
I tried this as an upgrade to an existing ESX4.1 host first, then after getting this error, I tired a clean install, same error.
Any one any ideas or basic troubleshooting steps I can carry out?
Attachments:
http://communities.vmware.com/message/1825706#1825706
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2011 06:42 AM
09-16-2011 06:42 AM
SolutionI logged a call with VMWare who confirm that this is an HP Driver issue.
I logged a call with HP who confirmt he issue and are planning a new release of ESX which will include a driver to fix it.:
ESXi 5.0 inbox be2net
4.0.88.0 driver due to a VLAN tagging issue
This version of the driver only affects Virtual Connect configurations. The async be2net 4.0.355
driver supporting ESXi 5.0 in a Virtual Connect environment is in the certification process currently.
This driver should be completed and posted to VMware's website for download in mid September
2011. This driver will also be included in HP ESXi 5.0 image releasing in mid September.