Lets dive straight into this error message which happens to be affecting two of my VMs:
As you can see I’m unable to get the console window working! Exact message displayed across the top sheds some light into why this is happening – “Unable to connect to the MKS: Console access to the virtual machine cannot be granted since the connection limit of 0 has been reached.”
I know of at least three different ways to make this error message go away and get to the console window again.
Edit the *.vmx file and change/add RemoteDisplay.maxConnections value and set it to 10. Example:
Make sure the affected VM is powered off. From vSphere client right click on the desired VM, Edit Settings, Options tab, under Advanced click on General and then on Configuration Parameters. Add Row is what we want to be doing. RemoteDisplay.maxConnections goes under Name and Value is 10.
Use vSphere web client. Open Internet Exporer, navigate to:
https://your_vcenter_ip_address:9443/vsphere-client and login as per normal.
Find your problematic VM, right click, Configuration and then Edit Settings.
Second tab called VM Options is where we should be clicking, expanding “VMware Remote Console Options” is what we want to do. As you can see “Limit the number of simultaneous connections to this virtual machine” is set to 0 meaning no one can connect. 10 is the value we want to set as that’s the default setting.
Either one of the three methods above will do to regain console access.
If you guys have any comments please leave them down below!
Dude I am reading all posts.
Superb Stuff..
Thank you
Good, glad you’re finding my posts useful!
Thanks, that Helps me.
RemoteDisplay.maxConnections was set to 0
Awesome! 🙂
Adrian, Thank you for your post. It was very helpful in resolving the issue at my work. Worked perfectly!
in my case was my firewall [solved]
Yep, firewall can cause this issue if you have one between PC running vSphere client and the ESXi server.
Graphic representation:
@Adrian Kielbowicz thanks for mentioning the firewall. I’ve been banging my head against the wall on this problem for a while and all posts just called it a DNS issue. In my case it was definitely the vSphere client machine not being able to talk to the ESXi host on port 902 which seems to be required for authenticating console connections.
Pingback: Virtual Machine Vm |
For me DNS problem. In hosts file insert the node and vcenter ip. I’ve solved
Any thoughts on this?
“Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period.
https://communities.vmware.com/message/2676815#2676815
It worked for me ! thanks , did it from the webclient while the machine was running, no power off