Actually My doubt is that, first i will explain you the setup i made it on my test lab.
1. I have 2 networks (1. public network 2. Private network)
2. Public Network is for Management network to access my vCenter from Any where(and it has private network aswell)
3. and 2 Private network i used for rest of vm's and hosts to interact etc..
this senario i can able to access my virtual lab from public or private with no impacts, but i have an problem when i try to open console of my vm it's not connecting i am not able to access my guest operating system (that's only accessing from Public network)
Quation is that , The cause of not accessing vmconsole because of both differnt networking ? do we need configure some thing like NATTING between this networks ?
Please help me ...........!
Please check wethere your machine from where you are trying to connect is resolving the ESXi hostname and VM Name as configured in DSN.
Try to ping the ESXi Host and VM with the hostname from your machine you are trying to connect. And if you are not able to ping the same with DSN name , add the ESXi hostname , VM Hostname and vCenter (if exist) and IP address in your local machine etc/hosts file
yes i have configured my DNS is private network and i am able to resolve hosts form virtual machine but still i am getting same error..!
Note:- there is no connectiviy from my public network and private network both are completely different
For your reference quickly made a sample diagram please look at it.
The problem is the way vCenter and the vSphere client coordinate your console connection.
Although you're connected to vCenter the console is actually a direct connection to the ESX host.
Think of it like a URL on a webpage. We're 'on' http://communities.vmware.com but if you click the link http://www.google.ca you'll redirect to google, you don't access it 'through' communities.vmware.com, you connect direct.
So even though you've assigned the ESX host a public IP, vCenter 'knows' it as 192.168.1.4, so when you say "open console on VM" it says "Okay, connect to this port on 192.168.1.4" which is not accessible from your 139.130.xxx.xxx. network.
Did you add the ESXi host to vCenter via it's IP of 192.168.1.4 or did you add it via an FQDN?
Ensure your client "from the client your open vSphere Client", able to ping your ESX host and telnet to port esxhost:902.
If you have any firewall from your client network to vSphere(ESX) host(vice-versa). Make sure open the port 902 first. You probably had open the 902 port but maybe only for vCenter Server not for your ESXi host.
You may test by doing this :-
If you added it with the IP only then vCenter will tell your client "Connect to 192.168.1.4", which won't work if you're on the public network.
Can you resolve the ESXi host's name from the public network? If you can, does it provide you with a public network IP or the private network IP?
I should point out that having a publicly accesible ESXi host is NOT a good idea.
If you want manage it remotely you should probably just RDP into the vCenter server and work from there.
But if you want to throw caution to the wind.. re-add your ESXi host to your vCenter using an FQDN that on the private network would resolve to 192.168.1.4 and on the public network resolves to a 130.139.xxx.xxx address and that should solve your issue.
It's just not a good idea to have your ESXi host exposed like that..