This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
virtualization:xenserver:xenserver_remote [2014/10/02 09:41] gcooper |
virtualization:xenserver:xenserver_remote [2016/10/18 18:10] (current) gcooper |
||
---|---|---|---|
Line 15: | Line 15: | ||
===== Remote XenCenter ===== | ===== Remote XenCenter ===== | ||
- | :!: You can get partial functionality | + | :!: For best security, you should limit access to your remote XenServer |
- | The easiest way I've found to access the console of a VM running on a XenServer behind NAT is: | + | You can get **partial functionality** by simply forwarding TCP port 443 into the remote XenServer, but not console access (XenServer or VM). Even if you forward a non-standard port (i.e. 4443) in to port 443 on the XenServer, you can still add the remote server to XenCenter: |
+ | |||
+ | '' | ||
+ | |||
+ | ===== Remote Console ===== | ||
+ | |||
+ | <note tip>A **VPN connection** makes the following workaround unnecessary!</ | ||
+ | |||
+ | Without a VPN connection, the easiest way I've found to access the console of a VM running on a XenServer behind NAT is: | ||
- Enable remote SSH access directly to the XenServer | - Enable remote SSH access directly to the XenServer | ||
- | * You can forward a non-standard port at the firewall (22222) to the standard port 22 at the XenServer | + | * You can forward a non-standard port at the firewall (i.e. 22222) to the standard port 22 at the XenServer |
- To access a VM's console, you must tunnel through localhost (the XenServer) | - To access a VM's console, you must tunnel through localhost (the XenServer) | ||
- Use SSH port forwarding to forward a VM's VNC port (5901, 5902, 5903, etc.) to ' | - Use SSH port forwarding to forward a VM's VNC port (5901, 5902, 5903, etc.) to ' |