Britgirl

[Britgirl]

NoMachine 8.2.3 has been released and contains the official fix. Thanks everyone for testing the patch and providing their feedback 🙂

[Britgirl]

Ah ok so you’ve configured your Windows PC to not use a password for remote connections by changing a system policy key, like explained here: https://superuser.com/questions/106917/remote-desktop-without-a-password.

and outlined here:

How to connect to Windows with NoMachine and an empty password
https://kb.nomachine.com/AR05L00802

 

[Britgirl]

Thanks for the feedback. Indeed, desktop sharing is one of the features of version 8 that we gave considerable thought. Being able to share your desktop with others on the fly needs to be under your control at all times. The input priority mechanisms in NoMachine that you mention mean that you always have control if someone is connecting to your desktop.

[Britgirl]

It’s not possible to remote into the computer without system credentials (not without explicitly changing your Windows settings). Please check this follow-up in a similar topic: https://forums.nomachine.com/topic/how-do-i-create-a-user-name-and-password-for-remote-control#post-37002

[Britgirl]

Hi, logs show that it’s an issue that we have also reproduced in our labs and are currently working on. For the moment, the only workaround available is to disable Wayland and use x.org.

[Britgirl]

The issue appears to be on the server side. To understand what’s happening, we need to see the logs. Please submit the server logs following the instructions here https://kb.nomachine.com/DT07S00243 and sending them to forum[at]nomachine[dot].com.

 

[Britgirl]

Hi, can you send us the NoMachine logs from both sides?

For detailed instructions, check this document: https://kb.nomachine.com/DT07S00243

You can also enable debug level 7 from within the server settings (on the Windows 10) if you are using verison 8. Once you’ve reproduced the error, send everything to forum[at]nomachine[dot]com, making sure to use the title of the topic as the subject of your email. Thanks!

[Britgirl]

Hi,

do you the latest version installed on both client and server? By “community” I assume you mean NoMachine Free Edition.

What Linux distro is installed on the server? Is it with Wayland? If so, please see the following article which contains suggestions and tips for Wayland desktops running in VMs:

Connecting to a Wayland-based desktop running in a Linux virtual machine
https://kb.nomachine.com/AR04R01083

Some further tips are also available here: https://kb.nomachine.com/AR02P00969

[Britgirl]

Good question. Actually no. But we thought of a product that would solve the same problems that we have within our company and that of our customers who’ve told us about the problems they have within their own organization to manage a large number of machines; machines that can be virtual but also physical, even servers, or users’ desktops. If we were to tell you the truth and say what the alternative products are, we would frankly tell you that there aren’t any 🙂

If we were to think of alternative products, we can think of the system with which you carry out management and access the virtual machines that, for example, Amazon AWS makes available. We could say the management and access system to the virtual machines that Google Cloud makes available, and we could also say the management and access system that Microsoft makes available on MS Azure. However, these are all “products” that are integrated with the access system to the Amazon, Google and MS Cloud Systems and for access to their virtual machines. If we had to name a product that does it on physical machines for use within your company, we don’t know of one. Indeed, since you have done this analysis, if you could tell us who they are, you would be doing us a big favor!

[Britgirl]

Hi, guest connections (with Guest Desktop Sharing) are for attended computer scenarios. I.e., someone needs to be in front of the remote computer to accept the guest. Guests connect only with the explicit approval of the user who is working on the desktop you want to connect to.

Is it just you connecting to the remote Windows laptop? You can use your Windows system credentials (username and password) to log in to it. As the “desktop owner” you can always connect.

Or are you allowing other users to connect to your laptop? If you want to let others connect and you don’t wish to share your account details, you should create accounts for them on the Windows host (these are called system users). Then, you can set in Server settings -> Security ->Don’t require acceptance if the user logged in as a system user. By default system users must be explicitly accepted by you. Ticking the box means other users (system account users, not guests) won’t need your authorisation.

[Britgirl]

Could something have changed in your LAN’s configuration?
Is the phone’s IP address in the same subnet as the server?
Can you ping the phone from PC on which NoMachine server is installed?
Can you ping desktop client from PC on which NoMachine server is installed?
Can you ping the PC (where you have installed NoMachine server) from the desktop client?

Are you sure you’ve (or someone else) has not changed the port on the server to a different port than 4000?
To what port on the router did you redirect the connection from the Internet to the NoMachine server?

What is the OS on the NoMachine server? Does the server have a firewall?
Can you temporarily turn off firewall during LAN connection tests?

[Britgirl]

Hi, we need to check something first. Can you disable Sharpkeys (for this quick test) and then check again if shortcuts are working as expected or are still wrong within the NoMachine session.

[Britgirl]

Hi,

can you tell us the complete DefaultDesktopCommand you are using?

We see that you are probably using custom built binaries. Have you checked that you can login to the GUI locally? I.e not with NoMachine involved.

If you can, open a terminal and run env > /tmp/env-i3.txt. Send us the file and we’ll take a look.

[Britgirl]

Hi Mark,

Those exit codes, actually, are the exit codes of the external programs run by the server, with these external programs being mainly “system commands” of the specific platform, the specific OS where the server is running on. So, to understand what the exit code means, you would need to know, for each exit code, what was the external program that was executed. These exit codes, for the record, are very “application specific”, and so, if I were you, I wouldn’t give much importance to these. Of course the server DOES GIVE them the importance they deserve, since the server KNOWS what the program is that is run and also what exit code the program will return, for every error the server expects. So, all in all, difficult to give you an informative answer. Need to know the context, what the server is doing, what is the program that is run and the exact log lines the server prints, for the procedure, before and after.

If you send us a few of the log excerpts of the problematic user sessions (submit to forum[at]nomachine[dot]com) and we can then give you some pointers to help you with your own debugging 🙂

 

[Britgirl]

Thanks for the feedback 🙂

[Author]

Posts