JUN
28
2004

Preview on kNX Client and FreeNX Server for LinuxTag Visitors

A Task Force Team of KDE and Knoppix hackers and enthusiasts created "just
in time" for LinuxTag 2004 two
programs which harvested an overwhelming response from visitors: FreeNX
Server and kNX Client. Although not yet officially released, several
presentations showed a well working preview of the KDE version for the speed
boosting NX Terminal Server technology.

NX Technology provides exclusive
compression techniques that make it possible to run complete remote cross
plattform desktop sessions using narrowband Internet connections. At speeds
as low as those offered by a modem or by ISDN it's possible to work fluently
with the remote desktop shown full screen. Besides providing high
performance on low bandwidth connections NX technology enables the user to
disconnect from and reattach to existing sessions running on the Terminal or
Application Server. Even sessions lost due to network problems can be
recovered easily. Therefore NX technology is expected to have a huge impact
on Thin Client architectures as well as well as mobile computing.
Enterprises, Internet cafes and similar users already appreciate KDE's Kiosk
framework
which provides a simple way to disable certain features in KDE to
create a more controlled environment. With mature technologies like Kiosk
as well as FreeNX KDE proves to be the ideal choice for Terminal and
Application Server deployment.

Both the FreeNX Client and the FreeNX Server will be available soon at
Kalyxo.org. Kalyxo is a project which focuses on KDE/Debian integration as
well as providing Debian-specific system tools for the enterprise.
Kalyxo.org will host the FreeNX source repository for all distributions. It
will host and maintain GPL'ed NX Debian packages.

Fabian Franz from the Knoppix Development Team is the driving force behind
FreeNX Server. kNX Client is developed by Joseph Wenninger.
Gian Filippo Pinzari, NX Development Architect and KDE enthusiast from NoMachine provides the foundation of the
NX Terminal Server technology by developing the GPLed libraries which are
used by the FreeNX Server. NoMachine is one of the sponsors of the KDE
Community World Summit
("Akademy") and will be present there as well.

More information on NX Technology:
http://www.nomachine.com/resources.php

You are invited to test NX Technology at:
http://www.nomachine.com/testdrive.php

Photos:
1. Joseph Wenninger, Kurt Pfeifle and Fabian Franz working on the kNX
Client.
2. Knoppix and KDE developers present the kNX Client and FreeNX Server
during LinuxTag 2004.
3. KDE core developer Joseph Wenninger in front of the Login Window of the
FreeNX application "kNX client"

Comments

hi,
tested it today with dsl and works really good. its a great one and i am looking forward to install an thin-client computerroom at school.


By gunnar at Sun, 2004/06/27 - 5:00am

This certainly rocks!
Would it be possible to integrate it into krdc?


By chico at Mon, 2004/06/28 - 5:00am

Well, I don't see why it couldn't be integrated.

