Forum Replies Created
If you haven’t enough bandwidth, or the latency across the two points is too high, it’s impossible to use comfortably a remote display software like NoMachine. So the first thing is to determine how much bandwidth and latency you have. Even the VPN software may not work at its best, for whatever reason, but making some simple tests, like opening a TTY connection, outside NoMachine, to check the interactivity and latency through the VPN, and trying to download a big file to see the available bandwidth, should give you a clear idea of where the problem is.November 21, 2013 at 14:17 in reply to: Custom session + floating window doesn't seem to work #852
The error is because the server side closed the connection without following the normal shutdown procedure. You should check why on the server.
Sorry but you don’t know what you are talking about. If you consider running a remote access software giving you access to the local screen a problem, don’t run it. Problem solved. As far as I understand nobody sold you NoMachine as a terminal server for Mac.
The fact OSX is Unix doesn’t mean it’s Linux. There are things that are trivial to do on Linux that are not as easy on OSX, especially when you are dealing with an OS where what you can do and what you cannot do is written in the EULA.November 17, 2013 at 08:45 in reply to: Fresh install on Debian "failed to map ssh port" error in GUI and 204 auth error #775
Occurs with the most recent NoMachine client for Windows 3.5.0_9
The most recent NoMachine client for Windows is probably a 4, not a 3.5, given that you say you have installed a 4.0.366 on Linux.
SSH connections are not supported in the free 4. This is stated in a multiple places in the docs, for example here: