Forum Replies Created
-
Posts
-
Hello,
this is a known issue and a fix has already been scheduled for the next maintenance release 🙂
Should I install the ‘NoMachine Enterprise Client or the Terminal Server Node package’ as well? Because I think I did do that last time.
You seem to be referring to our legacy version where users had to install 3 separate packages. This is no longer necessary with the latest version, well, since version 4 to be honest. It’s been one simple package for users to install since 2013. Additionally, you can’t install multiple packages on the same host, the installation will block. If you’ve had old NX products running on the same host where you’ve installed NoMachine, and here I am referring to NX-derivatives in particular, this could be what is causing all the problems. You should remove all of these if they are present.
For more information about our support services associated with Enterprise Desktop, please check the appropriate web page. Remote access is only offered in specific circumstances: https://www.nomachine.com/support-services
Regarding the original issue in question, now that you have done a complete removal and reinstall on the Linux server and have left it in it’s default factory configuration, I suggest you connect to reproduce the authentication problem, and gather the logs from both the Windows client (with the latest NM 6.9.2 package as well) and the Linux host, and you submit them as you did before. Please submit them as two attachments, one complete set for the connecting client, one for the server.
There is also an article in the knowledge base handling this issue:
How to solve black screen on headless machines
https://www.nomachine.com/AR03P00973Thanks for your interest. What with the coronavirus situation, we would have liked to have it ready and available to help you all out with remote working, given the current stay-at-home directives. It’s in its final stages, after some rigorous usability testing (at the GUI level) for which small changes to the GUI had to be made. Our developers continue to work remotely to complete it and bring you NoMachiners what you have been waiting for 🙂
If this result in a solution, is there any change I could get some remote support? Because this is going on for more then over two months now.
We can’t provide remote support directly on your host. This is a service we offer to customers with subscriptions (they have a customer area where they submit support enquiries) The forums is a free service we offer. We can’t guarantee that all problems reported to us on the forums can be resolved timely, although I can assure you that we do our best. If you submit the information we have requested as quickly as possible, it would naturally make the whole process go more quickly. Please submit the debug logs as Mth requested making sure you use the last email adopted to avoid our spam filter blocking your emails.
The alternative is to completely uninstall everything, remove all traces and reinstall from scratch. NoMachine works out of the box in the majority of scenarios and on hundreds of Linux distributions and shouldn’t need advanced editing of any cfg files. Editing these from the start can mess with the correct functioning of the software. So IMHO the safest and quicker option is to start again.
Can you send any files that didn’t upload to forum[at]nomachine[dot]com? Please put the title of your topic as the subject, thanks!
What OS and version is on the client? What Linux is it on the server side?
The logs didn’t attach. I would send both client side and server side to forum[at]nomachine[dot]com.
Can you submit client-side logs? This way we can check to see what’s going wrong. Follow these instructions: https://www.nomachine.com/DT10O00163#2
Also OS version, client and server side would be useful.
Good choice, it also gives you access via the browser in case the connecting clients can’t install the NoMachine package for whatever reason 🙂