The client that connects to the NX server is considered a thin client. In addition, with NoMachine we will also be able to perform other interesting actions on a remote computer. This application is useful for sharing access or files from one computer to another. NoMachine is a remote desktop tool that it will allow us to access a computer from a local network or through the internet. It will offer us connection protocols such as SSH y NX to connect the equipment. This is a remote access tool for Gnu / Linux, Mac and Windows. Previous message: Black Screen with Mouse Cursor After SuccessfulĚuth.įreeNX & NoMachine Player - Connection Issues Nick Couchman Nick.In the next article we are going to take a look at NoMachine Remote Desktop and see how to install it on Ubuntu 18.04.Next message: FreeNX & NoMachine Player - Connection Issues. I'm getting sporadic behavior trying to connect NoMachine Player (the replacement for NX Client in the 4.x NoMachine release) with a FreeNX-based server. First, let me state that getting NX Player working with FreeNX is a must - we need to connect Mac clients to our servers, and, since the only Intel-based version of the NX Client for Mac is NX Player 4.x, going back to the 3.5 client is not an option, at least for Mac-based clients. So, here are the software versions I'm using: So, for those who would suggest using the "known good" versions of NX Client 3.5.x, that's not really feasible in my situation. NX Player 4.0.181 Preview 6 (currently on Linux)Īs far as the client goes, I can successfully connect my NX Player client to the NoMachine Virtual Workstation for Linux 4.x preview software, so I'm fairly certain that network issues can be ruled out here. Also, I can successfully connect to FreeNX running on CentOS5, so it actually seems to be some interaction here between FreeNX and something in OpenSuSE. Hopefully someone can point out what, or at least help me better nail it down. It does not matter what Window Manager I try to use - KDE4, XFCE4, GNOME - all seem to fail equally well.Ĭonnections fail *most* of the time - maybe 1 connection in 10 works perfectly fine, but the rest fail with the exact same error.
0 kommentar(er)
