Forum Replies Created
-
Posts
-
Support for authentication with smart card has been set-up by relying on the Public Key Infrastructure (PKI) and using an OpenSC compatible smart card, and using the SSH key method (see more about this here: https://kb.nomachine.com/DT07S00230#4, there is also a nice comparison table in chapter 2 which shows you what is supported).
The alternative is to use password authentication. However, we currently have a TR open related to USB forwarding and the remote desktop which shows the login window.
In the meantime we have tried to reproduce, without success, so it’s possible that the keys you are using are corrupt in some way, that’s why it would be useful for us to receive them, so we can also test them.
I did mention we use GNOME in my first message.
Yes, you are right!
About the firewall, when installing NoMachine, it creates rules for the nomachine service, without these nomachine would be blocked.
Which every software update seems to overwrite back to defaults,
I’m not sure what you mean. When installing an update, your previous configuration should be maintained. If something is being overwritten, it definitely deserves a new topic as you wrote 🙂
Hi,
Let me clarify. Each subscription is for the computer you want to access (the “server”) where the specific package for that OS is already installed, and the subscription is for the specific operating system i.e macOS, Windows or Linux. This means you cannot use a subscription purchased for macOS, let’s say, to activate Enterprise Desktop installed on Windows.
If you have a mix of macOS and Windows computers which your users must remotely access, each of those servers needs its own subscription for that specific OS. So a simple example: there are 5 Macs and 5 Windows server computers which users must connect to. You will need 5 x Enterprise Desktop for macOS and 5 x Enterprise Enterprise Desktop for Windows. Are you looking to purchase Enterprise Desktop Pack? Indeed it’s not possible to mix platforms when purchasing a pack. (But please contact our sales team which will be happy to help).
Instead, on the computers or devices that your users connect from (“clients”), you can install the Enterprise Client package or the mobile app. Clients are free and you can have as many as you like on whichever OS you prefer. Simply install the package for the specific OS.
Hi, take a look at the response I provided for https://forum.nomachine.com/topic/can-connect-but-screen-frozen#post-52625. The set-up is similar to yours. Does that help?
Another way to get round this limitation of the video card is to install an HDMI dongle (refer to the article) to force the system to take full advantage of the GPU as if a real monitor were connected. 🙂
Katpan was right about the version in which we added the option to allow the host identity key to be automatically accepted (see the link above), “Adding a new option in the UI to automatically accept the host identity key”.
There is now an option in the ‘Edit connection’ panel to automatically accept the new host identity key when the “Verify host identification” dialog is issued. If you go in to the Edit panel when configuring the connection, you can see the checkbox ‘Always accept the host verification key provided by the remote host’.
It corresponds to the following setting in the connection file (.nxs):
option key="Automatically accept new hosts identification key" value="true"The key-pair that you generated would be useful for our own tests, but we’ll take a look at the logs in the meantime and come back to you.
Hi, I was just about to reply to you asking you to send the logs, but then you seem to have resolved the issue.
What I was going to mention was to not edit the AvailableSessionTypes key, since it should not be necessary – if you remove physical-deskop from the key, this will prevent you from connecting. So restoring the original cfg cofiguration was a good idea.
You mention GDM, so now we know you are connecting to a Gnome desktop. It would have been useful to know which command is used in the NoMachine node.cfg file. You can run the following to find out:
grep DefaultDesktopCommand /usr/NX/etc/node.cfg.But next time it happens and you can reproduce it, we need to see the logs with debug enabled from the Debian host you are connecting to. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
I’m not sure to understand how exactly !M works
As I mentioned earlier NoMachine Free Edition lets you connect to the physical display, installs out-of-the-box and should not require configuration of node/server cfg files. On Linux when it can’t find an xserver running e.g the video card is turned off, NoMachine creates its own to let you access the desktop all the same. (see more about this here: https://kb.nomachine.com/AR10K00700). About the resolution, take a look at the following article: https://kb.nomachine.com/AR02M00836. I’m not sure what changed suddenly that now means you connect correctly and see the display at the proper resolution, but it’s most likely due to the desktop configuration or system. As I said if it happens again, logs and also screenshots would be useful.
ECS provides internal loadbalancing of the connections between the primary/secondary server of the cluster pair. It does not loadbalance between separate ECS gateways. To do that, you can use any tool that load-balances at the router level e.g HA Proxy.
One other possibility is to change a key which can be used to change the screen grabbing method in the node.cfg file on the Macbook Pro server host. Look for the
DisplayServerExtraOptions ""key, remove the prepending # and change it to this:DisplayServerExtraOptions "-nosckgrab". Restart the NoMachine server. Then try to reproduce the black screen issue.Good to know that resolved it!
I’d like to update my earlier response where I suggested to edit the player.cfg. My apologies for not suggesting it first. In your case, you could actually disable HW decoding on the fly for that session from the connection menu (the libraries are still loaded but are not used). Open the NoMachine menu panel inside the session by Ctrl+Alt+0 or click on the page peel at the top right corner of the window. Then click on Display -> Change settings. In that panel click on the Modify button to open the advanced display settings. Click on ‘Disable client side hardware decoding’ to disable it.
If possible, would you be able to send us the logs from the Player reproducing the error? It would mean reverting your edit to the cfg file.