Timeline for Connecting to vCenter Server, Unable to connect to the MKS: Failed to connect to server xxx.xxx.xxx.xxx:902
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 26, 2014 at 12:21 | comment | added | Mike Naylor | Ricky, I don't disagree, I just never say something CANT be done unless I know for sure. It may be possible if you're a networking genius or a developer from VMWare who knows the intricate ins and outs of the software... @Mirx, I'm not familiar with Juniper equipment but setting up a VPN between the two networks should work fine as long as traffic on the necessary ports is allowed to cross the VPN. Make sure you setup the VPN correctly and also verify the firewall allows traffic from the LAN to the VPN zones on both sides on the ports for VMWare. | |
| Mar 26, 2014 at 8:26 | comment | added | mirx | @MikeNaylor: just another noob question: I know that its possible to setup VPN on JSRX - never done this before but will this be good for my needs? Found this art: juniper.net/techpubs/en_US/junos12.1x44/topics/example/… | |
| Mar 26, 2014 at 7:47 | comment | added | mirx | @RickyBeam: Ok thanks guyz but I need a little more help with this :) I understand that I need to setup VPN client on the computer in the remote network (lets say, its VPN IP: 10.8.0.2) and VPN server on the same virtual machine where I have my vCenter Server istalled? (lets say, 10.8.0.1). And when I setup such connection should I do a port forwarding, 10.8.0.2:443 -> 10.8.0.1:443? Will it be enough for this to work as I want? | |
| Mar 25, 2014 at 22:05 | comment | added | Ricky | @Mike, more than that... It. Cannot. Be. Done. vCenter is going to provide the local address of the esx server, which is NOT the address to which he needs to connect. This is communicated through an SSL connection were it cannot be rewritten. The only solution is to be in the LAN (directly, vpn, or using global addresses) with the servers. | |
| Mar 25, 2014 at 21:01 | comment | added | Mike Naylor | What he is saying is that this would be very difficult to setup as you have a NAT rule to point inbound traffic to the vCenter server but the Console connections come from the host itself. Currently the outbound console traffic is not being routed and translated to your remote machine which results in the MKS error and the connection timing out. Attempting to setup NAT rules for this would be difficult and most likely result in more problems than it solves. I would highly recommend a VPN connection to accomplish this as other options open up more security holes in your firewall. | |
| Mar 25, 2014 at 19:56 | comment | added | mirx |
So what do I need to be able to make such connection? I dont need to forward ports 902 and 903 on my JSRX? Im very new to networking, thanks for help :)
|
|
| Mar 25, 2014 at 19:55 | history | answered | Ricky | CC BY-SA 3.0 |