Hi All -
Have any of you seen this error. I can log into VC fine and my licenses are there but when I try to open a console connection to a VM from VC I get this error.
"Error connecting: Cannot connect to host myhost.domain.com: No connection could be made because the target machine actively refused it."
I have even gone so far as uninstalling VMware and reinstalling the VC server.... Still no luck
Yes I've seen it before. have you checked firewalls between you and the VC server? That includes software firewalls on the OS as well. Is the Virtual Center Service running?
That is what I was thinking but I have checked and I have an 100% open connection between VC and my ESX server. They are both on the same VLAN.
Table 2-1 in the Quickstart Documentation has the ports you need to open if that is the cause (http://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_quickstart.pdf). Page 31 I believe.
Please award points if my answer was helpful or correct.
cpq, can he still log into Virtual Center if the service wasnt running?
I see what you mean now! I should have read the entire post. ![]()
Message was edited by: cpqarray
I have seen a similar error that was caused by name resolution problems, have you added DNS entries or host entires on the VC server for each of your ESX hosts?
So what controls the access to the VC, he was able to log in fine but when he tried to use the console he got the error? Is it the web part that is installed with the VC? Sorry to ask a question within this question.
The service is running and I have verified name resolution between VC and ESX.
If I point my VC client directly to my ESX server I can open the console. Not through VC though... Even though I can configure my ESX host via VC...
Could it possibly be permissioning? Have you checked your roles and permissions?
I have checked permissions and even granted them again at the data center level for Domain Admins administrator role. It is propagated down throughout... Still no luck though...
UPDATE - I tested opening a console from the VI client on VC server itself and that does work. It gives that error when I try to open console from any other VI client on another machine though.. That same machine can open console if I connect directly to the ESX server but not from VC. Running Vista if that makes a difference...
Which version of Vista? I believe the only supported environments for Vista are Business and Enterprise -- for the machine where you install the Virtual Infrastructure Client that is.
I have the exact same problem, though my setup is slightly different. In my case, the vc is not accessible from the outside, so I used ssh tunneling (port 443). All is well, except for vm console access. I believe it has something to do with port 901 and 902, and I could not figure out way to pass these ports at the same time as I am using 443.
Since from VC itself I can access the vm consoles fine, I wonder if it is just a matter of proxying or tunneling though the vc server in order to make the vm console accessible to vi client in this case. Any advice as how to do this would be greatly appreciated. I thought vmware could just allow everything flow thru port 443, but somehow vm console does not.
Thanks for any ideas,
--John