If I remember right it was on the kde 3.3 feature plan.
(but I can't find it anymore, so might be moved to 3.4)

NX is surely going to rock.


By Mark Hannessen at Mon, 2004/06/28 - 5:00am

If it was on the 3.3 feature plan, it surely should be parr of the 3.3 release, no?

I believe the reason for the "just-in-time" sentence of the story above may be that they rushed to finish it before 3.3 freeze, no?


By I-want-kNX-in-K... at Mon, 2004/06/28 - 5:00am

If it's now not listed in the feature plan then it will not be in KDE 3.3.


By Anonymous at Fri, 2004/07/02 - 5:00am

It should be doable to integrate the kNX backend classes into krdc and other tools


By Joseph Wenninger at Tue, 2004/06/29 - 5:00am

It seems as though the KDE Debian/UserLinux proposal was not just lip-service then? This is the sort of stuff Enterprizes want to hear, not arguments about licenses and developing proprietary software for free.

Working with Novell Zenworks and distributed VB apps, I certainly know the major problems 'fat' clients can cause - and it's worse than I ever thought possible. Distributing the right DLL versions, ini files, distributing database passwords (encrypted in ini files!) on the client for database access, MDAC components..... That's just the tip of the iceberg. Centralizing this whilst using clients in the correct manner would be a godsend.

This seems to have come along at a very opportune moment. I sincerely wish you all the best at Linuxtag 2004, and let us know the scale of interest. It should be huge.


By David at Mon, 2004/06/28 - 5:00am

these printing issues with thin clients.
On a local net it's easy, since you can have a cupsd running on the clients which have printers connected. With the browsing capabilities of cups an available printer will show up as soon as it's 'online', but _what_ if you want to connect via the internet? I don't want to open port 631 and I don't want to fiddle with a vpn...


By thomas at Mon, 2004/06/28 - 5:00am

http://www.nomachine.com/faq.php#21

Is it printing to local printers supported in NX?

NX provides support for SMB protocol, by which both local printers and file-systems can be made available to the remote session. Currently, printers and file-systems are "mounted" by the NX server. These resources can in turn, be mounted by a WinTSE machine. All the SMB communication, that is both file access and printing, takes place compressed through ZLIB. The compression level depends on the link speed. Enhancements have been added to the GUI to simplify sharing a printer or a resource but this is still a work in progress. At the moment there are still problems to fully integrate NX client with the local printing system (e.g. CUPS or Win printing).


By Debian at Mon, 2004/06/28 - 5:00am

The upcoming NX-1.4 will start to support printing from your remote X11 sessions to your local printers. The current 1.3.2 release doesnt support this yet -- but it supports all the speed gains you read about in the article and comments.

To test the 1.4, look for the "1.4 snapshot" release on NoMachine.com. It is there in source form and you need to compile it.

If you are a Debian user, visit Kalyxo.org for *.deb packages with a working "nxtunnel" script (that serves as a temporary placeholder until "FreeNX Server" is fully released).


By Kurt Pfeifle at Mon, 2004/06/28 - 5:00am

Any word on how this compares or is different then *VNC? Outside of the cooler domain name of course.

We use a couple of VNC servers at my .edu and they work really great.

Downloading eval NX client now...


By Ian Monroe at Mon, 2004/06/28 - 5:00am

To answer my own question, NX appears to actually be some sort of wrapper around VNC and X Windows. And the sound server, which I was impressed by. It appears to have some sort of support for file and print sharing as well.


By Ian Monroe at Mon, 2004/06/28 - 5:00am

Wrapper around VNC? This sounds wrong.


By Anonymous at Mon, 2004/06/28 - 5:00am

You get the selection of Unix, VNC and Windows as your Desktop. I assume Unix means X11? But I dunno really. Their test servers are swamped, as to be expected.

For some reason running with multimedia support and Amarok conflicts, even though they're both using artsd.


By Ian Monroe at Mon, 2004/06/28 - 5:00am

From http://www.nomachine.com/faq.php: "NX is about building the next web on top of remote execution and tunneling of arbitrary protocols (X, RDP, SMB, HTTP, IPP, RSYNC, Audio, Video) in a peer-to-peer network."

So you can tunnel VNC through NX too but it's not needed/used to tunnel X.


By Anonymous at Mon, 2004/06/28 - 5:00am

NX is NOT a wrapper around VNC. NX (for unix) has nothing to do with VNC. NX is "just" a compressing proxy for X protocol, that means it only uses the X primitives and compresses them.

You would never get such a performance (70:1 compression and almost no round-trips) with VNC...


By MacBerry at Mon, 2004/06/28 - 5:00am

NX itself is based on X11. NX adds

-- extremely efficient compression (better than generic ZLIB, with less CPÜ cycles burned) to X-based traffic;

-- a very intelligent caching mechanism (click for first time on the "K"- or any other menu and watch the delay -- then click on the same menu a second time and notice the difference);

-- elimination of the dreaded round-trips (composed of "X-request" and "X-reply" pairs) which make X over lo-bandwidth/hi-latency links so slow, even if you switch on the "-C" (for compression) in your "ssh -X" (X-forwarding) connection).

