Britgirl

[Britgirl]

I suggest you update to the latest version and if the problem persists, please open a new topic.

[Britgirl]

The logs were probably too big to be accepted. Submit them to forum[at]nomachine[dot]com. Make sure you include the link to the topic.

Please also provide some further information about the client OS you are using and what is on the remote host you are connecting to (distribution, version, NoMachine product, see ‘What to include’ below).

Thanks

 

[Britgirl]

If the lssas.exe process is working in protected mode one, possible workaround is to configure antivirus software, so that it doesn’t enable additional security settings in Windows. In AVG it’s possible to check ‘Disable antivirus self protection’ option.

Other anti-viruses can have a different name for this setting. In the worst case scenario, the user needs to completely disable/uninstall antivirus software.

[Britgirl]

There is a new TR related to the recent findings above.  Please sign up to know when a fix has been released using ‘notify me’.

https://www.nomachine.com/TR06O07893

[Britgirl]

There is a Trouble Report which we have open on this issue: https://www.nomachine.com/TR03O07676. Please sign up to know when a fix is available with the ‘notify me’ option.

[Britgirl]

‘BaseDirectory’ represents the folder where the application gets installed. On Mac, this is usually Applications.

[Britgirl]

Please consult the following article for instructions on how to enable logs.

https://www.nomachine.com/DT07M00098

Reproduce the issue and send us <home_directory>/.nx, /usr/NX/var/log and /etc/sssd/sssd.conf.

You can also check the content of /var/log/secure or /var/log/auth.log (depending on distro) for entries suggesting authentication failure.

[Britgirl]

Thanks for letting us know.

[Britgirl]

Hello, we’ve not been able to reproduce on Gentoo, using SSH port set to 222 and by setting the same rules in iptables. What I suggest is you update to 5.3.9 and see if the problem persists and let us know.

[Britgirl]

Fixed in version 5.3.9. See:

Black screen occurs when connecting via web with WebRTC enabled
https://www.nomachine.com/TR05O07747

Please update.

[Britgirl]

Thanks for the feedback 🙂

NoMachine is compatible with Nougat tablets. The app you find in the Play store is for Android tablets but not optimized for phones which is the reason why you see the desktop cut off on the sides.  If you install it on a tablet, you’ll see that the sides aren’t cut off at all. We’ll update the app’s page to make it clearer that phone users should come to our website to download the app.

An app for smartphones is planned and will be released as part of the NoMachine 6 branch, so look out for that. It’s coming soon!

https://www.nomachine.com/FR12M02991, on the other hand, is still under evaluation and hasn’t been inserted in to the roadmap yet – let’s get version 6 out first 😉

[Britgirl]

What with the great variety of desktop environments available for Linux hosts, a certain desktop may not run out-of-the-box. Moksha is not a common DE amongst our users which favour predominantly Gnome, KDE, XFCE, LXDE, Cinnamon. It’s impossible for us to test all distros with all possible DE flavours available.

With regards to the comment about updating – our choice by design was to use our own upgrade servers and protocol, or for those who don’t want to update from our own servers, there is the possibility to download the package from our website and launch the usual procedure for updating Linux packages.

We tested that installing the package from our website installs correctly. We’ll investigate further with the software updates method.

[Britgirl]

Mac El Capitan 10.10.5

NoMachine 5.2.1 (did not yet upgrade to latest)

This is on the server side I take it. What OS are you connecting from? Knowing your complete set-up will allow us to investigate, following the exact same steps. It is advisable to update your software in any case.

I get mostly “No available sessions on this server” just like per https://nomachine.com/TR11K04044

This TR is from 2014 and on version 4. It’s very unlikely that the issue you are encountering is caused by a bug from a much earlier version.

What I suggest is you enable debug, reproduce the problem and then send us the logs (to forum[at]nomachine[dot]com. Both server and client side. Please follow the instructions here: https://www.nomachine.com/DT07M00098

Update: we haven’t been able to reproduce the problem, so logs would be useful.

[Britgirl]

We are not able to reproduce this issue. Since we’ve released 5.3.9, updating is advised just to make sure whether the problem persists. We will then send you a debug package for your 5.3.9 installation.

[Britgirl]

Since we haven’t received logs, I suggest you update to 5.3.9 and let us know if the problem persists. If it does, we’ll need logs to be able to investigate further.

[Author]

Posts