Forum Replies Created
-
Posts
-
When the NoMachine Client connects to a server 3.5 or to a server 4.0 which defines the Connection policy rules, it starts a new session if it can’t reconnect a session already running. There may be a problem with the detection of the session to reconnect. Precise information about the NoMachine software versions (client and server) will be helpful to debug the issue.
Hello Ian,
To connect to a 3.5.0 server from NoMachine client 4 you need to select the NoMachine login in the connection GUI. Steps are here:
https://www.nomachine.com/AR04J00627
Let us know that this fixes the problem.
Hi, NoMachine uses its own automatic update system, currently in beta. This update system works the same on all platforms (including Windows and Mac) and has no system dependencies.
To update your installation:
– Run the NoMachine GUI from your Programs menu.
– Access the ‘Change server settings’ panel.
– Click on the ‘Software updates’ button (last little icon on right).
– Click ‘Check updates’.
Updates are only manual, at the moment, until the system will be considered ready for production use.
BG
Can you verify that you are indeed using 4.0.368 on the server side? There was a known bug that was supposedly fixed in the 4.0.368. Of course your problem can be unrelated, but we would like to be 100% sure it’s not the same.
What you need is the Workstation for Linux.
Any of the products from the Terminal Server range (e.g. Workstation or Terminal Server, https://www.nomachine.com/enterprise) allow to create virtual desktop sessions. The Workstation and all the Terminal Server versions work as terminal servers, by creating sessions running in the background. These are terminal servers, intended for the enterprise market.
Hi Lawrence, I noticed you are using 4.0.352 on the client side and 4.0.366 on the server side.
Can you update both to 4.0.367 (use the automatic updates ;-)).
It is likely to be related to a bug which we’ve fixed in the latest release, here: https://www.nomachine.com/TR12K04092.
This has been fixed in 4.0.367 (recently released).
Don’t forget to use the automatic updates to get the changes and let us know that everything worked 😉
Error: Connections to virtual desktops are disabled on this server.
It appears to be a problem which was just fixed with the release of 4.0.367. Can you update? Note that a fix for https://www.nomachine.com/TR11K04066 is not yet available. It will probably make the next update.
Ang, again the logs don’t show anything strange. If possible, can we send you a debug version for you to install? Let us know: issues[at]nomachine.com
BG
It sounds like the bug with domain users’ authentication for which a fix should be released very soon.
https://www.nomachine.com/TR11K04021
A quick check to see if it is this bug is to try logging in with a local account (if that’s possible).
We’re investigating and will update with our findings. In the meantime can you tell us if you encountered the problem of input not being accepted anywhere else, e.g. is it only ever in the login screen?
Hi, we’ve often contemplated offering a version for FreeBSD, but it really all comes down to the number of users who would be interested. Interest has been rather sporadic which simply doesn’t justify the costs: not just investment for initial development, but also the subsequent maintenance efforts involved when supporting any platform such as the constant regression tests which are fundamental at every release.
Neil, see this topic here: https://www.nomachine.com/forums/forums/topic/changes-disabled-cant-unlock-with-ad-account which looks similar.
Some further information would be useful. Are you able to tell us the output (from a terminal) of ‘net user
and send it to us at issues[at]nomachine.com? Logs (both sides) would also be interesting to see. Just attach them to your email with the subject of your topic. To extract the logs take a look at the article here: https://www.nomachine.com/AR10K00697
Thanks.