Forum Replies Created
-
Posts
-
If User A connects, and then another user WITH the same account connects, the session will migrate. NoMachine understands that the owner is connecting from another client and thinks it’s the same person.
Is it not possible for you to allocate an an individual system account to the users which need to connect? The default behaviour is that if UserA is connected to the remote computer, and UserB tries to connect, UserA will see a pop-up notifying them of the attempt. Only if UserA ignores the notification, they will be bounced off.
Tom5, can you send us the user/.nx from your Windows Enterprise Client? Then from the Cloud Server host, send us the var/log. Instructions are here: https://www.nomachine.com/AR10K00697.
Then send everything to forum[at]nomachine[dot]com. Make sure you place the title of the topic in the subject. Thanks!
Q1: I was wondering how many connections can be made to the same machine at the same time? My understanding is just ONE for the free client. Please correct me if I’m wrong.
With the free version installed on the remote computer you want to access, one connection will be allowed at a time to that end point. On the connecting client, you can install either the free version or Enterprise Client, it’s up to you, and you can start as many connects as you want, but if you want to have more users connected to the same remote computer, that remote computer will require Enterprise Desktop. More details here:
What’s the difference between the free NoMachine package and Enterprise Desktop Subscription?
https://www.nomachine.com/AR02P00965Q2: If there is already a connection from a guest to host, does this preclude a second guest from logging on, or does the second guest disconnect the first – in essence bouncing the first user off?
The default behaviour is that if UserA is connected to the remote computer, and UserB tries to connect, UserA will see a pop-up notifying them of the attempt. If UserA ignores the notification, they will be bounced off.
There was an issue with manifest causing a permissions error (for server-side installations), which has since been fixed so it is probable that you downloaded the update after we fixed it 🙂 You shouldn’t get the problem again.
To change the ownership back to nx, it’s enough to run the command:
sudo chown -R nx /usr/NX/var/db/limits(related topic: https://forums.nomachine.com/topic/session-negotiation-has-failed)
This is a duplicate of this topic: https://forums.nomachine.com/topic/block-users-from-client-from-transfering-files
Change the system account of the connecting user to one with fewer permissions on the remote host, then they won’t be able to access the server/node cfg nor alter the settings in the server GUI. If the connecting user is an admin user, it’s impossible to prevent them from accessing the server preferences.
Change the system account of the connecting user to one with fewer permissions on the remote host, then they won’t be able to access the server/node cfg nor alter the settings in the server GUI. If the connecting user is an admin user, it’s impossible to prevent them from accessing the server preferences.
Kurt, we’ve found what the problem is and our developers are looking into a possible solution. For some reason no confirmation that session is running is received from the agent, why this is I cannot say, this is what our developers are investigating. So, I am unable to give you an immediate workaround here. It is probable that we will need to send you a patched package, also with debug enabled. I or one of the developers will update the topic soon.
The file didn’t attach, probably because it exceeded the max size allowed. Please send it to forum[at]nomachine[dot]com making sure you insert the title of this topic in the subject and indicate your forum nickname. Thanks!
Please take a look at: https://www.nomachine.com/AR11L00827
The implementation of the upcoming feature NoMachine Network will make this type of intervention on the router and firewall unnecessary. You can read more about this here: https://www.nomachine.com/FR07J02731
Zenith, just to confirm because this topic is quite long (in theory it would be wiser to open a new topic about performance), you are connecting from Windows to Linux, aren’t you? In any case, regardless of the OS you are connecting, when connecting to the physical desktop, the supported resolutions are those of the remote graphics card as listed in the System settings on the server. I.e., the session resolution on the client cannot be higher than the maximum resolution supported by the remote graphics card which in your case is on the Linux host you are connecting to.
More information is here:
Resize and scaling options for NoMachine client version 4 or later
https://www.nomachine.com/AR02M00835About performance. You can check a few things.
1) Check CPU usage, on the client but more importantly on the server
2) What changes when you move the Quality slider during the session?
3) Try switching off the X-server, that way NoMachine will activate its own. This article explains how to do that. https://www.nomachine.com/AR03P00973. If you read there, also look at points 3 and 4).
Can you also look in the session in the C-*/session logs to see what is written there with regards to H.264?
If you get:
Info: Using H.264 software encoder.
the encoding is done by the CPU, otherwise you’ll get “hardware encoder” if it is done by the GPU.
I will answer for points 5 and 6
Point 5)
Also I do not fully understand this article:
That Trouble Report is nothing to do with manual port-forwarding on the router. It’s referring to the GWPort box in the server GUI Services panel which is not being flagged correctly. In this panel the port that NoMachine server has automatically chosen to allow connections to the computer over the Internet is printed. See our Server Guide, specifically section 2, (see the guide here: https://www.nomachine.com/DT10O00155#2.1.)
Point 6)
And I also don’t understand the concept behind this post:
https://forums.nomachine.com/topic/problem-mapping-gateway-port#post-18936
The topic you mention is also not your case. In that particular topic, the user was having issues with changing the port in the Services panel of the server GUI, mentioned in point 5. That user wanted to change the port of a particular computer to his preference. The message returned was “Failed to map the port on the Gateway” in his case.
NoMachine works like this. NoMachine tries to use UPnP to carry out port-forwarding on its own. When NoMachine starts, it automatically selects and maps certain ports to prepare for outside access. If you want, you can change the port (GWPort) to something more memorable to allow connections from the outside (see the same guide mentioned above). This is the port which shows up in the Welcome Panel when opening NoMachine on the server.
On some occasions, NoMachine can’t enable UPnP on its own for whatever reason, and it’s necessary to intervene manually on the router. In this case, you change nothing in the UI of NoMachine and any intervention is only done on your router according to the instructions for port-forwarding of your specific router.
As for point 1) I’d just like to add that when a user doesn’t specify the actual version in numbers, it’s standard practice that we ask just to make sure. The community edition you refer to I imagine is the free version and that you downloaded it from our website.
I reviewed this previous post with a similar problem:
https://forums.nomachine.com/topic/failed-to-map-the-port-on-d-link#post-24387
We test NoMachine in a multitude of set-ups with multiple types of routers as well, but we can’t for obvious reasons test with every router available on the market. This particular user had a problem with an old D-link router which was proving difficult to configure. Replacing it solved the connectivity issues.
Any attachments can be sent to forum[at]nomachine[dot]com. If they are large files, or too many, attaching can sometimes fail. Make sure you include the title of your topic in the subject. Thanks!
You should check how you have configured your system’s settings screen lock. See example attached.
Then, if changing that doesn’t help, you will need to provide more details. On both sides, assuming you have the free version of NoMachine installed on the Windows and Linux hosts, open NoMachine, go to Settings -> Server Preferences -> Updates. What’s the version printed there?
https://www.nomachine.com/DT10O00155#2.6.
We will need to know the desktop environment on the Linux host, plus the actual distribution and version (maybe CentOS?).
Attachments:
Use of the free version is for non-commercial use. If you’re not using the game server for financial profit, it would not be considered commercial use.
