Best VNC?

[IronGeek]

Hi I've noticed that there is more than one version of VNC for the Pocket PC. The one I have (don't have it in front of me, so I don't know who compiled it) runs way too slow to be useful. What is the best version to get and how can I speed it up? Thanks.

[Dave Beauvais]

I use this one (http://www.cs.utah.edu/~midgley/wince/vnc.html) the most, but have also tried this one (http://www.allware.com.mx), which actually allows you to send a right-click. (Click the "Pocket PC" link on the left of the page.) I use the first one most because it seems more stable and responsive. However, both of them are painfully slow even over a wireless LAN connection. Whenever possible, I'll use TightVNC (http://www.tightvnc.com/) on my laptop, but when I'm travelling with just my Pocket PC, sometimes one of these PPC VNCs has to do.

Most of the servers or workstations I'd need to connect to remotely support terminal services or remote desktop, so I use the PPC's Terminal Services Client the most. This is far superior to VNC in terms of function and responsiveness, and I highly suggest it if you can make use of it. I threw together a little how-to (http://www.beauvais1.com/ppc/ppc_term_svcs/index.html) for getting the TS Client to connect to WinXP's Remote Desktop.

--Dave

[MobiliT]

I use this one (http://www.cs.utah.edu/~midgley/wince/vnc.html) the most, but have also tried this one (http://www.allware.com.mx),...
Wow, very informative Dave. Thanks for such a detailed post.

[Dave Beauvais]

Wow, very informative Dave. Thanks for such a detailed post.
Hmm, I can't tell if that was sarcastic or not. Those are links in that sentence. :)

--Dave

[MobiliT]

Hmm, I can't tell if that was sarcastic or not. Those are links in that sentence. :)
--Dave
haha :wink:
I actually was being serious. I had no idea so many VNC options were out there for each platform.

[Sooner Al]

An additional comment is to note the VNC data stream is not encrypted like the TSC/Remote Desktop link is. Over the public internet that can be a security issue. A solution is to run the VNC connection through a VPN tunnel.

Also, running a TSC session through a VPN tunnel negates the need to open additional ports (ie. TCP Port 3389) in any firewall. You can also access multiple XP Pro Remote Desktop or W2K/W2003 Terminal Servers behind a firewall via the VPN tunnel since the PPC 2002/2003 OS TSC can not call using anything other than the default port (TCP Port 3389). Simply connect the VPN link then start the TSC session.

Here is how I do VPN and TSC together to access my home LAN.

PpvVPN How-I-Did-it (http://www.oecadvantage.net/ajarvi/PpcVPN.html)

My TSC/RD page...

TSC How-I-Did-it (http://www.oecadvantage.net/ajarvi/TSC.html)

Via direct dial to a XP RAS box...

RAS How-I-Did-it (http://www.oecadvantage.net/ajarvi/PpcRAS.html)

Dave...great page...

[Dave Beauvais]

Thanks for that VPN page. That's really useful info!

--Dave