An Unknown Connection Error Occurred
Contents |
VMware 396221 Followers Follow Join the Community! Creating your account only takes a few minutes. Join Now vSphere Client could not connect to (IP/Server) An unknown connection error occurred. (The request failed because of the connection failure. an unknown connection error occurred vsphere client (Unable to connect to the remote server)) Reply Subscribe RELATED TOPICS: vSphere Client vsphere an unknown connection error occurred vcenter client manager Unable to login to vSphere Client   1 2 Next ► 33 Replies Thai Pepper OP Andrew an unknown connection error occurred vsphere Samuel Dec 30, 2013 at 12:15 UTC Can you ping the remote server? Are you trying to connect to the host name or to the IP address of the server? If you're using the host name, vsphere client could not connect to vcenter an unknown connection error occurred try the IP address. (it may be a DNS issue). Can you connect directly to the VM hosts? 0 Mace OP George1421 Dec 30, 2013 at 12:51 UTC There is not a lot of info here, but there are a few things to check. I assume your vCenter/ESXi server is version 5.5 and your client may be something older like 4.x or 5.0. There was a big change in
Vsphere Client Could Not Connect To An Unknown Connection Error Occurred 404
the environment between 4.x and 5.5. I've also seen this error when you connect to a vCenter server and the vCenter server service is not running. Things to check 1) Make sure you are running the latest vSphere client 2) If you are using a vCenter server make sure all of the required services are running. 3) Also make sure your firewall is not blocking ports 443 and 902 0 Poblano OP f0st3r Dec 30, 2013 at 4:31 UTC Yea need a little more info.. Are you connecting to vcenter? Host directly? I had some weird issues connecting hosts in vcenter once and it was because the vcenter server did not hold a default gateway, once I got the default gateway in everything worked. Might check that. 0 Tabasco OP TAHIN Dec 30, 2013 at 8:35 UTC We see that error whenever the vpx/management agents are having issues. It will prevent your client from connecting to the hosts directly. Do you have a vcenter server? Did this particular host in a 'disconnected' state from vcenter? First I'd try to ping as Andrew said. If you can ping the host successfully, it's either the management network or the the agents being locked up. Try to iLO into the host. From the menu
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vSphere™ > VMware ESXi 5 > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 10 Replies Latest reply: Jul 16, 2014 7:57 AM by
Vsphere Client Could Not Connect To A Communication Error Occurred
FelipeSE Can't connect to new ESXi 5.5 hosts with vSphere Client MarkBowker the request failed because the server closed the connection esxi Sep 29, 2013 11:26 AM Completed fresh install of ESXi 5.5 on two new Dell PowerEdge servers last night.Trying unable to connect to vsphere client to connect to them through the vSphere client fails.I can ping both servers with no problems from the server where the vSphere client is installed (it is not a DC https://community.spiceworks.com/topic/425982-unable-to-connect-hosts-through-vsphere-client but a Windows 2003 server - it does have .Net 3.5 SP1 installed).If I try to open the IP of the hosts in a web browser, http://xxx.xxx.xxx.xxx times out however if I try http://xxx.xxx.xxx.xxx:902 It connects to the server, but rather than getting the web page I'm used to expecting with 5.1 I get this message:"220 VMware Authentication Daemon Version 1.10: https://communities.vmware.com/thread/458401?start=0&tstart=0 SSL Required, ServerDaemonProtocol:SOAP, MKSDisplayProtocol:VNC, VMXARGS supported, NFCSSL supported. I get this exact same message if I telnet in on port 902. So I know I can talk to the host, but have no clue why I can't log in to it or have it display the tools in a web browser."Trying to use the same IP with port 902 in the vSphere client to login I get this error:vSphere Client could not connect to "xxx.xxx.xxx.xxx"An unknown connection error occurred. (The client received an invalid response from the server. (The server committed a protocol violation. Section=ResponseStatusLine))I did notice there was a 2 hour and 4 minute time difference between the host server and the client server. I reset time to match in BIOS of the host server. Testing afterwards yielded the same results.Probably unrelated, but throwing it out there in case it points to an answer, when running the "Test Management Network", ping passes for the default gateway and the secondary DNS server (which is google 8.8.8.8) but fails for the Primary DNS server (local IP) and fails resolving host name.Any thoughts, h
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring http://serverfault.com/questions/342863/vmware-vsphere-client-cannot-connect developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ http://www.emware.nl/articles/vcenter-server-appliance-could-not-connect-an-u.html Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top VMware vSphere Client Cannot Connect up vote 3 down vote favorite 1 When I try to connect to a error occurred couple of our ESXi servers with my vSphere client I get the following error message: "vSphere Client could not connect to "IP Address". An unknown connection error occurred. (The client could not send a complete request to the server. (The underlying connection was closed: An unexpected error occurred on a send.)) I'm thinking this may have something to do with a version incompatibility but I'm not sure. Can somebody shed some light? vmware-esxi share|improve this question edited Dec 20 '11 at an unknown connection 19:13 Shane Madden♦ 91.1k6107181 asked Dec 20 '11 at 18:55 Windows Ninja 1,23193551 Well are you using a VSClient that's up to the same level as the host you're trying to work on and if the host is lower than the client version have you installed that version too? –Chopper3 Dec 20 '11 at 19:19 add a comment| 5 Answers 5 active oldest votes up vote 4 down vote This error troubled me for quite a while, and since this thread is still the first google result, here is my solution. It is quite simple actually, just "Restart the Management agents". As mentioned by VMWare knowledge base all you have to do is run: /etc/init.d/hostd restart /etc/init.d/vpxa restart from shell. share|improve this answer answered Mar 21 '15 at 12:28 diehard 411 Worked perfectly! –Saif Jul 2 '15 at 8:00 For me only /etc/init.d/hostd restart solved the issue –Lisandro Dec 9 '15 at 18:37 add a comment| up vote 2 down vote Test the network by pointing your web browser at the address of the server. It should give you a web page and a link to download the client and a link to login to the Web UI. If the page displays correctly then login to the web ui to test your logon/pw share|improve this answer answered Dec 20 '11 at 19:21 james 40127 Looks like there is a bigger problem
Server Appliance - Could not connect: An unknown connection error occurred 9,039 Views Just now and then i ran into a strange problem: my vCenter wasn't reachable anymore. A simple reboot works, but is no solution! When you connect with the vSphere client you recieve the following error message: vSphere Client could not connect to "