There is "trivial" logging but I don't think it will help in this case. Worth a try though...
It did not, so I created it and chmod'd it 700 (owner root), but it doesn't seem to have changed anything.
Ug, might be time to call support.
Yeah, I'm trying to avoid that, but I may not have a choice. What's strange to me is that I get to the point where the VI Client shows me which VMs are running on the host and asks me which folder to put them in when I'm attempting to reconnect, but then it claims that it can't reach the host, so it does seem as though some process is not responding as expected.
I have called support with this problem after the where in my system for about 2 hrs they just told me to reboot
For anyone watching this thread, the solution was to restart xinetd on the ESX host.