That, of course, makes NX the prime choice to tunnel X connections through. In the highest compression level (select "Modem") the avarage efficiency increase for an office productivity session (running KDE as a desktop, Konqueror as the file manager, KMail as your mail client, OpenOffice as your word processor and Mozilla as your browser) you can get as much as 60:1 effective compression on avarage (and if you stick to "pure KDE" (use KWord for word processing, and Konqui for web browsing too), it may even be more...

But NX (and based on this, kNX Cclient and FreeNX Server) can do even more: it can also convert RDP (Remote Desktop Protocol, used by Windows Terminal Servers) and RFB (used by VNC servers) to NX and thereby increase efficiency of these two protocols by 2- to 10-fold across slow links (even if you compare it to TightVNC!).

So to call NX a "wrapper around VNC" would be entirely wrong even if you use it to access a TightVNC server: a mere wrapper would never give you a 2- to 10-fold speed boost....


By Kurt Pfeifle at Mon, 2004/06/28 - 5:00am

Ok, that makes sense. I was just going on the fact that you had a choice between Windows, Unix and VNC.

I'm using it to connect to my computer at home. It uses a upload-capped cable modem (so its set to ISDN), so its squeaking by. Response to some input seems delayed. I would call it usable, which couldn't be said for VNC.

I notice that cacheing your talking about when browsing a web page. Its faster to scroll up and down in areas of a page I've already looked at.


By Ian Monroe at Tue, 2004/06/29 - 5:00am

> It uses a upload-capped cable modem (so its set to ISDN), so its squeaking by.

I take you're saying your monthly quota is 100% used and the service is making difficult to upload things.

I say this because, even if your "up" connection is limited to, say, 33Kbps, you would still have an usable experience with NX (I've use ICA in this situation and NX is said to equal or better than it).

Could someone in-the-know throw some 2¢ here?


By Café, pô! at Tue, 2004/06/29 - 5:00am

No its capped at about 15-20 kpbs (the supposed minimum upload is 32 kbps second, but it seems to be more like thats the max), there isn't a quota. ISPs with quotas are un-American. Like I said, its usable but sometimes unresponsive. With VNC its easy to gauge if its being responsive enough since the mouse cursor is drawn remotely, but the cursor with NX is always responsive.

I know your overall internet connection can be hosed by using all your upload bandwidth. It could be a situation where limiting the amount of bandwidth available to NX would make things more reliable.


By Ian Monroe at Wed, 2004/06/30 - 5:00am

Cable is a shared bandwidth medium. Because everybody on the same cable segment shares that bandwidth, the more they can restrict a users use of bandwidth, the more customers they can put on the same segment.

Further, they don't like other people's content competing with theirs so they do slimy things like severely restrict upload speeds to that Bit Torrent and other peer-to-peer networks don't function well.

DSL by contrast doesn't have the maximum transmission speed that cable does, but your circuit is your circuit, and the upload speeds tend to be less restrictive although most DSL is still asymmetrical favoring download speed over upload, but in general upload speeds are much better and DSL companies generally won't cancel you for using too much bandwidth which has become a favorite hobby of some cable companies.

And no I didn't come here to advertise; I was looking for a way to do audio with vnc; this just happens to be a sensitive point because I loose a lot of customers to cable when people are fooled into thinking they're getting a huge amount of bandwidth on the cheap; and of coarse they are as long as they don't actually try to use it.
If you're a Linux user, you're probably downloading RPM's to keep your system up to date and expand functionality regularly. Cable might not be the best option. Ok, I admit it, I'm biased as I do sell DSL services. But really, we don't do that crap and I don't find it ethical, but when you understand the economics and how cable access works you can understand why they do.


By Robert Dinse at Fri, 2008/12/12 - 6:00am

It has much better compression (average 70:1).


By Anonymous at Mon, 2004/06/28 - 5:00am

What about adding an "a" so it's kNaX? :)
The binary would of course be all-lowercase: knax


By cm at Tue, 2004/06/29 - 5:00am

Just say "kinks"... ;-P


By Café, pô! at Tue, 2004/06/29 - 5:00am

What's wrong with just saying K-N-X? Or even k'nex?


By Paul Eggleton at Tue, 2004/06/29 - 5:00am

hi,
i want to know if can install FreeNX Server and kNX Client. and if it is possible how i can find the howto
thank you


By tahtah at Mon, 2004/07/19 - 5:00am