Forum Replies Created
-
Posts
-
We’ve opened a Trouble Report with a workaround: https://www.nomachine.com/TR02L04249
It would be useful to understand how you feel the new version is inferior to the older version, so that we can improve it.
The biggest change in version 4 is that you can do all the configuration you did in the old client during the session, while in version 3 you had to take a number of decisions before connecting to the remote server and, once connected, you could do very little. The initial GUI, by which you must choose the computer to connect to, is designed to be “dynamic”.
As for the select text issue, it would help to know what Windows version on the client you have installed, what Linux distribution and version you are using on the server side, what DE it is. What NoMachine products and version have you installed on client and server sides? (see list below “What to include”). We assume that you have Workstation installed on the server side.
We are aware of a problem with selecting text for which a TR is open https://www.nomachine.com/TR11K04089.
You can change the size of the remote desktop at any time by using the OS system tools directly from within the NX session, and then via the menu you can select whether to view 1:1 or not.
For example, if you are running a virtual or a remote desktop on Ubuntu 11.04, you can change the size of the remote screen by running the ‘Monitor Preferences’ tool from the System -> Preferences -> Monitors menu. It is then up to the Player to adapt the way it displays the content of the session inside its window.
Hi Ethanee, a Trouble Report is open: https://www.nomachine.com/TR02L04246
See this article here https://www.nomachine.com/AR10K00710.
That would be very helpful. Can you send us details? Contact us at isses[at]nomachine.com so that any sensitive data is not published on the forums.
Could it be that you had a different server product installed prior to installing NoMachine Terminal Server?
There is an issue with reporting sessions from remote node where NoMachine server did not find working ‘X server’. That’s why the virtual
session was indeed created on the remote host, but it was not reported on ‘session list’. Thus the session will not be available for reconnection. Version 4.1 will have the fix.why “out of the box server node” comes with port 22 (proto SSH?), but when I run “nxserver –nodeadd <ip>” its added with port 4000 (proto NX?)?
TR has been opened.
Hi, we will need:
1. Compressed var/log directory from server’s side (on Windows standard path should be C:\ProgramData\NoMachine\var\log
2. Confirmation of whether you have a password set (if it’s not a password-less account)
3. Did you reboot of the server machine after installing NoMachine.
4. Are there other user accounts on the server machine – can you successfully log in on them via NoMachine?For logs, see the following article: https://www.nomachine.com/AR07K00677
This is a bug. Problems with update are not related to the expired evaluation license. You should simply get a warning message and the server will refuse to work once update completed.
We have reproduced it and there is a workaround available while users wait for the fix to be released.