I am now trying to setup a vSphere connection much the same as my RDP connections.
I use the VPN session details, and ideally want to use dynamic port but even with static port it's not working.
The default remote port is 3389 so even if I change this to 443, still no good.
The general settings also doesn't allow a port to be used for vSphere client.
If I use localhost:port it will also try to connect using my local PC name instead of the VPN remote IP
Also, vSphere client requires 3 ports to be opened for better functionality. 443, 902, 903
Am I missing something? Does anyone else tunnel vSphere client over SSH?
Hello,
We have focused on SSH and RDP, we've never had that request before AFAIK.
As always within the VMware ecosystem, names are hugely important. If I understand correctly you are using the VMware (Player, Workstation, vSphere) entry type, set to the VMware Infrastructure Client / vSphere client application.
My own tests show that only forwarding port 443 is indeed not sufficient. In the screenshot below, you see that I can open a browser and it does reach the server, but the vSphere client does not like it.
In the vSphere client logs[ :Error :P: 3] 2017-01-10 07:24:24.509 possible failure processing clients.xmlSystem.Net.WebException: The request failed because of a connection failure. (Unable to connect to the remote server) at VirtualInfrastructure.Utils.WebQuery.LocalizeWebException(WebException exception) at VirtualInfrastructure.Utils.WebQuery.Request(String url, Nullable`1 timeoutSecs) at VirtualInfrastructure.Utils.ClientsXml.ParseXml(Int32 timeoutSecs) at VpxClient.Login.ClientsXmlLoader.TrySinglePort(ClientsXml clientXml, Exception& activeError) System.Net.WebException: Unable to connect to the remote server at System.Net.HttpWebRequest.GetResponse() at VirtualInfrastructure.Utils.WebDownload.GetResponse() at VirtualInfrastructure.Utils.WebDownload.get_ResponseStream() at VirtualInfrastructure.Utils.WebQuery.Request(String url, Nullable`1 timeoutSecs) System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.1.151:50001... at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) --- End of inner exception stack trace --- --- End of inner exception stack trace ---
There is definetly something missing. If its only a matter of opening multiple ports, our Port Forwarder is meant for that. We need to dig more in vmWare's documentation.
Maurice