Forum Replies Created
-
AuthorPosts
-
Britgirl
KeymasterPlease update to version 8. That version contains the fix for this issue.
October 18, 2022 at 15:04 in reply to: Content in NoMachine session from iPadOS 16 is off-centre #40801Britgirl
KeymasteriOS users following this topic please read here: https://forums.nomachine.com/topic/important-notice-for-nomachine-users-about-ios-version-16
Britgirl
KeymasterFurthermore, when I used my version of ‘DefaultDesktopCommand ‘only one of my clients with Mac could not create a NoMachine session. Other Mac users and windows users are able to log in using my version of ‘DefaultDesktopCommand’ and get GPU acceleration. Kindly let me know your comments.
If you are still encountering the problem, please open a separate topic. This topic about virtual desktop on Linux can be considered solved.
Britgirl
KeymasterMaybe you could go back to the developer of the project in question and ask them how to modify their script to use NoMachine instead of the other tool they are using? 😉
Britgirl
KeymasterUser was contacted via email.
Any feedback will be considered as we redesign the implementation of mouse support, taking advantage of the new APIs provided by the most recent iPad versions. We’ll also investigate the specific behaviour you have been encountering with the mouse model you
mention (middle button not working). Either way, in version 8 improvements will be made, so watch out for those.Thanks very much for taking the time to let us know. It’s certainly information that is useful for our developers.
Britgirl
KeymasterWe never received the log file, so what I suggest at this stage is you update to the latest version and if you are still seeing the same issue, submit the logs.
October 18, 2022 at 09:56 in reply to: Connecting to Windows very slow without remote monitor on #40792Britgirl
KeymasterI just realised there is a ‘1’ missing in the key I wrote. I apologize for that.
The key should look like this:
DisplayServerExtraOptions “-displayrequired 1”
Britgirl
KeymasterHi, thanks so much for your feedback 🙂
but in many other contexts, like the context we have, with machines both inside and outside the network.
This is exactly why we implemented it, to make adding nodes to your Cloud Server as seamless as possible.
October 17, 2022 at 12:52 in reply to: Session HW encoding stopped working after NoMachine server upgrade from 7 to 8 #40784Britgirl
Keymasteryou’ve changed the way you pick mouse position in Wayland, directly from udev which conflicts with other virtual input devices, blocking access to the remote desktop’s input, when the same is running an automation task…attempt to get mouse movements/control on the NoMachine client side.
What you describe is a new feature giving keyboard and input events from the local user logged-in to the remote computer priority over input generated by the user connected via NoMachine.
It is mainly intended to add a further security level to desktop sharing, so that the input (mouse and keyboard) of
the remote user connected by NoMachine will be effective only after the local user doesn’t produce any input for a certain period. When the NoMachine user gains control over keyboard and mouse, the local user can stop him/her at any moment by simply moving the mouse or typing something.To disable this behaviour, you can set this in node.cfg:
DisplayServerExtraOptions "-eventdelay 0"
Your Android app is unparalleled when it comes to ease of access and keyboard functionality, and with Wayland support, you’ve been paramount to a whole section of the Linux comunity. We’re not going anywhere, we just want to use the old v7 server.
That’s good to know 🙂 You can try contacting the web team via the website to see if they can share a link to the earlier version. But first we would appreciate knowing if the -eventdelay setting improves things for you with regard to the mouse position issue you mentioned.
Regarding the SW/HW/white screen issues described in the thread, we are still investigating.
Britgirl
KeymasterTo create your connection to the remote computer, click on ‘Add’ which you can see in the image you attached, top left.
Then, if you are connecting on LAN, you need to know its private IP address which is assigned to your specific device. See Fig. 1 in https://www.nomachine.com/getting-started-with-nomachine. If you are connecting over the internet, you will need its external IP address.
There are two ways you can check your computer’s IP address in NoMachine. (i) When you’ve installed NoMachine on the computer you want to connect to, open NoMachine from the programs or applications menu. A Welcome panel will publish the local IP address of the computer on which you have installed the software. Or (ii) click on the !M icon (the NoMachine Monitor) which is visible in the computer’s system tray. Click on ‘Show the Server Status’.
I then need to set the password for this connection,
To be able to connect to a Mac or PC from remote you need to have a system user account for that computer (username and password). The password along with the username is what lets you authenticate to the desktop and connect to it. For attended desktop scenarios it’s possible to allow guests to connect, i.e they don’t need a username and password, but they will only be able to connect with your authorization.
The second connection on this image attached looks like a connection to a local PC, but I don’t see how to set that up
The second connection, which has a “little pipe” indicates all computers with NoMachine (server) installed (more about this here https://www.nomachine.com/finding-other-nomachine-computers-on-the-same-network). So if you want to see other NoMachine-enabled computers on your LAN, you must install NoMachine (Free Edition, for example, or any other NoMachine server) and make sure that 1) “Advertise this computer on the local network” is enabled on those machines. To do that, check the link just above. By default broadcasting is enabled. And 2) that your Player (the computer you are connecting from) is configured to show other computers on the LAN. To do that, open NoMachine Playersettings -> Security -> Check that you have not ticked the box “Don’t show other computers on the local network”. The default setting is to let you see other computers on the network.
Britgirl
KeymasterHi, we found that there is an incompatibility in the way the WebPlayer uses WebRTC, with the latest WebRTC released by Google.
They made a few changes to the WebRTC protocol and specifically changes to message IDs, that made our version incompatible.
We’ve fixed it and this is going to be released in the next maintenance, due in the next few days.
You can track the Trouble Report at this link: https://kb.nomachine.com/TR07T10566.October 14, 2022 at 18:18 in reply to: Input issues between Win10 Client and Linux Mint server #42202Britgirl
KeymasterCheck your inbox from us 🙂 We’ve sent you a test package
October 14, 2022 at 11:51 in reply to: Edit appearance of NoMachine Player to show thumbnails as connection icons #40754Britgirl
KeymasterHi! We already tried it and it was ugly. But, we are working on something even better than this. And it will allow you to monitor a given machine, even monitoring the screen as you said 🙂
October 14, 2022 at 07:23 in reply to: Session HW encoding stopped working after NoMachine server upgrade from 7 to 8 #40752Britgirl
KeymasterCan you submit a screenshot where the client shows SW encoding in the session?
Can you send us the logs of the server? Please see the following document for instructions and submit them here or send to forum[at]nomachine[dot]com, making sure to use the topic’s title as the subject of your email. Thanks!
https://kb.nomachine.com/DT07S00243
October 13, 2022 at 17:04 in reply to: Session HW encoding stopped working after NoMachine server upgrade from 7 to 8 #40745Britgirl
KeymasterWe are not aware of a similar issue. Is this on Ubuntu or something else?
Can you submit a screenshot where the client shows SW encoding?
Can you send us the logs of the server? Please see the following document for instructions and submit them here or send to forum[at]nomachine[dot]com, making sure to use the topic’s title as the subject of your email. Thanks!
-
AuthorPosts