Forum Replies Created
-
Posts
-
Hi norcalwingman.
We’d like to examine logs of your authentication attempts. After it fails, please enter the directory $HOME/.nx and save all directories with prefix ‘M-‘ by using this command:tar -czf logs.tar.gz M-*
Send the archive logs.tar.gz to forum[at]nomachine[dot]com.
Thank you very much for your help.Hey motto, this is just to tell you that we’re still checking the problem. I’ll let you know something as soon as possible.
Hi albe.
Please check this, the workaround explained there should help you:
A crash occurs when executing a call to network API on OS X 10.11 El Capitan
https://www.nomachine.com/TR10M06094Hi Chris.
For now we’ve implemented a shortcut Ctrl+Alt+N, where N is the ID of the monitor to select. We’ll release it in the next software update. As for the trackpad gesture, we’ll evaluate it for a future release.Hi Motto.
The problem you’re reproducing on version 5 may not be the same you had on version 4, we would need some logs to understand what is happening. Could you please retrieve them?
Get server logs as explained in https://www.nomachine.com/DT04M00076#3, and client logs by clicking the button “Save logs/Enregistrer les journaux” in the error dialog. Compress all information and send them to forum[at]nomachine[dot]com. Thank you!Hi.
Yes, using Ctrl+Alt+N to switch windows would be fantastic. When can I get this version? I assume I just need to update NoMachine on my client and can leave the server running the same version as before?
We’ll release it with the next update, if you keep enabled the automatic software updates check NoMachine will alert you when a new version will be available.
So in my case it’s expected that the process never goes away?
There are cases where it is normal that the process runs in background, but what you’re describing is something different. We could not reproduce it so far, so I’d be grateful if you can help us to get some information from that hanging process.
From logs you’ve submitted I’ve noticed that the client goes into a termination state, but there is something preventing it from closing completely.
A way to know what’s happening consists in getting a stack of running threads. You can do it by using a Windows tool called Process Explorer:https://technet.microsoft.com/en-us/sysinternals/bb896653.aspx
Launch it as administrator (no need to install, it’s a standalone binary) then double click the hanging process in the list to open the properties window. Select the Threads tab then double click on each row, and copy the content in an e-mail (or take a screenshot if you prefer).
Wondering what would it happen if I disconnect the monitor from the PC. Would the Mac client force 1680×1050 on a non-existent monitor? Or would the PC just stick to the last used resolution? Mhhh… will give a try.
When you detach the monitor you can select as output your graphic adapter, and both the OS and NoMachine would report more supported resolutions than those limited by the monitor capabilities. A reboot may be required.
Hi!
We’ve recently found a problem on OS X 10.11, in order to verify if the issue is the same, can you please do this:– Open Terminal
– Execute the command tar -czf logs.tar.gz ~/.nx/R-*
– Execute the command tar -czf stacks.tar.gz ~/Library/Logs/DiagnosticReports/nx*
– Execute the command open .In the Finder window you’ll find the files logs.tar.gz and stacks.tar.gz. Could you send them to forum[at]nomachine[dot]com?
Thank you!A more comfortable way to shutdown the server: NoMachine tray icon => Show the server status => Use the ON/OFF button.
Hi Cris.
The behaviour you described seems to be related to a virtual desktop, so you create a new desktop on Linux instead if connecting to the running physical desktop, or maybe it’s an headless server.
In such a case, this Feature Request will do what you’re asking:Making it possible to treat multi-monitors on the client as separate monitors in virtual desktop sessions
https://www.nomachine.com/FR12K02799Can you confirm please?
Hi cacophony.
We recently submitted to our testing team a client version allowing to switch selected monitor by using the shortcut Ctrl+Alt+N, where N is the monitor ID. Will that be fine for you?
As for the secondary question, if you’re running an Enterprise Client and that process never closes, it may be a problem. Could you please compress directories %USERPROFILE%\.nx\R-* and send the archive to forum[at]nomachine[dot]com? We’ll check logs to look for clues about the possible issue. Thank you!
Hey Motto! Thank you for the report.
So far we didn’t reproduce the issue, could you please help us by getting client logs? Connect to the server and when you reproduce the issue, enter the directory %USERPROFILE%\.nx on the client, copy the latest directory with prefix ‘R-‘, compress it and send it to forum[at]nomachine[dot]com. Thanks!
The setting DisplayGeometry sets the resolution used by the X server when it starts, and it is kept unless the client asks a different resolution.
Normally settings configured on server side take over those configured on the client, but in some cases the client has priority. The geometry is very specific for each client configuration, and forcing it on server side may cause serious headaches for users with a different display resolution. This is not your case, but consider a server configuring a resolution 1920 × 1080 and a user connecting with a laptop 1366 x 768. He would be forced to use either the fit to window to scale the session, or the viewport to navigate the session with scrollbars.
This is a session setting, you can configure it when you’re connected to the remote server. Press Ctrl+Alt+0 when you see the remote desktop (this is the default shortcut, unless you’ve changed it in Input preferences) and you’ll see that Display button.