Difference between revisions of "RealVNC"
(Created page with "__FORCETOC__ ==How to configure RealVNC Server on Windows VPS==") |
(→How to configure RealVNC Server on Windows VPS) |
||
| Line 1: | Line 1: | ||
__FORCETOC__ | __FORCETOC__ | ||
| − | ==How to configure RealVNC Server on Windows VPS== | + | =='''How to configure RealVNC Server on Windows VPS'''== |
| + | |||
| + | Once you have download and installed RealVNC you will need to make sure that you have an exception in your windows firewall to allow connections to your Public IP. | ||
| + | |||
| + | 1. Open Windows Firewall and add an inbound rule | ||
| + | 2. Click on Port and define the port you want allow (default is port 5900) | ||
| + | 3. make sure you allow TCP and choose Allow Connections | ||
| + | 4. add an outbound rule and repeat steps 2 and 3 | ||
| + | |||
| + | |||
| + | '''Configure VNC Usermode and Server Mode''' | ||
| + | |||
| + | While the VNC Server in Service Mode icon does not appear in the Desktop | ||
| + | Tray in an RDP session, it will most likely be running in the background. | ||
| + | Could you do the following: | ||
| + | |||
| + | - Start VNC Server in Service Mode. | ||
| + | - Open VNC Server in User Mode, make note of the IP Address (you will need | ||
| + | this to connect to the VNC Server in Service Mode) | ||
| + | - Close VNC Server in User Mode, then exit out of the RDP session. | ||
| + | - Enter the IP Address that was shown on the VNC Server in User Mode into | ||
| + | the VNC Viewer application (please note, the IP of your User Mode Server was | ||
| + | probably something along the lines of: "192.168.5.1:1" - in order to connect | ||
| + | to the Service Mode Server, you will need to connect to "192.168.5.1" | ||
| + | (without the :1 at the end). | ||
| + | - You should now be prompted for a password and username upon connecting via | ||
| + | VNC Viewer, by default these details are those of the Windows System User | ||
| + | who launched VNC Server. When you connect you will be prompted with the | ||
| + | local login screen. | ||
| + | |||
| + | From here you should be able to login and see VNC Server in Service Mode in | ||
| + | the Desktop Tray, and be able to configure it in the same way you were able | ||
| + | to configure VNC Sever in User Mode. | ||
Revision as of 20:08, 21 January 2014
How to configure RealVNC Server on Windows VPS
Once you have download and installed RealVNC you will need to make sure that you have an exception in your windows firewall to allow connections to your Public IP.
1. Open Windows Firewall and add an inbound rule 2. Click on Port and define the port you want allow (default is port 5900) 3. make sure you allow TCP and choose Allow Connections 4. add an outbound rule and repeat steps 2 and 3
Configure VNC Usermode and Server Mode
While the VNC Server in Service Mode icon does not appear in the Desktop Tray in an RDP session, it will most likely be running in the background. Could you do the following:
- Start VNC Server in Service Mode. - Open VNC Server in User Mode, make note of the IP Address (you will need this to connect to the VNC Server in Service Mode) - Close VNC Server in User Mode, then exit out of the RDP session. - Enter the IP Address that was shown on the VNC Server in User Mode into the VNC Viewer application (please note, the IP of your User Mode Server was probably something along the lines of: "192.168.5.1:1" - in order to connect to the Service Mode Server, you will need to connect to "192.168.5.1" (without the :1 at the end). - You should now be prompted for a password and username upon connecting via VNC Viewer, by default these details are those of the Windows System User who launched VNC Server. When you connect you will be prompted with the local login screen.
From here you should be able to login and see VNC Server in Service Mode in the Desktop Tray, and be able to configure it in the same way you were able to configure VNC Sever in User Mode.