Using Windows to connect to a virtual machine with VNC
This article refers to settings that are out of date and have been replaced with our web console/web VNC
Why use VNC?
VNC gives you 100%, complete out of band access to your server. If your server is ever in UP status, but not reachable, you can use VNC to connect and troubleshoot. Typical scenerios include system updates or configuration issues that prevent the server from booting, iptables rules that block you via ssh, disk checks that drop to single user mode, etc.
To connect to your server using VNC, you must first enable VNC under the options page of your server. To do so do the following:
- Log into www.vr.org
- Select your servers Dashboard under My Services
- Select Options
- Click the link to manage VNC settings
VNC with Windows
It doesn't work
The client and steps in this article are known to work.
- If you can't connect, make sure that the ip address listed in the firewall and your wan ip match. You may need to update the rule. You can always see your current IP by going to the VNC page.
- If you still can't connect, try a telnet test on your VNC port. If you are unable to telnet, local firewall rules within your network may be blocking you.
- You may also alternatively want to try with or without SSL, and with or without a password to confirm it isn't a local client issue. If you are still having trouble, please try using the recommended client specified in this howto, and if you are unable to connect contact us for further assistance.
- Make sure your client is set to trust or accept unsigned SSL certificates if using SSL.
- If you can connect and you're getting a blank screen, checkÂ the grub entry for the console parameterÂ "xencons=vfb"Â in the kernel line. If you still can't get to the console, contact us for assistance.