Forum Replies Created
-
Posts
-
Thanks for letting us know. We’ll check it in preparation for supporting the official version when Apple releases it.
Here are some further notes about our policies for supporting pre-release or beta versions of supported operating systems: https://www.nomachine.com/AR03E00450
Hi, we’ve never come across this before, and unfortunately we don’t have access to the hardware you are using, so any attempt to reproduce on the fly hasn’t been successful with our own set-ups. You could enable debug, reproduce the issue again and send us the logs, but it would probably be quicker if we send you a debug package to help us investigate. Would you be able to do this?
From the error message it appears the password is wrong. Can you please verify that your password is entered correctly, for example by writing it in a clear input field momentarily within the NoMachine app? It could possibly be a problem with interpreting some characters which is causing the wrong password to be sent.
It’s not clear from what you’ve written what is actually missing. Can you send us a screenshot of the weird behaviour you are seeing?
NoMachine can connect over any network to the remote PC provided you know its IP address, not just on LAN. With the release of NoMachine Network the need for knowing the IP address will be removed, giving users two ways to connect. Is this perhaps what you are referring to?
More info here: https://www.nomachine.com/FR07J02731
Hi, thanks for letting us know. If you notice any unusual behaviour again, let us know and we’ll look into it 🙂
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.
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/AR11L00827If 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
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.
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.
/etc/NX/nxserver --restartThe problem is that — has to be enclosed with the ‘code’ tags which I have now corrected in both Mth and Nikolas’ posts 😉
@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/syslogcontent?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.
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.
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!