Britgirl

[Britgirl]

Hi, we are able to reproduce the scrolling and trackpad issues that users have reported. Please follow this link to track the fix which will be made available in the next MR:

Mouse scrolling doesn’t work on macOS 13 Ventura
https://kb.nomachine.com/TR10T10655

[Britgirl]

Where did you send them to? We have not received any logs. Can you send us a link to download them maybe?

 

[Britgirl]

I’m not sure what you mean with “safety of using RDP”. Windows’ native RDP can run with virtual display drivers, so it can create virtual displays mirroring the client displays and switch the user’s remote desktop session onto those virtual displays.

Anyway, that NoMachine does not provide a virtual Windows display is not because of technical limitations within NoMachine. It’s a question of licensing terms. You may have noticed that all our server products for Mac and Windows connect users to a remote local display which is a physical one. NoMachine captures what the graphics card on the remote device displays. I.e it functions as any other remote desktop software. The exception is Linux. Our free product on Linux, for example, can connect you to both the physical display or can create a virtual display (in the case of headless machines).

Btw, this question has been dealt with multiple times in our forums. For example, here:

https://forums.nomachine.com/topic/enterprise-desktop-with-dual-monitor#post-35185

[Britgirl]

First, you should limit the number of connections to 1. You do this using the ConnectionsLimit key in server.cfg file of the computer you are connecting to. Set this to 1. Then you should set the following key AutomaticDisconnection 1. See the section “Limit the number of concurrent connections” in the Enterprise Desktop guide: https://kb.nomachine.com/DT07S00246

Limits above can be used in conjunction with the AutomaticDisconnection key which controls the server behaviour when the maximum number of allowed connections is reached:

AutomaticDisconnection 0 – The server prompts the connected user to accept or refuse to disconnect for making room for the incoming user. If no choice is made, the user is automatically disconnected. This is the default.

AutomaticDisconnection 1 – The server automatically disconnects the connected user to make room for the connecting user. No message is issued to the already connected user.

AutomaticDisconnection 2 – The server prompts the connected user to accept or refuse to disconnect for making room for the incoming user. If no choice is made, the server doesn’t disconnect the user and advises the incoming user that the maximum number of allowed connections is reached.

AutomaticDisconnection 3 The server never notifies desktop owners about incoming users, incoming users are informed that the maximum number of allowed connections has been reached.

Does this help?

[Britgirl]

Please send to forum[at]nomachine[dot]com making sure to use the topic’s title as the subject of your email. Thanks!

[Britgirl]

users to connect concurrently to the same physical desktop, but next every one switching to “his” how remote monitor.

It’s possible for the 3 connected users to each see a different monitor, but the input events will still be shared. That is, they would be sharing the input devices and they would be “fighting” for the control of the pointer and keyboard.

NoMachine does not virtualize Windows nor Mac, so what you need is a virtualization solution. See this topic: https://forums.nomachine.com/topic/multiple-sessions-issue#post-4285

[Britgirl]

Hi, thanks for the information, we are investigating and will come back to you.

[Britgirl]

We’re not able to reproduce this. Did you perhaps change something in your settings. Are you able to share your server.cfg with us? You can send it to forum[at]nomachine[dot]com.

[Britgirl]

Hi, this pop up is to show the desktop owner that someone is connected to their desktop. It can be closed by clicking on the ‘x’ or by going into the NoMachine systray icon and disabling it from there. Please see for more details: https://kb.nomachine.com/DT07S00239#5.1. It’s especially useful for when another user is connecting to your desktop in Guest Desktop Sharing mode (https://www.nomachine.com/getting-started-with-guest-desktop-sharing).

That you can’t close is odd, so we need further details.
Are you connecting to a NoMachine Free Edition or one of the Terminal Server products?
Can you tell us the version of Ubuntu and what desktop environment it is?

[Britgirl]

Hi, the setting is exactly the same, however, when applied to the connection it has effect only on that connection, on these ‘Connection settings’. Applied to the node it will have effect on all connections to that node.

[Britgirl]

Hi,

my laptop set to do nothing when the lid is closed if on power but if I close the lid

We cannot reproduce this. In our own tests the Windows laptop is set to “Do nothing” in the “When I close lid” configuration of both battery and plugged in options, the laptop is visible in the Player’s Machines panel and it’s possible to connect to the laptop. Can you show us a screenshot of your Windows settings?

What Windows version is it?

open the lid and restart the server

Do you mean that when you open the lid the OS restarts? Or when you open the lid you have to restart the NoMachine server (but the OS is still running)? Have you checked that the IP of that Windows computer can be pinged even with the lid closed?

[Britgirl]

I’m just using touch screen and keyboard on my Android device for mouse and keyboard input to the remote PC.

Thanks for the clarification.

We aren’t aware of issues with inputting from Android clients. Are you able to connect from another computer in place of your Android device and encounter the same problem?  This would indicate it’s not an issue on the Android side.

You can use Xev to debug keyboard and mouse events on Linux. See this article for how to get the output.
https://kb.nomachine.com/AR12N00911. This will show if events are being received.

Logs would be useful in any case. For server side logs: https://kb.nomachine.com/DT11R00182#1 (or enable log level in Server status -> Server logs 7- Verbose), then from a prompt run sudo /etc/NX/server --debug --collect. Send everything to forum[at]nomachine[dot]com making sure to use the title of the topic as the subject of your email. Thank you.

[Britgirl]

What kind of mouse and keyboard are you using with your Android client device? Is it bluetooth?

What about if you use just the screen of your device to input in to the remote desktop window? Do you still get the same behaviour?

Are you able to try a connection from a regular PC NoMachine client in place of your Android device?

What’s the desktop environment on your Manjaro Linux server?

What version of NoMachine is installed there? The latest 8.1.2?

 

[Britgirl]

Hi, we’re putting a special binary together and we’ll be in touch when it’s ready 😉 Thanks for everyone’s patience.

[Britgirl]

Did you recently update to drivers or the system in general?

[Author]

Posts