Forum Replies Created
-
Posts
-
Logs didn’t attach, probably because they were too big. Send them to forum[at]nomachine[dot]com.
Just to clarify, are you connecting from this Red Hat client? When you say it doesn’t respond, do you mean the GUI opens when you start the connection, but doesn’t continue? Can you submit a screenshot of what you see when it ‘hangs’.
Or do you mean that when you try to connect, the connection just hangs? What is using 100 CPU? The connecting client or the remote host to which you are connecting?
SSH is geared towards the Enterprise users. The free version doesn’t support SSH and there are good reasons why SSH is not in the free version.
People expect software to install and work out of the box, while SSH requires that you install and configure SSH beforehand. This is not what the average user expects. Second, SSH can be tricky to configure, so why give users of the free version these problems before they’ve even started? Third, the NX protocol can use both TCP and UDP for multimedia traffic and this can make a huge performance difference.
Clearly NoMachine wants people to get the best from the software. If you are in a setting where SSH is a requirement (but you don’t want to install one of the Enterprise pay-for products), or you’re tech-savvy, then you can still tunnel the NX connection over SSH, as you would do for any other protocol.
If you are interested in knowing more about the differences, I suggest you check this article: https://www.nomachine.com/AR11K00739
We’ve not been able to reproduce this issue at all. If it’s possible, can you send us the logs from the server? You’ll need to enable logs first, then reproduce. See the instructions here and send them to forum[at]nomachine[dot]com. Thanks.
We don’t need to send you a debug package. It will be enough for you to enable debug and then submit the logs: https://www.nomachine.com/DT07M00098.
Please follow the instructions and then send the logs to forum[at]nomachine[dot]com.
We’ve not been able to reproduce this problem so we are sending you a debug package to investigate further. Check your inbox for emails from our keymaster.
Hello everyone, the patch for this bug has been released today. Update now. More details about 5.1.54 are here: https://www.nomachine.com/SU09N00176.
We’ve reproduced the issue and opened a Trouble Report. You can sign up to receive notification of a fix when it’s available. Thanks for reporting.
Error: “Cannot add firewall rule” may indicate that it’s necessary to configure the firewall manually: routers not supporting UPnP or NAT-PMP and firewalls have to be configured manually to pass traffic to port 4000 (NX protocol) or 4022 (SSH protocol on Windows).
We suggest to read:
https://www.nomachine.com/AR11L00827
How to connect to NoMachine when the server is behind a NAT router or a firewallTry submitting logs again (what you submitted was empty?). You can also send to forum[at]nomachine[dot]com.
You can send them to forum[at]nomachine[dot]com. Maximum size allowed is 1024 KB so maybe they were too big.