This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
doc:faq:start [2015/08/21 00:00] mikedep333 Move Client FAQ after Server FAQ |
doc:faq:start [2015/08/23 13:13] ionic Switch to AE... |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== FAQ ====== | ====== FAQ ====== | ||
- | For those who want to find reasons for certain | + | For those who want to find reasons for certain |
- | ===== Server | + | ===== NX Protocol |
+ | ==== Is X2Go compatible with NoMachine' | ||
- | ==== Is X2Go compatible with nomachines | + | No. It is not possible to use NX client to log on to an X2Go server and vice versa. |
- | No even though | + | X2Go does use the same libraries |
+ | |||
+ | X2Go also performs SSH authentication in a different manner than NoMachine does. | ||
==== Can I install FreeNX and X2Go Server on one system? ==== | ==== Can I install FreeNX and X2Go Server on one system? ==== | ||
- | Yes - the NX libraries of X2Go are actually the most recent versions of NXv3 libs available | + | Yes - the NX libraries of X2Go are actually the most recent |
- | + | ||
- | Due to these circumstances in the future the X2Go project will be upstream source for NXv3 libs for quite some distributions like Debian or Ubuntu. | + | |
In former times the NX libs shipped with X2Go installed into an X2Go' | In former times the NX libs shipped with X2Go installed into an X2Go' | ||
Line 19: | Line 20: | ||
Nowadays the NX libs shipped with X2Go work as a replacement for the NXv3 that are not maintained by NoMachine anymore. | Nowadays the NX libs shipped with X2Go work as a replacement for the NXv3 that are not maintained by NoMachine anymore. | ||
- | (This FAQ article has been written by Mike Gabriel, if someone does not agree with the given information on NoMachine, please be so kind to contact | + | (This FAQ article has been written by Mike Gabriel |
+ | |||
+ | ==== Why are you using the terms " | ||
+ | |||
+ | Basically: | ||
+ | |||
+ | - That is the term that was always used. | ||
+ | - Libraries are created also from the source package. | ||
+ | - Those libraries define the NX protocol. | ||
+ | |||
+ | Note that originally, " | ||
+ | |||
+ | - nxcomp | ||
+ | - nxcompext | ||
+ | - nxcompshad | ||
+ | - nxproxy | ||
+ | - nxagent | ||
+ | - nxauth | ||
+ | - nx-X11 | ||
+ | |||
+ | Only the 1st 3 are libraries. | ||
+ | |||
+ | Having separate tarballs made maintenance more difficult, so they were combined into one as the X2Go project started redistributing them. | ||
+ | |||
+ | ==== Why not just use X11 forwarding over SSH? This is what Keith Package recommended. ==== | ||
+ | |||
+ | You are probably referring to the [[http:// | ||
+ | |||
+ | It is true that X11 forwarding' | ||
+ | |||
+ | However, nx-libs performs 3 additional performance improvements: | ||
+ | |||
+ | - nx-libs caches images, so that they do not have to be resent. For example, opening up your "start menu" is very fast the 2nd and 3rd time that you do so. | ||
+ | - zlib is generic lossless compression, | ||
+ | - XCB applications are still partially hindered by round-trips, | ||
+ | |||
+ | The 1st 2 performance improvements also reduce bandwidth usage; which has the effect of improving performance when other users are sharing the same WAN link. | ||
+ | |||
+ | ==== Why Am I told to enable X11 forwarding with X2Go? I thought that X2Go uses nx-libs instead of X11 forwarding! ==== | ||
+ | |||
+ | The simple answer is that the OpenSSH server treats the connection differently (in such a way that degrades nx-libs performance) unless X11 forwarding is enabled. | ||
+ | |||
+ | [[https:// | ||
==== What is the difference to LTSP? Why a free thin client environment? | ==== What is the difference to LTSP? Why a free thin client environment? | ||
Line 25: | Line 68: | ||
LTSP requires a high bandwidth on your network. It can efficiently be used in Local Area Networks (LANs) only. | LTSP requires a high bandwidth on your network. It can efficiently be used in Local Area Networks (LANs) only. | ||
- | However, X2Go is not a mere solution for local area networks, but it also allows for the integration of a mobile network into the system. Nomachine’s NX libraries - used by X2Go - enable the transport of whole desktop sessions over a narrow | + | However, X2Go is not a mere solution for local area networks, but it also allows for the integration of a mobile network into the system. Nomachine’s NX libraries - used by X2Go - enable the transport of whole desktop sessions over a narrow |
Further bonuses of X2Go are that you can pause a desktop session and take it to a different thin client for further use. | Further bonuses of X2Go are that you can pause a desktop session and take it to a different thin client for further use. | ||
+ | |||
+ | ===== Server FAQ ===== | ||
==== What are the packages x2goserver-home and x2goserver-one for? ==== | ==== What are the packages x2goserver-home and x2goserver-one for? ==== | ||
Line 47: | Line 92: | ||
Yes, there are two: [[doc: | Yes, there are two: [[doc: | ||
- | ==== Is there a MacOS Client? ==== | + | ==== Is there an OS X Client? ==== |
[[doc: | [[doc: | ||
Line 79: | Line 124: | ||
This happens because of a package called '' | This happens because of a package called '' | ||
- | In general, this is not a bug. Using two applications that handle display | + | In general, this is not a bug. Using two applications that handle display resolution is not supported, as it can lead to many unexpected |
- | resolution is not supported, as it can lead to many unexpectable | + | |
- | race conditions. | + | |
- | On machines that act as X2Go Server only, it may make sense removing the kscreen package completely. This, however, may have an effect on your X2Go server' | + | On machines that act as X2Go Server only, it may make sense removing the kscreen package completely. This, however, may have an effect on your X2Go server' |
For X2Go we suggest disabling the KScreen KDED module (System Settings -> | For X2Go we suggest disabling the KScreen KDED module (System Settings -> | ||
Line 122: | Line 165: | ||
At this time libssh, the ssh library used by X2Go is unable to work with an ECDSA key. | At this time libssh, the ssh library used by X2Go is unable to work with an ECDSA key. | ||
- | However you may use an RSA key--if you need to--or go with the SSH default authenticating method using the remote user's password. | + | However you may use an RSA key - if you need to - or go with the SSH default authenticating method using the remote user's password. |
==== SSH Login issue ==== | ==== SSH Login issue ==== | ||
- | If you already use openssh | + | If you already use OpenSSH |
< | < | ||
The host key for | The host key for | ||
Line 133: | Line 176: | ||
</ | </ | ||
- | This is related to the ECDSA Key (see FAQ above). | + | This is related to the ECDSA host key (see FAQ above - although there is a subtle difference between host and client keys.) |
- | To solve this issue, you can disable ECDSA keys on your ssh server configuration, | + | To solve this issue, you can disable ECDSA keys on your OpenSSH |
< | < | ||
#HostKey / | #HostKey / | ||
Line 156: | Line 199: | ||
</ | </ | ||
- | ==== Libreoffice | + | ==== LibreOffice |
- | If when using Libreoffice, text selections and copy/paste operations | + | If when using LibreOffice, text selections and copy/paste operations |
- | ==== Mate and numlock erratic | + | ==== Mate and numlock erratic |
- | If using Mate DE, your numlock key makes numeric keyboard act in a numeric manner or as a moviment | + | If using Mate DE, your numlock key makes numeric keyboard act in a numeric manner or as a movement |
< | < | ||
gsettings set org.mate.peripherals-keyboard remember-numlock-state false | gsettings set org.mate.peripherals-keyboard remember-numlock-state false |