Mobile VNC solves your remote control and maintenance challenges.
|Download Demo||Download User-Guide||Buy a License (9.95 Euro per device)
Follow the active development of MobileVNC and MobileVNC vncserverlib (vnc.lib) and report feature requests, ideas and bugs here:
MobileVNC is a minimal footprint native C++ based VNC server and library software for Windows, Windows Mobile, WinCE, Windows CE and Windows embedded compact operating system. In combination with any VNC viewer software, such as the RealVNC viewer or the RealVNC Android Viewer App it is possible to remote control every Microsoft based operating system. The screenshot below shows how to control Windows 7 with MobileVNC Server Software and RealVNC Android Viewer App on a Samsung Nexus smartphone:
A VNC (Virtual Network Client) client server software provides a reliable and convenient way to access remote servers and workstations over a network. VNC als well as Microsoft’s Remote Desktop Connection implement such graphical desktop sharing system which are used since several decades for remote controlling hosts. Desktop sharing systems are specifically useful for remote management of servers or embedded computers, control systems, which do not have a graphic output device, or are hard to reach physically. The RFB protocol, which is used in VNC client and servers transmitts input, through a keyboard or a pointing device, as well as the visual output over a TCP/IP connection, in order to control the remote host.
High, network bandwidth and latency allows the fluid and fast remote control of network devices through VNC or Microsoft’s Remote Desktop Connection Services without major performance issues. Often the user is not aware that the desktop actually working on is a shared desktop that runs in a network.
Many different embedded thin clients terminals (such as the HP t5000 series, Dell Wyse Winterm, Jack PCs, DT Research DT366 TABLET) run on Windows CE as an operating system and can be controlled with this MobileVNC Windows CE and Windows Embedded Compact VNC product.
Windows CE and Windows Embedded Compact terminals are used worldwide for a multitude of different application areas, such as:
- POS – Point of Sales, Point of Purchase and Checkout terminals for electronic cash register and sales processes, either as stationary devices or as mobile checkout devices (e.g. Windows CE .NET, Win CE 5.0 platform based POS Systems).
- Mobile Barcode Reader / Scanners, 2D and 3D Barcode, for organizing logistics processes in large quantities.
- Thin Client Terminals.
- Industrial Windows CE Touch Panel Computers and Modules
While Microsoft Remote Desktop Services uses the proprietary Remote Desktop Protocol , VNC uses the open and published RFB protocol, which was already mentioned above. Microsoft Remote Desktop Services is available for all major Windows versions as host service and for all Windows versions as client implementation. There are also some open source implementations of RFB clients and servers, such as the XRDP - an open source RDP server implementation.
As VNC’s RFB protocol is an open and published protocol it attracted a lot of client and server implementations on all major platforms. Examples for VNC implementations are RealVNC, UltraVNC and TightVNC which offer downloads of free client and server software for different platforms.
MobileVNC on the other hand is a specific VNC server implementation for Windows Mobile, PocketPC, Windows Embedded Compact and Windows CE platforms. MobileVNC implements the standard features of the RFB protocol version 3.3 and adds file transfer capability in combination with UltraVNC clients.
MobileVNC was originally inspired by the SynCE project, that implemented an open source synchronisation solution between Linux Desktops and Windows Mobile clients by implementing the ActiveSync protocol.
MobileVNC server is no port of the original open source VNC server code for Windows, instead it is a complete new C++ based implementation on the Windows CE platform. The Hextile encoding algorithm used in the original RealVNC Server was bugfixed and modified to offer more performance on mobile devices.
The MobileVNC server offers following features:
- Raw Encoding (quite slow according to the network bandwidth)
- Hextile Encoding (good performance according to the bandwidth and to the processor time used)
Both Encoding styles are offered with 8bit and 16bit pixel depth. Reducing the images to 8bit pixels offers a really good performance over LAN and WLAN and an acceptable performance over Bluetooth connections.
- File-Transfer with UltraVNC VNC clients!
- Confirm connection function.
- HTML5 noVNC client support
- Autostart feature
- Fully configurable with text ini file
- Outgoing connections to listening viewers (vnc viewers in listening mode)
- Silent startup
- Automatic Reconnect to VNC Routers or listening VNC Viewers
MobileVNC Platform Compatibility
The MobileVNC VNC server offers a lightweight and small footprint VNC server solution for all Microsoft platforms that are based on the Windows CE kernel (on Windows Phone 7 and up this native VNC server software cannot be used by endusers and is therefore restricted to OEM bundle usage) and for all Windows32 system kernels. Refer to following graphics to check all Windows CE and Win32 based operating system platforms:
Users report that the Windows CE, Windows Mobile, Windows Embedded Compact VNC server is successfully running on following devices:
- Symbol MC70 Barcode
- HTC Touch 3G, Windows Mobile 6.1
- Sprint PPC 6700, Windows Mobile 5.0 (screen rotation not supported)
- HP iPAQ RX3716, ARM PocketPC 2003 Pro device, internal WLAN and Bluetooth interface
- T-Mobile MDA, ARM PocketPC 2003, SanDisk Wi-Fi SD WLAN Karte 802.11b
- HP iPAQ 4155, ARM PocketPC 2003 device, integrated WLAN
- FS Loox 600, ARM PocketPC 2002 device, Symbol Wireless SD card
- HP t5000, X86 WindowsCE.NET 4.2 thin client device, LAN Network
- Windows 7, x86 Lenovo Laptop