Difference between revisions of "Troubleshooting (Virtual Machine)"

Jump to navigation Jump to search
m
→‎Can't Connect to VM Console: Fixed restart the management services link
m (moved Virtual Machine Trubleshooting to Troubleshooting (Virtual Machine ): Name doesn't work well on Virtual Machine category page)
m (→‎Can't Connect to VM Console: Fixed restart the management services link)
Line 6: Line 6:
'''Error connecting: Cannot connect to host...''' or '''Can't connect to MKS...'''
'''Error connecting: Cannot connect to host...''' or '''Can't connect to MKS...'''
* This is caused by a TCP connection failure to the ESX server the VM is hosted on. Using telnet or a port test utility, confirm you can connect on both TCP 902 and 443 from your machine to the ESX server.
* This is caused by a TCP connection failure to the ESX server the VM is hosted on. Using telnet or a port test utility, confirm you can connect on both TCP 902 and 443 from your machine to the ESX server.
* If the problem is affecting a single ESX that previously worked, [[ESX#VMware_Management_Agent_Restart|restart the management services]] on that ESX
* If the problem is affecting a single ESX that previously worked, [[Procedures_(ESX)#VMware_Management_Agent_Restart|restart the management services]] on that ESX


== Can't Deploy VM ==
== Can't Deploy VM ==

Navigation menu