Differences

This shows you the differences between two versions of the page.

--- virtualization:xenserver:xenserver_remote [2016/10/18 18:06]
gcooper
+++ virtualization:xenserver:xenserver_remote [2016/10/18 18:10] (current)
gcooper
@@ Line 17: / Line 17: @@
 :!: For best security, you should limit access to your remote XenServer by source IP address in the firewall at the remote site.
-You can get **partial functionality** by simply forwarding 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:
+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.host.or.ip:4443''
@@ Line 23: / Line 23: @@
 ===== Remote Console =====
-<note tip>A VPN connection makes any workaround unnecessary.</note>
+<note tip>A **VPN connection** makes the following workaround unnecessary!</note>
-The easiest way I've found to access the console of a VM running on a XenServer behind NAT is:
+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

Virtual Architects Support Wiki