Forum Replies Created
-
Posts
-
Hi Knockadoon,
We suggest as a first step to assure that the connection is arriving at the intended machine (the one at your workplace). This can be done by examining the nxd.log file and checking if there is any info about incoming connections at the time you tried.
If there is no incoming connection, you can try to set up access to the intended machine according to the following article:Â How to connect to NoMachine when the server is behind a NAT router or a firewall
Hi gsus24,
Thank you for letting us know. We are glad it works!
Logs are not required at this point. As the problem is solved, the logs are now overwritten.
In case there is the need to collect logs for future cases, you can check the following article: Collect server and client logs manually.Hi baloo0496,
The username and password required by the NoMachine are your usual account credentials from your remote machine (fig. 6 here https://www.nomachine.com/getting-started-with-nomachine).
The TR associated with this forum post was closed in the software release 7.1.3: Incorrect mouse pointer offset when dragging the cursor in a macOS session
Please update, if you have not done so yet 😉The TR associated with this forum post was closed in the software release 7.2.3: Error ‘The session negotiation failed’ occurs when a user is already logged on at the physical desktop
NoMachiners, please update 🙂
Hi Maykro,
We received your files, but the file containing Windows Logs/Security events is corrupted. Can you please recreate the file and send it again?
Thanks!The TR associated with this forum post was closed in the software release 7.1.3.
Copy paste from Windows or macOS client ends up with a NUL character with PyCharmHi lmcjoma,
We understand your concern. The program is a binary, however it is just a modified version of the nxexec binary, so it should not represent an issue. The procedure will be to simply replace the original nxexec with the test one, reproduce the problem and collect logs.
Let us know if this would be ok for you and we will send you the test program via email.Hi Coleman,
thank you!
As you well described, although it is possible to connect to a server when the monitor is powered off, in some conditions the performance of the connection is low.
We have created a feature request for this issue: Giving the possibility to automatically awake Linux server monitor from sleep mode. In the meantime, we recommend avoiding to let the screen shut down on the server machine.You can tick the box at the bottom of the feature request (‘notify me’) to show your interest and to be notified when it will be released.
Hi krypterro,
in order to further investigate the issue, we need you to collect and send us server-side logs. Please follow the instructions in this article: Collect server and client logs manually
You can submit them directly to forum[at]nomachine[dot]com putting the title of your topic as the email subject.
Thanks!Hi warpuser,
we have received your screenshots and we were able to confirm that this is a known issue.
A high priority feature request to resolve it was included in our product roadmap: Integrating the NoMachine window fullscreen mode with macOS Spaces management. Our development team is working on it and it will be fixed in the near future.
You may tick the box at the bottom of the feature request (‘notify me’) in order to receive an email when it is released.
Thanks!Hi lmcjoma,
we would like to send you a test program. Would you mind running that program in order to collect more debug logs?
Please let us know and we will send it via email.
Thanks!Hi paulnehse,
Unfortunately, we were not able to fully understand the problem. Do you mean that the screen is frozen or that you can’t log in from the login window?
Can you please provide us with some additional information? A screenshot showing the actual problem that you are encountering would also be useful.In addition, we suggest to first upgrade to version 7.2.3 as we already fixed some issues related to screen detection:
Connections to the Linux desktop (Wayland) fail
Connection to physical desktop is no longer available after uninstalling v. 6 and installing v. 7 on Linux.Thank you!
Hi sjcho,
Hardware encoding is not currently available in virtual desktop sessions running X11 vector graphic mode, but it is planned. Please consult its feature request here: Adding support for H.264 HW encoding in virtual desktops sessions running in X11 vector graphics mode. You may register to the ‘Notify me when the FR is implemented’ option on the Feature Request page to be informed when this feature is realised.
As an alternative, you can try to disable x11 vector graphics mode.