Forum Replies Created
We are still unable to reproduce the problem.
Logs would indeed be useful, you can send them to forum[at]nomachine[dot]com, referencing the topic as subject.
We need logs of player and server both from rpi machine, plus server.cfg and node.cfg. – to check if some option(s) were changed, which provokes the problem.
Could you please send us more details about the issue, maybe screenshots ?
There was an error during the upload of logs. Can you please send them to forum[at]nomachine[dot]com, referencing the topic as subject ?
Can you also explain us how you want to use that Smart Card Authentication (a step by step description would be nice), as we wonder if the USB will be needed, or not, do achieve what you want to.
Thank you for letting us know, we are glad you’ve found a workaround that works!
Best Wishes 🙂December 8, 2020 at 16:04 in reply to: NoMachine connection fails first attempt, second attempt always successful #30684
I don’t have a date, but the release of version 7 should happen in the very near future.August 7, 2020 at 10:33 in reply to: Correct procedure to install NX on a Domain Controller #28915
Can you please collect the installation logs ( C:\Users\%USERNAME%\AppData\Local\Temp\Setup Log 2020-…-…. logs ) to help us investigating ?
and send them to forum[at]nomachine[dot]com, referencing the topic as subject.
In order to investigate your problem, can you first tell us what OS and version is installed on the target PC and if you reboot or shutdown the PC ?
Windows 10 has a known issue of not shutting down properly (see a workaround proposed on that website https://www.easeus.com/resource/computer-cannot-shutdown-how-to-fix-windows-10-automatically-restarts.html). Does your problem occur as well when you are not connected with NoMachine to the PC, or not ?
On behalf of the whole team, thank you for your kind words!
We are very happy that NoMachine free brings you satisfaction and that it helps you in your everyday life.August 5, 2020 at 08:20 in reply to: Restrictions to session shadowing with NoMachine Linux #28872
Simultaneous connections are unlimited in all the products of the Terminal Server Family, but new virtual desktops/custom sessions are limited to four with the Workstation. I.e. up to four users can have their own personal Linux desktop. There are no limits instead for connections to the remote physical desktops (multiple users can connect to that).
The article “What is the difference between physical desktop connection and virtual desktop connection?” may be helpful (https://www.nomachine.com/AR10K00700)
We hope nothing remains unclear, but let us know if it’s the case.August 4, 2020 at 16:01 in reply to: Restrictions to session shadowing with NoMachine Linux #28855
“As suggested here, I suppose this is a limitation of the free version which limits to 1 user per Server.”
Yes, NoMachine free allows only one user to connect remotely at a time, i.e. it allows 1 connection. Different users can connect, but one by one. Note also that NoMachine free is for personal use (see article “Is NoMachine for remote desktop free?” https://www.nomachine.com/AR03P00972)
The table of its features is available here: https://www.nomachine.com/remote-access-for-everyone
“Is the number of virtual desktops (so 4 for the Workstation version) also the number of users that connect simultaneously to the same NoMachine server ?”
It doesn’t limit the number of users, but the number of new NoMachine virtual desktops that users can create. If a user for example reconnects the virtual desktop or connects to another user’s desktop, the limit counter is not increased.
Yes, it is possible to retrieve the sessions lost in the master node on the secondary node, but NoMachine has to be configured to not run sessions on the Enterprise Terminal Server host, but only on the Terminal Server Node(s).
I.e. only sessions running on the nodes can be recovered, if the server goes down.
You can find in the following guide more details and a step by step example to configure a HA multinode setup: https://www.nomachine.com/DT06O00142&dn=failover#3.4 (check the section 3.4. Setting-up Two Enterprise Terminal Servers in a Failover Cluster)
There is a workaround explained in the trouble report “White screen is displayed when connecting to a remote physical display (VP8 encoding)”: https://www.nomachine.com/TR06R09772
Please try it and let us know if it solves your problem. If not, we will need to investigate further.
We didn’t find anything helpful for the investigation in the logs.
But we would like to try something: can you remove NoMachineUSB drivers, following the procedure explained it this article: https://www.nomachine.com/AR12O00955
And let us know if it helps.
We haven’t received your logs. Did you send them to forum[at]nomachine[dot]com ?
Please make sure to reference the topic as subject, to make it easier to find.