NX technology is a computer program that handles remote X Window System connections, and attempts to greatly improve on the performance of the native X display protocol to the point that it can be usable over a slow link such as a dial-up modem. It wraps remote connections in SSH sessions for encryption.
It is developed by Gian Filippo Pinzari at the Italian software company NoMachine. The NX scheme was derived from that of DXPC - the Differential X Protocol Compressor project.[1]
NX software is currently available for Windows, Mac OS X, Linux, and Solaris. NoMachine has clients available for Windows and Mac OS X, and Google makes a freely available Open Source GPL2 version of the server called NeatX[2].[2]
Contents
1 Technical details
- 2 Other display protocols
- 3 Use of SSH protocol
- 4 License
- 5 Clients
- 6 Previous X11 compression schemes
- 7 See also
- 8 References
- 9 External links
Neatx is an Open Source NX server, similar to the commercial NX server from NoMachine. If you're not familiar with NX, these links might help:
- NoMachine's “Getting Started With NX”
- NoMachine's “Introduction to NX technology”
- Wikipedia article on NX technology
Neatx was developed by Google for an internal project. That project is now finished, and the source was released for the community to use/develop/benefit from. A couple of Google employees are doing sporadic releases and maintenance in their spare time.
==================
Next Generation Remote Display NX is an exciting new technology for remote display. It provides near local speed application responsiveness over high latency, low bandwidth links. The core libraries for NX are provided by NoMachine under the GPL. FreeNX is a GPL implementation of the NX Server and NX Client Components.
FreeNX 0.7.3 "Priscilla One Year Edition" Released - Sunday, 18/08/08 -
[Download]
Here is a good place to get started with FreeNX:
http://ubuntuforums.org/showthread.p...ghlight=freenx
You may also want to look at NoMachine's website www.nomachine.com for the web companion to help with connections using a web site. It requires more setup, but it's worth it.
Finally, unless you use FTP (you should use SFTP anyways) you can use port 21 on your firewall and redirect it to port 22 to the machine you want inside. On the other hand, if your router doesn't support that feature (sadly some are removing it) you can change the SSH port on your Ubuntu machine to 21 as most employers do not block this port. As a last resort you may have to forfeit the web interface and use port 80 for SSH.
On the side of hamachi, I have successfully been able to get it to work, but you need to make hard links for the ssl libraries, because the libraries it looks for are older than the ones supplied with Gutsy. I have made the hard links and they work just fine. So it is definitely possible to send your request through hamachi if you want to. However, for speed sake I would recommend using the port 21 approach if you can, since no one should use FTP anymore IMHO.
Here is a good place to get started with FreeNX:
http://ubuntuforums.org/showthread.p...ghlight=freenx
You may also want to look at NoMachine's website www.nomachine.com for the web companion to help with connections using a web site. It requires more setup, but it's worth it.
Finally, unless you use FTP (you should use SFTP anyways) you can use port 21 on your firewall and redirect it to port 22 to the machine you want inside. On the other hand, if your router doesn't support that feature (sadly some are removing it) you can change the SSH port on your Ubuntu machine to 21 as most employers do not block this port. As a last resort you may have to forfeit the web interface and use port 80 for SSH.
On the side of hamachi, I have successfully been able to get it to work, but you need to make hard links for the ssl libraries, because the libraries it looks for are older than the ones supplied with Gutsy. I have made the hard links and they work just fine. So it is definitely possible to send your request through hamachi if you want to. However, for speed sake I would recommend using the port 21 approach if you can, since no one should use FTP anymore IMHO.
No comments:
Post a Comment