Forum Replies Created
-
Posts
-
During installation NoMachine detects the default desktop environment set on the system and configures the node accordingly. If you don’t want to run the default one, you change it. It could be that this is what causing the problems?
Firstly check that in the node.cfg that you have:
DefaultDesktopCommand "/usr/bin/startxfce4"written there. More info is in our KB here: https://www.nomachine.com/AR04K00667The patch has been queued up (and already fixed) for the next available maintenance, but I can’t say exactly when that will be. We can send you over a link to download a patched package. Can you tell me if you are using RPMs 64 or 32 bit?
Hi, this is weird. We’ve been unable to reproduce the behaviour that you have described above, with and without Samba, but to no avail. You mention “an obscure fix” you found on the internet. Can you pass us the link?
Hi, to understand better what is happening, we need to see the server-side logs from the AWS CentOS machine.
Please follow the instructions here: https://www.nomachine.com/AR10K00697 and then send them to forum[at]nomachine[dot]com.
Terminal Server works out of the box for a myriad of distros and set-ups, so why are you getting that message is unclear. You don’t mention the desktop environment. You mention you have an older version (note that forums handles the latest version only), what’s not clear is whether you have installed version 6 on top of that. If I were you, given that you have a subscription, I would open a ticket in your customer area, also to avoid sensitive data being published here.
You need to be using at least 6.3. The possibility to know the version of each client connecting was introduced with this Feature Request.
Hello, can you try sending again? We checked to make sure that everything is working and it is. We’ve also checked our mail server as well for attempted receipts from your IP address and domain. You can also try submitting here if they are small – I wasn’t sure how big they would be, hence I suggested to send them directly.
The evaluation software provides 30 days, after which you will need to make a fresh reinstall. Alternatively, you can contact the sales team and request an extension.
The free version connects to the physical display only.
This is planned. Please see:
Forwarding SSH agent authentication to the remote nodes
https://www.nomachine.com/FR09Q03878@rcasero can you update to the latest version and tell us if the issue continues? (any further debug will be based on the latest version)
Can you send us the logs of the problematic node? Follow the guidelines here: https://www.nomachine.com/AR10K00697 at
Then send them to forum[at]nomachine[dot]com making sure you put the title of the topic in the subject. Thanks!
Please send the logs directly to forum[at]nomachine[dot]com making sure you include the title of your topic in the subject. Thanks!
Fixing it is not so simple, because we need to add support explicitly for KeeAgent/Pageant. The FR has been made public here: https://www.nomachine.com/FR09Q03877
If you are using Putty, you could try using the option ‘Private key’ authentication with ‘Forward authentication’ option checked, making sure that it’s in the OpenSSH format or convert it. To do that choose the key file in the PuTTYgen main window. Then go to Conversions->Export OpenSSH key to export your private key and save it.
Some useful info about key based authentication with NX protocol here and for SSH protocol is available here: https://www.nomachine.com/AR02L00785 and https://www.nomachine.com/AR06O00932
btw, when a TR has a “due to be fixed in ” version, it indicates a target, we can’t however guarantee that the a fix will be found, and the target should change to the version that we are currently on. For some reason, that particular TR wasn’t updated to show a later target version.
As Fra suggested previously,
please check that the ‘Match the client resolution upon connecting’ box is unchecked
As for the page-peel, see our online guide here: https://www.nomachine.com/DT10K00060#2. It’s in the top-right corner.
Maybe you missed the Welcome Screens when you first connected and then disabled them? You can re-enable them by following the instructions here: https://www.nomachine.com/AR11O00951