NB: Depending on your Internet connection your Public IP address may change every time you re-dial or reboot. On your Handheld PC you must connect to the Internet Then in the VNC Client Connect to box you must type the IP Address found in Step 8 followed by the desktop suffix e.g.
Type the IP address of the host system into the VNC Client connection box followed by the Desktop suffix e.g. Select the Details tab to view the IP address information.Double Click the 'Incoming Connections' Entry for your device.You will need to know the Dial-up Server's designated IP address * NB: You will need a local DNS or WINS server in order to accomplish this If you are connecting using a Dial-in connection If for example the IP Address is listed as 192.168.1.165 you would then type the following in the VNC Client's address box: 192.168.1.165:0 To connect to the computer at Address: 192.168.1.165 (Under non-Windows platforms consult the OS documentation on how to lookup the IP address) The machines network IP address will be listed as 'IP Address.'.At the prompt type ipconfig and press enter.If running Windows 95, 98, 98SE, Millennium type: command.If running Windows NT 4.0, 2000, XP or 2003 type: cmd.To discover the IP address of the computer running the VNC Server: You should now try and connect to the VNC Server using it's Network IP address. If the VNC client cannot connect to the remote computer using the correct Computer Name then the LAN you are using may not be sophisticated enough to connect using the Name*. So on the Handheld PC in the VNC Client connection box you would type: Inspiron:0 To connect to the computer names Inspiron, which in this example is running Microsoft Windows In the above example the computer name is Inspiron. The computer name will be listed in the 'Full computer name:' area as shown below.To discover the name of the VNC Server computer. Whether you can use the Remote Computers Name will depend on the complexity of the LAN you are using. To discover the IP Address / Name of the computer you are connecting to: If you are connecting over a Local Area Network 192.168.0.1:0 -or- snoopy:0 If you are connecting to a Unix / Linux system then the suffix number will have been defined when you started the server e.g. You must add :0 after the physical Address / Name of the server e.g. If your VNC server is Windows based, the suffix part of the VNC Server address will generally be the same. You can download the VNC View Client package from the HPC:Factor download centre of from the download section of this articleīut what to put in the VNC connection box? This will depend on how you are connecting to your server, and even on what Operating System your server is running. You've installed VNC server, and now it's time to connect your Handheld PC to it.įirst you need to install the VNC Views Client for Windows CE onto your device. Only allows you to connect to a Remote PC at a range of 5 metres Pointless Specify the Server Name / Address and Desktop Number Requires expert knowledge May be Expensive HPC2000 only Direct Cable Connection
Provides the freedom of the Internet and an additional layer of security Con. VNC offers NO security for your PC Securing the connection requires expert knowledge VPN Tunnel Convenient for accessing you PC from anywhere Con. Requires Modem Requires Available Phone Line Slow Internet Provides the most security on a virtual level Con. Requires Network Hardware Remote machine must be on the LAN Dial-in Provides the fastest possible VNC connection Con. Reliability and speed do trump an initial set up phase of VNC Connect still.Pro. And in my case, I needed to open a port on my router, and to set up Dynamic DNS-something that you wouldn't normally do when using TeamViewer, for example. One notable solution was AnyDesk, which worked quite well for me, but RealVNC's VNC Connect took the crown as it was more customizable for my needs and faster too.ĭo note though, that VNC Connect requires more effort to set up as well. But what to do when they both fail at the same time? So I have been using these 2 services concurrently to have a backup when 1 of them fails. The same, in my experience, was true with Chrome Remote Desktop-sometimes it would fail me. TeamViewer was not working reliably for me and sometimes I was not able to connect to my desktop when I needed to. I switched to RealVNC's VNC Connect from TeamViewer, and Chrome Remote Desktop for purpose of connecting to my desktop computer remotely and RealVNC's solution works very well for me.