Can't access (manage) ESX server

[CX600]

I'm in a bit of a pickle here, hopefully someone can help.

I have a single ESX server (version 3.01 I believe). I was able to access it last week through the Virtual Infrastructure Client. This week I can't access it at all. When I try to connect, I get a message that says "Cannot connect to host . No connection could be made because the target machine actively refused it." I have tried Telnet and Secure shell as well, with the same results. I cannot access it via monitor and keyboard that are directly attached. I think the server was booted without the keyboard attached last time, so it apparently doesn't realize a keyboard is there now. Display is blank.

Is it possible to connect to an ESX server with a serial cable, and manage it via Hyperterminal or something?

The virtual machines on it are still running. The server itself is still pingable.

I am nervous about power cycling this computer, since it runs a number of important virtual servers. I guess I can set up ESX on another server under 30 day trial, in case we can't get this one to come back up after restart. I would still have to copy off any virtual machines to the other server then.

Any ideas appreciated.

 

[ArizonaGeek]

Well in order to move the files to another ESX server you'd still need to get access to the physical servers. Have you tried hooking up a USB keyboard? Remember telnet is turned off by default and SSH is not accessible by Root by default. If you have access to the guest VM's you're probably better off logging on to them, shutting them down and then power cycle the machine. Last thing on the list but if you have to, that'd be the way to do it. Make sure you have keyboard, mouse and monitor hooked up.

Cheers
Rob

The answer is always "PEBKAC!

 

[CX600]

Thanks Arizona. I finally managed to gain access to the console via the Dell DRAC. I have never used that capability on our Dell servers before, but mananged to get it figured out eventually. Once I was able to get a console, I was able to restart the mgmt-vmware and xinetd services. That seemed to fix it up.

Thanks for taking the time to respond.