Britgirl

[Britgirl]

From you’ve written Patok, this is probably what you’re interesed in:

Making it possible to treat multi-monitors on the client as separate monitors in virtual desktop sessions
https://www.nomachine.com/FR12K02799

[Britgirl]

This is a Trouble Report, we’ve reproduced it: https://www.nomachine.com/TR03R09591

Please use the ‘notify me’ utility to receive an email from us when a fix has been released.

[Britgirl]

Cannot add server pc1:4000. The remote server type NoMachine cannot be be a server of server type NoMachine cloud server evaluation .

The free version cannot be added to Cloud Server. Choose any of the Enterprise-oriented products. If you are looking for the enterprise version of the free NoMachine package, you should download and install Enterprise Desktop.

The second error is not so simple. You need to have configured the foreign server (so there is no NoMachine software installed) so that its physical desktop allows remote access, and the cookie for this access has to be in the default xauthority file of the user you are trying to use to add this server.

I would suggest you start again, and follow this tutorial: https://www.nomachine.com/adding-servers-to-nomachine-cloud-server-via-the-user-interface for how to add servers via the GUI.

For advanced configuration and set-up, please refer to

3.5. Federating ‘Foreign servers’ under a Cloud Server
https://www.nomachine.com/DT02O00123#3.5

and

How to use NoMachine v. 6 to access legacy unix-based systems (foreign servers)
https://www.nomachine.com/AR11O00943

Let us know how you get on.

[Britgirl]

The logs show you are using an older version, namely 5.1.x. Please update to the latest version and check whether the issue still persists. If it does, we will need a new set of logs from the Workstation version 6. Issues related to version 5 can be handled in the customer area if you have a valid subscription.

I also suggest you consult the following documentation relative to version 5:

Integrating NoMachine with Various Authentication Methods
https://www.nomachine.com/DT07M00088

How to set up key based authentication with SSH protocol
https://www.nomachine.com/AR06O00932

[Britgirl]

So I DO need to change the SessionLogLevel to 7 in the server.cfg and node.cfg files and SessionLogClean 0 in the node.cfg file?

Yes – remember you need to do this on the Linux server host.

Also, since the update tab is under ‘Server preferences’ this still represents the player version (as well)? In that case it’s indeed version 6.9.2

Yes

[Britgirl]

Please send to forum[at]nomachine[dot]com and reference the title of this topic as the subject. Thanks!

[Britgirl]

Please take a look at this:

How to uninstall NoMachine on Mac
https://www.nomachine.com/AR12K00767

[Britgirl]

Submit the logs as requested including the steps (given you are using the free version which doesn’t support web sessions, there is no need to set the debug level for web sessions).

If you have Enterprise Client installed, open the GUI, click on Settings -> Preferences -> Updates. If you have the free NoMachine (server/player combined package) on your Windows host, see:

https://www.nomachine.com/DT11M00106#3.6.

[Britgirl]

Please submit them to the email address that bro provided making sure you put the title of your topic in the subject. Thanks.

[Britgirl]

There’s no workaround. However, development is almost finished, so if it doesn’t make the next maintenance release, it could be the one after that. So please sign up to receive notification using the ‘notify me’ utility.

 

[Britgirl]

The logs you submitted were not complete. We need the whole directory as per the article mentioned above.

[Britgirl]

Hello,

this is a known issue and a fix has already been scheduled for the next maintenance release 🙂

https://www.nomachine.com/TR09P08876

[Britgirl]

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.

[Britgirl]

There is also an article in the knowledge base handling this issue:

How to solve black screen on headless machines
https://www.nomachine.com/AR03P00973

[Britgirl]

I can’t provide you with that information at the moment.

[Author]

Posts