Forum Replies Created
-
Posts
-
A recording would be useful. You can even do it using NoMachine’s built-in screen recorder. You can open it from the !M system try icon on the Mac. It stays on top whilst you record. On the server activate the Accessibility Keyboard by pressing the Cmd + Option + F5 keys to open Accessibility Shortcuts. Enable Accessibility Keyboard from the list, and the keyboard will open. This will help us to see what keys are being pressed when you log in. Go to your Windows computer or whichever client-side OS you want to reproduce the problem and log in. Stop the recording on the macOS. Send us the nxr file which you generated.
Hello,
so you are connecting from Windows local side to a macOS?
I suggest you update to NoMachine 8 to start with. What macOS version is on the NoMachine server, the OS you are connecting to? This would be useful to know. It could be a permissions issue in macOS. See the following article for the steps to take: https://kb.nomachine.com/AR11Q01061. If NoMachine has already been added, please remove it and add again.
Hi, the server-side logs were clean. And the logs from the client-side were actually logs from the server component of the Windows machine you are connecting from.
Are you able to try connecting from a different device? Does the same behaviour occur?
To get logs from the client side of the session, see “Fourth Step: Collect Client Side Logs” of the document I posted last time.
The following instructions have to be done to the user’s device.
Inside the NoMachine session, open the menu panel by ctrl+alt+0 or click on the page peel at the top right corner of the window. Open ‘Connection’ and click on ‘Take the logs’ button on the left and choose where to save logs. A copy of the session directory is created to store logs and named as session name plus date. Compress it to create the log archive to be sent to Support Team.
On Windows the .nx folder is hidden. To find it, write the following in the address bar or the file browser:
%USERPROFILE%\.nx
Or you ca navigate through the computer folder till the user’s home and digit .nx in the navigation toolbar to reach it. Its path can be similar to: C:/Users/nomachine/.nx
The bug report can be tracked here: https://kb.nomachine.com/TR02V11091
Absolutely. It is something that we’ve been wanting to do for a long time and is the current development roadmap.
Hi xoepe,
confirm what distro and desktop environment you are using. Does using X.Org solve the problem?
Send us the logs from the affected OS. We can then check against known issues with Wayland. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Did you already try rebooting the Win10 again?
After checking that, send us the logs of the Win 10 host. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
In fact your session stats show that latency is indeed the problem, 1106 ms latency 5s, 840 ms latency 30s with regards to your network. So check your network 😉
Did you follow the tips in the article I referred you to in my previous reply, it’s about headless Linux machines. Is your Ubuntu headless?
Please clarify the problem you are experiencing when connecting to the physical display. In your first message you said that you “get disconnected directly”.
Logs from the server would be useful. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Hi,
the quickest way to reset your NoMachine server settings is to uninstall and reinstall.
Regarding the issue about slowness, one thing you can check is that the monitor is actually turned when connecting. We have seen cases in the past on Linux where the video drivers were limiting the frame rate to 1 fps in the case the monitor was detached or turned off. Session statistics would also be useful. You can get these during the session.
– run the menu panel within the session by Ctrl+Alt+0 or click on the page peel
– click on Connection
– then click on ‘Take the statistics’ and save them on your local device.You can attach them here.
fishnet37222 – the issue is known and we have a Trouble Report open which you can monitor here:
White screen occurs when connecting to a KDE/Plasma Wayland desktop on Kubuntu
https://kb.nomachine.com/TR07U10921lordhong – your issue is slightly different and can be tracked here:
Black screen when connecting to Wayland using two monitors
https://kb.nomachine.com/TR0110731Hi,
please tell us:
– NoMachine version and product on both client and server sides
– OS on client side
– Linux desktop environment on Ubuntu server side
– What message you see when you try to connect to the physical desktop
– Follow the tips here: https://kb.nomachine.com/AR03P00973Can you tell us if the workaround in the TR here helps?
https://www.nomachine.com/TR05S10271
As a temporary workaround in ‘Edit connection’ -> ‘Modify’ next to ‘Use key-based authentication with a key you provide’, do not check option ‘Import the private key to the connection file’ in the UI.
NoMachine does not change permissions on the system. It is likely there were sudo operations on user account, for this reason you found yourself having to reset permissions. Check with the Ubuntu documentation about fine tuning your files and folders in your Ubuntu OS.
We have reproduce the problem and have opened a Trouble Report. Please use the following link to track the issue.
Keyboard grabbing works inconsistently on Sonoma
https://www.nomachine.com/TR03V11102