Forum Replies Created
-
Posts
-
The problems with the keys improved quite a lot by updating to the latest version of NX on both PCs.
When you say that there are improvements, do you mean that problems with keys being repeated or not received has gone away completely, or are there still issues?
If I left the connection idle, the screen went black after a couple of seconds. I disabled the power saving screen blanking (its timeout was set to 10 minutes. With that change, the blanking issue has gone away.
We’ll look into this.
Can you send the logs to issues[at]nomachine.com please? Make sure you provide the info I requested in my earlier post.
Thanks.
For a detailed explanation on these directories, please see the following article: https://www.nomachine.com/AR12K00765
In brief, the C-hostname-display-sessionID directories are for managing the connection to the physical desktop or virtual desktop. You will probably have also seen S-hostname-display-sessionID directories; these are related to the client monitor run for each connection.
When you terminate a session, NoMachine’s default behaviour is to delete all old directories from your .nx on the server side unless NoMachine is configured to preserve them, e.g. for debug purposes. When you disconnect your virtual desktop, a C-* and the S-* directory is left in your .nx to be ready for the reconnection.
A correctly terminated session is renamed to T-C-*. When you find a F-C* or a F-S* directory in your .nx , it means that something went wrong and the session or the client monitor has been terminated unexpectedly or incorrectly. You can safely remove all T-C*-*, F-C-* and F-S-* directories.
Be careful not to delete a C-* or a S-* directory as it will cause the sudden termination of the current connection.
To ensure that NoMachine deletes all old directories, edit the node configuration file, namely node.cfg, uncomment and set the SessionLogClean key to:
SessionLogClean 1
Did you update the client side software to version 4 as suggested? If so, we will need to see logs from both sides, plus the information that is listed in ‘What to include’ just below. Note that we’ve since release 4.0.369 and you can use the automatic updates to get the latest fixes.
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’.
If the logs are too big, send them to issues[at]nomachine.com referencing your topic.
Thanks.
Hi,
We are not away of any bugs. Are you able to provide some more information?
– Do you have a multi-monitor setup on the Mac server?
– What is the version of your Mac server?
– Is the “Keep original aspect” button selected in the Display settings panel?
What behaviour do you observe when switching it?– What part of the remote screen are you able to see? The one with the upper left corner?
– Are you able to navigate the viewport by moving the cursor near the border of the player
window? Can you see in this way parts of the remote screen that were previously hidden?– Is the problem fixed if you change the resolution of your Mac screen by means of the
“System Preferences -> Displays” pane and restore it back to the previous value? (see screenshot)Attachments:
See this post Sanki
https://www.nomachine.com/forums/forums/topic/thin-client-with-4-or-more-monitors
I think what you need is the functionality documented in the Feature Request here: https://www.nomachine.com/FR11K02797
The steps to generate the cookie are:
1) $ COOKIE=
ps -ef | md5sum | cut -f 1 -d " "2) $ sudo xauth -f /var/run/Xvfb-0.auth add :0 MIT-MAGIC-COOKIE-1 $COOKIE
3) $ xauth add :0 MIT-MAGIC-COOKIE-1 $COOKIE
We’ll update the article 😉
Check that you have set up your forwarding to port 4000. If you are connecting via NX, NXD listens on the default port 4000.
Bug confirmed. A Trouble Report is open (https://www.nomachine.com/TR12K04131). We’ve added a notification facility to all TRs now, so you can receive an email when the fix has been released.
I tried to verify the difference using the MacOS and Linux clients (4.6.8) connecting to CentOS 6.5 and the default NX server from the distribution
This indicates that you could be connecting to an older NX server, possibly 3.5.0. You are therefore connecting using a connection file created with (let’s say) NX Client 3.5.0, in which the type of the desktop (e.g. KDE, Gnome etc) is always saved in the connection settings. Selecting the desktop type was a pre-requisite in 3.5.0 before logging in, in version 4 you select after authentication.
when I reconnected and did “Reset login information and preferences”, suddenly the session list appeared. This worked with both clients to the same host.
This means that the check box is doing its job properly 🙂 You can see the remote sessions list because when resetting the connection configuration, the session type you have already set in your “old connecting file” gets removed. The client can’t automatically start an “unknown” session and hence you get the option to run a new virtual desktop session. Maybe you had selected to create a new desktop and stored this setting in the connection file. Resetting this setting now, you get the options to reconnect to an existing desktop (the session list). Knowing that, if you find any inconsistency please let us know.
If you prefer this behaviour, you can uncheck the box “Save this setting in the configuration file” when selecting the type of virtual session to start. This way you will see the session list and the option to start a new session.
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
