Forum Replies Created
-
Posts
-
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/TR03V11102We’ve reproduced the issue and have opened a Trouble Report which you can track using the following link:
Chromebook trackpad scroll gesture doesn’t work in NoMachine session
https://kb.nomachine.com/TR03V11106Thanks for clarifying, so everything is working correctly.
In version 9 we will be including our own built-in 2FA option in the GUI. This might be of interest to you. To use it, users will require a NoMachine account and the NoMachine app installed in order to receive push notifications, and being logged in to new NoMachine Network service within the app. NoMachine 2FA can be used to protect your NoMachine/Network account logins as well as for approving incoming connections. As I said, it will be released in version and will be available in all products.
In NoMachine, MFA relies on the MFA already configured in the system and it cannot be configured directly in the NoMachine GUI.
You submitted this topic in Terminal Server products, so that means you are using Linux (if you have a subscription please consider submitting a support enquiry in your customer area). I’m not sure whether you already followed the instructions in the article about 2FA here: https://kb.nomachine.com/AR12L00828 (see section 3.2. Example 2: use Google Authenticator and also Example 4). There’s something not clear in what you wrote. The correct steps for the end user should be:
1) start the nomachine connection
2) input your username and password
3) input the Authentication code (from the google authenticator on the mobile app)Is this what your users are seeing?