We’ve defined the start point of the tunnel to be port 33902 (in other words 127.0.0.1:33902). The following example shows a typical tunnel configuration. Here you can see nothing is using port 33902 on my workstation: The port number is the bit after the colon in the Local Address column. Then look carefully through the list of listening connections to see if the port number you want to use is already being used. To check if a given port is in use, grab a command prompt and type By default VMWare Server listens on port 902, so I’d pick something like 33902 for the start point. Normally I’ll pick a high port number that is similar to the port of the service I’m tunneling to. The port number for the start of the tunnel can be anything you like, as long as it’s not being used by some other service. The end is defined from the perspective of the SSH server you’re connecting to - you have to tell the SSH server where to send the traffic. The start is just a TCP port on your local machine that you will be able to connect to. Now, when you’re defining a tunnel, you define the start and end point. To get to the Tunnels configuration page, select the Tunnels category on the left. ![]() Most likely you have already created such a profile. In PuTTY define a connection profile that will let you connect to your remote SSH server. ![]() So now that we can establish an SSH connection we can define a tunnel to pipe traffic between our local machine and the remote VMWare Server over that connection. Probably the most common setup would be to use a SSH server on the same network or even the same host as the VMWare Server, but other configurations are possible too. That SSH server must in turn have unencumbered access to the host machine running VMWare Server on the port that VMWare Server is listening on, which is port 902 by default. To be able to tunnel VMWare Server traffic over SSH, you must first have a SSH server set up somewhere that you can connect to. For remote access to guest operating systems you should still SSH / VNC / Remote Desktop directly to the guest machines. Tasks like creating new virtual machines, restarting machines etc are quite do-able though. Don’t expect to be driving any Windows guest machines over this type of connection. My experience of VMWare Server over SSH is that it is slooow. Access your VMWare Server from a remote location without having to directly expose it at your network’s boundaryīefore you get too excited by the way, I should remark on the speed.Work-around firewalls that aggressively block outbound traffic. ![]() I believe VMWare Server has built-in support for SSL, which means it’s not necessary to resort to SSH tunneling for security, however tunneling can have other benefits, such as allowing you to: ![]() This post shows the typical setup of a SSH tunnel through to a VMWare Server. Once you know how to setup an SSH tunnel for one type of traffic, it’s easy to setup tunnels for other services as the only thing that changes are the TCP ports involved in the tunnel. SSH tunneling is a really neat all-purpose technique for getting TCP/IP traffic securely from you to a remote server.
0 Comments
Leave a Reply. |