NoMachine NX - Resources: Documentation

	Home > Support > Documents > Installing NX on a PocketPC Linux device

Installing NX on a PocketPC Linux device

An embedded version of NX Client is available for HP/Compaq iPAQ and Sharp Zaurus devices. NX Client Embedded Edition includes a version of NX client software compiled for QT Embedded version of QT toolkit libraries, NX protocol compression software, an X server based on XFree86 kdrive server, SSH client and X utilities needed to configure and run user sessions on a remote NX Server.

All the remote access protocols supported by desktop version of NX Client are supported by the embedded counterpart. This means that NX Client Embedded Edition is able to run X, RDP and VNC sessions without the need for any additional software.

The following document explains, step by step, how to configure and run NX Client on an iPAQ device. The same procedure applies, almost unmodified, to Sharp Zaurus. Customers are invited to report problems and differences identified setting up NX on their own environment.

NX Client on HP/Compaq iPAQ PocketPC

To use NX Client on HP/Compaq iPAQ PocketPC you need:

An iPAQ PocketPC with installed Familiar Linux and OPIE Embedded Palmtop Environment.

Detailed information on how to setup Linux and OPIE on iPAQ are available here and here. Zaurus users need to install OpenZaurus packages. There are incompatibilities between the kdrive XFree86 server and kernel distributed with present version of the device.

Step by step guides on how to install OpenZaurus packages are available here.

A working network connection to the NX Server.

Information on how to setup PPP serial connection and IP routing are provided below.

NX Client and Familiar Linux

NX Client was tested on Familiar Linux version: v0.5.3 , v0.6 , v0.6.1.

Connecting iPAQ PocketPC to your desktop computer using PPP

With the recent releases of Familiar, almost everything has already been set up by the operating system's installation procedures. To test your device's connection to the network you'll need a computer routing the traffic betweeen your device and the LAN or WAN where NX Server is plugged. Here's what you need to do to get PPP up and running.

Close minicom or any other terminal program that may have a connection to your serial port.

If you are getting message "Connect script failed", the PPP modules probably are not loaded at boot time. This can be fixed by adding the lines "slhc", "ppp_generic", and "ppp_async" to /etc/modules.

If this doesn't fix the problem, try to execute this command after login:

echo "slhc 
ppp_generic 
ppp_async" >> /etc/modules

and then reboot the iPAQ.

Now, run this command from your desktop computer:

/usr/sbin/pppd /dev/ttyS0 115200 {IP of your PC}:{IP of your IPAQ} 
nodetach local noauth nocrtscts nodeflate nobsdcomp lock user ppp 
connect "/usr/sbin/chat -v -t3 ogin--ogin: ppp

Add parameter "debug" to the above command if you want to see LCP debugging information.

If connection is successfull, local and remote IP addresses will be reported by PPP daemon. Now the link between the Linux machine and your iPAQ device is running. Now you need to route the traffic coming from device to the network where your Linux computer is connected.

Install the ipchains kernel module on your Linux desktop computer.

Check if ipchains kernel module has already been loaded at boot time by running "lsmod". If not, run "insmod ipchains".

Set up the routes from iPAQ to desktop computer's LAN.

NoMachine provides a ready-made IP masquerade script to do this. You will probably need to slightly adapt the script to reflect your network's IP numbers. You can find the script here.

Installation of NX Client on HP/Compaq iPAQ PocketPC

Download the latest version of NX Client from NoMachine web site.

Install the package.

Package should have the extension ".arm.ipk.". Open a console window and type the following command:

ipkg install nxembedded-XXX.arm.ipk

Restart OPIE.

You should find the NX Client icon on your desktop in the Applications group.

iPAQ is a trademark of Compaq Information Technologies Group
Zaurus is a trademark of Sharp Corporation

	Technology Brief


		Data encryption and security NX security is guaranteed at every layer involved in the communication process. NX uses SSH public-key encryption and 128 bit volatile random cookie generation.


		Windows file sharing support Share a file, folder or entire disk from your local Linux computer and let it be accessed by the remote applications running on the NX server. Full support of industry standard SMB protocol.


		Unified support for all major remote desktop protocols Thanks to its outstanding compression performances, NX is able to deliver X, RDP and RFB remote sessions using the same client. This is achieved by translating "foreign" protocols into X-Window, the native protocol of NX.

Home |