VMware Cloud Community
bnk
Contributor
Contributor

vSphere Client 5.0 can connect to vCenter but not ESXi server.

If i connect vSphere Client 5 to an ESXi host on a server that is on the same subnet as the ESXi server, everything works fine. If i do it on an other subnet I can connect to vCenter but not to an ESXi host???

Does anyone have an explanation why it is not possible to connect to an ESXi server when I am on another subnet?

I got the following error:

vSphere Client could not connect to "xxx.xx.xx.xx".

An unknown connection error occurred. (The request failed because of a connection failure. (Unable to connect to the remote server)). 

Reply
0 Kudos
10 Replies
nielse
Expert
Expert

Did you check the logs for any errors when you connect?

Have you tried restarting the management agents?

@nielsengelen - http://foonet.be - VCP4/5
Reply
0 Kudos
bnk
Contributor
Contributor

How do i restart the management agent on an esxi 5?

Which logs are you refering to. Logs om ESXi or the one I am making the connection from?

Reply
0 Kudos
iw123
Commander
Commander

Theres no reason why it wouldnt work across subnets by default - however it may be that there is a firewall/access list blocking your access to the server. If memory serves you need to be able to talk to the esxi servers on port 902, 903, so if you have an access list on the router between your subnets then this is likely to be the problem.

When you are already on the subnet, then you won't be hitting the access list so would expect that to work. 

*Please, don't forget the awarding points for "helpful" and/or "correct" answers
Reply
0 Kudos
iw123
Commander
Commander

also, to test connectivity you can telnet to port 902.

btw - can you access the server using a web browser, or is it just the vi client that can't connect ?

*Please, don't forget the awarding points for "helpful" and/or "correct" answers
Reply
0 Kudos
nielse
Expert
Expert

The logs on the ESXi host. Regarding the restart of the agents I provided a link to the KB on how to do this. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100349...

@nielsengelen - http://foonet.be - VCP4/5
Reply
0 Kudos
aravinds3107
Virtuoso
Virtuoso

May be a firewall which is blocking when accessing from another subnet, Take a look at this KB for port requirements

How do i restart the management agent on an esxi 5?

If you have access to DCUI you can restart from there, check this KB or SSH to the host and run /sbin/services.sh

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful |Blog: http://aravindsivaraman.com/ | Twitter : ss_aravind
Reply
0 Kudos
john23
Commander
Commander

check lockdown mode.

Thanks -A Read my blogs: www.openwriteup.com
Reply
0 Kudos
iw123
Commander
Commander

lockdown mode will block access regardless of which subnet you are trying to connect from. 

*Please, don't forget the awarding points for "helpful" and/or "correct" answers
Reply
0 Kudos
GreatWhiteTec
VMware Employee
VMware Employee

I'm not sure how your infrastructure looks like. Are the separate subnets just VLANs within a L3 switch/Router? or are they actually totally separate networks divided by a firewall in between? If there is a firewall, there could be a rule to allow you to connect to vCenter but not ESXi. Again, not sure what your set up is like, so I'm fishing for info here...

Reply
0 Kudos
bnk
Contributor
Contributor

I found the error.

The Management Console network had the wrong Default Gateway:)

My mistake.

But thanks for all the replys.

Reply
0 Kudos