

Annual subscriptions are available for any of the enterprise-oriented products from the store. The only problem I experienced was with the support of more than one keyboard layout, but sparing few glitches here and there, it's working now.If you are using NoMachine in a commercial environment, you need to purchase a subscription. I haven't checked the printing support or the shared folder option, but they exist. There is also support for seamless application, serving a single application window that looks like it is running locally. You can connect to the server local session, but you can also create different sessions for many users. There are client for different operating systems, so you can connect from Windows machine as well. All you need for sound to work is to install PulseAudio on both the remote and the local machine. X2Go supports PulseAudio sound tunneling. Fedora 20 has adopted x2go as remote desktop solution, replacing NoMachine's NX implementation. At least in Fedora, install is as easy as yum install x2goserver (assuming firewall allows ssh). It's based on NoMachine NX code, meaning communication is compressed and it's using cache, but unlike NoMachine it's foss. So there are some "ingredients" still missing here.Īny pointers or own configurations out there that can help me here are welcome. Now so far, if I enable both settings, I can use XDMCP to connect to the server, but I am getting a black screen with a simple mouse-cursor consisting of a white cross. etc/X11/xdm/Xaccess needs to be modified, too (enter a pattern for hosts that are allowed to get a remote login window). To enable remote login I need to modify /etc/gdm/nf: KDE-Remote seems to be fast, propably same with gnome (using port UDP 177, xdmcp).VNC is slow (using ports TCP 5900 onwards, vnc:0.Just forwarding X11 via SSH is very slow (using port TCP 22, ssh).I would like to have a number of users, either with gnome or with kde (based on their likings) who will connect to the server and start their individual settings on the same machine. I am planning to setup a "terminalserver" for my *nix based administrators.
