Dear all,
We have running this VM Server for almost one year with any issue.
Last night we have relocated our VM Server to a new network with new WAN IP address allocated by ISP.
Prior to the server relocation, we have updated the Management IP of the VM Server but we did not update the IP address of the Virtual Machine.
After relocation, we were able to boot and access the VM Server, we can also power on the virtual machine using VMware Client.
When we want to access the console to update the new WAN IP address, it just give us a blank white screen. We have rebooted the machine many time but with no result to access all the virtual machine.
Is there any magic that we can access to the console of the virtual machine, any help is really appreciate as we have lot of important data in the virtual machine.
We have phsyical access to the server.
Version of the VMware used.
VMWARE Infrastructure Client Version 2.5.0
VMware Esx Server 3i Verison 3.5.0
Virtual Machine - Centos 6 32bits
Thank you and we look forward to any advise!
Welcome to the Community,
do you have a firewall (port filters) between the Client and the host? Check whether the necessary ports (902/903) are open.
André
Message was edited by: a.p. - forgot to paste the KB link http://kb.vmware.com/kb/1012382
Dear Sir,
I have disabled all firewall on the client. A nmap port scan on the VMware server show,
Scanning WAN IP [1000 ports]
Discovered open port 80/tcp on WAN IP
Discovered open port 443/tcp on WAN IP
Discovered open port 5989/tcp on WAN IP
Discovered open port 902/tcp on WAN IP
Completed Connect Scan at 03:04, 44.70s elapsed (1000 total ports)
Nmap scan report for WAN IP
Host is up (0.0013s latency).
Scanned at 2012-08-11 03:03:24 Time for 45s
Not shown: 996 filtered ports
PORT STATE SERVICE
80/tcp open http
443/tcp open https
902/tcp open iss-realsecure
5989/tcp open wbem-https
Port 903 is missing.
André
Dear all,
No firewall in between server and client. I have disabled all firewall on client. How do I open up port 903 on the VM Server?
Thank for replying and your time is appreciated.
I could be wrong, but since you just relocated the host to a new network, I don't think this is something on the ESXi host, but rather something with a firewall setting on your ISP's network!?
André