You may see following problem if you login vCenter Server 6.0 by vSphere Client:
Login to the query service failed.
The server could not interpret the communication from the client. (The remote server returned an error: (500) Internal Server Error.)
That’s because “Use Windows session credentials” checkbox is selected. Deselect it and give it a try.
Refer KB Searching the Inventory with the vSphere Client fails (2143566)
Just a quick post. When virtual machine cannot get DHCP IP address the first thing you want to check is firewall. Whatever Windows firewall or physical firewall. You should make sure UDP port 67 and 68 are not blocked. Otherwise you will see the virtual machine gets 169.x.x.x IP address only.
The two ports is required for DHCP client to query IP addresses. The methodology is introduced in RFC document.
DHCP uses UDP as its transport protocol. DHCP messages from a client
to a server are sent to the ‘DHCP server’ port (67), and DHCP
messages from a server to a client are sent to the ‘DHCP client’ port
(68). A server with multiple network address (e.g., a multi-homed
host) MAY use any of its network addresses in outgoing DHCP messages.
I also got some ideas in this post.
If you have VMware Workstation and VMware Remote Console both installed on Windows 10 you may see vCenter virtual machine console in vSphere Web Client is opened by VMware Workstation instead of VMware Remote Console. If you see same case your VMware Remote Console may be hijacked. I call it “hijack” since there is no easy way to revert it back.
如果你的Windows 10电脑上装了VMware Workstation和VMware Remote Console，当你在vSphere Web Client里打开运行在vCenter上的虚拟机控制台时，VMware Workstation可能会代替VMware Remote Console自动连接到控制台。恭喜！你的VMware Remote Console被劫持了。这个问题解决起来比较复杂所以我叫它“劫持”。
It’s easy to find a solution for this particular problem. VMware has a KB for this error. Somehow it’s not my case. I don’t know what’s the exactly root cause but you can try vMotion the virtual machine to other host and give a try.