Britgirl

[Britgirl]

We’ve sent an email to everyone in this thread, a couple of emails bounced so if you have not received anything, please contact us directly for a macOS package which includes the fix. Thanks!

[Britgirl]

Hi, thanks for taking the time to report this. Does the player window show an error or does the session window just close?

Are there any core files generated that you can share with us?

[Britgirl]

Hi, glad to know you find the server activity helpful. That was the exact reason behind adding the ‘server activity’ feature: to allow admins to keep an eye on NoMachine connection numbers, users, average connections etc even what files are being transferred. Showing the history of connections is the next step in improvements we will be adding to the server admin GUI. Watch out for that in one of the upcoming releases.

[Britgirl]

You should submit that screenshot to forum[at]nomachine[dot]com, the link was removed because it was unavailable. You say that you are using the latest version of NoMachine, which is version 8. I assumed you were referring to the server side. Please confirm what NoMachine product and version is installed on the server side. Thanks.

 

 

[Britgirl]

can you connect to the remote Windows laptop with a traditional .nxs connection file?

Can you make this quick test even if the laptop is not showing in the Machines panel?  Start a traditional connection with ‘Add’  and inserting its local IP address.

[Britgirl]

Hi, please take a look at the article in our knowledge base:

Connecting with NX protocol to a NoMachine server on Linux in an Active Directory domain
https://kb.nomachine.com/AR12P01007

Does it help?

 

I noticed others requesting similar question, but the suggestions there did not work for me

I’m not sure which topics you are referring to, perhaps this one https://forums.nomachine.com/topic/nx-linux-sssd-ad-issues-with-nfs4-kerberos-home-dir which is currently being investigated. At a glance yours looks to be different.

[Britgirl]

Thanks for the additional details. Whilst we investigate further, can you connect to the remote Windows laptop with a traditional .nxs connection file? We’ll come back to you if we need more information.

[Britgirl]

Pipewire support was added in 8 correct?

Initial support for Pipewire in physical desktop sessions will be added in the next MR which is going to be soon. I would wait until then and then check whether it solves your issue once you’ve updated.

[Britgirl]

I’m getting the error mentioned in the subject when trying to connect with user mike, after john has disconnected from his session.

By default all desktop sharing connections must be explicitly accepted to proceed. On the remote computer users are connecting to, go to “Server settings -> Security -> User Acceptance -> Don’t require acceptance if the user logged in as a system user”. Make sure that box is checked. The default setting is to not require acceptance if the owner of the desktop logs in from remote, but not for other system users.

Please also see our Guide to the NoMachine Server User Interface. Scroll down to “Server security”:

https://kb.nomachine.com/DT07S00237#2.5

 

[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

[Author]

Posts