December 1, 2009 – 9:11 am
Virtual Private Network (VPN) is a technology allowing you to establish a secure network connection over an insecure public network. In Virtuozzo 3.5.1 SP1 or greater, you can make Virtual Environments operate as VPN clients connecting to VPN remote access servers.
By default, the VPN support inside a VE is disabled. However, you can use the –vpn option of the vzctl set command to enable a VE to take advantage of the VPN technology benefits.
[text]C:…Administrator>vzctl set 101 –vpn on –save
Command ‘set’ is successfully finished
C:…Administrator>vzctl restart 101[/text]
To then check if the VPN is supported and on type:
[text]C:…Administrator>vzlist -o nettype 101
NETTYPE
routed+vpn[/text]
Unless you purchased a service with an application such as FOREX Traders or PLESK, the server usually comes with a standard install which generally has the minimum installed to prevent a “bloated” installation. Windows Installations, do come with IIS pre-installed and ready to go and can be removed if required.
If you have any specific needs as regards software, please contact a sales representative to discuss.
With a Linux Server, you access the server via SSH. In order to do this you will need an SSH Client, of which we recommend PUTTY, your IP address and your user credentials.
Once connected, you will administer your Linux system from the Command Line Interface.
With Windows, you use Remote Desktop Connection that comes with Windows XP or Vista. This can be found in your Start Menu in Accessories. (Windows XP is under Communications in Accessories). Again, you will need your IP address and user credentials to log in.
Virtuozzo takes all of the required security patches from the hardware node. Virtuozzo will not work with certain security patches that Microsoft releases so it is imperative that you do not try to do a Windows Update on your VPS as you will most likely get an error like below:
Error invoking external utility: ERROR:Virtuozzo API function call ‘VzkrnlStartVps’ failed dwErr=0x000004FB ERROR:Container X is not started ERROR:Exec ‘@VzOnShutdown’ failed in container X
If however, you do install updates manually, we will warn you to expect us to either have to revert to your last backup, or in the event you have not performed one recently, then you will need your VPS reinstalling.
