Britgirl

[Britgirl]

A Trouble Report has been opened regarding this issue: https://www.nomachine.com/TR05Q09329

You can sign up to receive notification of when an official patch has been released on the website. Until then, we can send you a patched package. If you’d like to receive it, let us know.

[Britgirl]

Hello, it could possibly be your router. Some routers don’t automatically accept UPnP or NAT-PMP commands, so it’s necessary to configure it manually through its administrative interface. Please consult this article for trouble-shooting.

How to connect to NoMachine when the server is behind a NAT router or a firewall
https://www.nomachine.com/AR11L00827

If that doesn’t help, we’ll need you to submit the logs from the server side, which you can then submit here or directly to forum[at]nomachine[dot]com. Logs can be found by following the instructions here: https://www.nomachine.com/DT10O00163

[Britgirl]

Hi, this is a currently know issue https://www.nomachine.com/TR05Q09329.

We can send you a patched package for further testing. If you’re interested, please write to us at forum[at]nomachine[dot]com and we’ll send you a link.

[Britgirl]

Hi, this is the same problem as discussed here: https://forums.nomachine.com/topic/black-screen-connecting-to-nx-6-7-6-on-linux

We can send you a patched package, please write to us at forum[at]nomachine[dot]com if you’d like to receive it for your distribution.

[Britgirl]

 /etc/NX/nxserver --restart 

The problem is that — has to be enclosed with the ‘code’ tags which I have now corrected in both Mth and Nikolas’ posts 😉

[Britgirl]

@pellisuk can you send system (/var/log/syslog) and NoMachine logs to forum[at]nomachine[dot]com? Please enable debug, restart nxserver (sudo /usr/NX/bin/nxserver –restart) before you reproduce problem. Instructions about debug and collecting logs you can find here: https://www.nomachine.com/DT07M00098#1.

@dlp_1 can you send just the /var/log/syslog content?

We would also like to send a debug library with further instructions which would eventually help us with the investigation. Let us know if you’re interested.

[Britgirl]

Logs would be useful for the problem connecting from Mac to Linux. We would need sets from both sides, so client logs from the Mac machine and server logs from the Windows PC. You can submit them here or send them to forum [at]nomachine[dot]com using the title of your topic.

Instructions on how to gather logs are available here: https://www.nomachine.com/AR10K00697.

[Britgirl]

Can you try disabling your firewall and then try to connect?

If that makes no difference, we’ll need the full set of logs from both the connecting client and server side which you should extract after reproducing the error. Instructions for enabling and extracting the logs are available here: https://www.nomachine.com/DT10O00163. Please send them directly to forum[at]nomachine[dot]com making sure you include the title of the topic in the subject of your email. Thanks!

[Britgirl]

Hi, the logs from the server side would be useful. Please follow the instructions here: https://www.nomachine.com/DT10O00163

You can send them directly using the address forum[at]nomachine[dot]com making sure you include the title in the subject. Thanks.

[Britgirl]

User submitted updated information that version 6.7.6 fixed the issue.

[Britgirl]

To everyone following this topic, we are aware of issues on certain models of Chromebook (it is not limited to Pixelbooks as we previously thought) and we are continuing investigations. Until we are able to reproduce the same strange behaviour which will allow us to open a Trouble Report, this topic will be archived. Any updates will be posted on the forums.

[Britgirl]

This is the Trouble Report related to the issue reported here: https://www.nomachine.com/TR05Q09323. You can sign up to receive a notification when a fix has been officially released in an upcoming update. In the meantime, we will reach out to you individually with a hotfix.

[Britgirl]

Check your inbox 🙂

[Britgirl]

Hi, thanks for the new set of logs.

They show us that there is a sudden termination of nxnode upon connection, but unfortunately they don’t provide useful hints as to why that is happening. So, I need to ask you to send us some additional information.

Please check for core files and then send us a backtrace (after having reproduced the problem again). To do that, follow the instructions here: https://www.nomachine.com/AR09L00810

You can attach the files and send them to us directly as you did last time. Thanks for your collaboration 🙂

[Britgirl]

Hi dlp_1,

we received the logs but unfortunately you enabled them when some of the processes were already running. So I have to ask you to restart the nxserver reproduce and send logs again (restart can be achieved by executing /usr/NX/bin/nxserver –restart). Thanks!

[Author]

Posts