Forum Replies Created
-
Posts
-
Once you’ve installed NoMachine on your VM, you need to open port 4000 in your VPS setting (I don’t know what provider you are using) I’ve attached an example of what I had to set on my Elastichosts VM (TCP 4000).
Then, to connect, you need to use the IP address or hostname that your provider allocated. E.g in our Amazon AWS tutorial you can see that Amazon allocated:
ec2-54.194.185.70.eu-west-1.compute.amazonaws.com
(link to our tutorial for installing NoMachine on AWS – https://www.nomachine.com/accessing-your-remote-linux-desktop-on-amazon-elastic-compute-cloud-via-NoMachine)Attachments:
Sorry for the late reply. As a rule we test problems that users are reporting on both the version they are using and also the most recent version released if there has been a software update in the meantime. We haven’t been able to reproduce on either. So what you should do is submit logs:
Do the following:
– please disable autocleaning of logs in the /usr/NX/etc/node.cfg by setting ‘SessionLogClean 0’
– restart the nxserver
– reproduce the problem with audio and then gather up the logs: sudo tar cvfz NoMachine-log.tar.gz /usr/NX/var/log
Send them to forum[at]nomachine[dot]com
I replied but my post is being held for moderation?
We moderate everything – unfortunately trolls are frequent as are spammers 😉
See Kroy’s answer above. The IP you are using (the one you circled) is for connecting to that computer from another computer or device. So, go to another device, install NoMachine, and enter the IP of the computer you want to connect to.
We need a little more information to be able to provide further guidance, see below in the ‘What to include’ 🙂
What machine OS are you connecting to, and version?
What NoMachine product have you installed on it, and version?
Are you connecting on a LAN, over WAN?
There is a Trouble Report documenting this issue.https://www.nomachine.com/TR03O07677
Please sign up to receive a notification when a fix has been released.
In the near future it will be possible to eliminate these problems of having to know your IP address by using our Network (was Anywhere) service which is in its final testing stages. If you want to sign up to the beta programme, let us know 🙂
Are you trying to connect using NX or SSH? This seems to be a server-side problem. Can you tell us what is installed on the server (OS and version)? Is it possible for you to contact the administrator? They can then open a support enquiry in the customer area or contact us directly via Contact Us and our Info team will try to provide further assistance.
We’ve been unable to reproduce this. Can we send you a debug package for you to install? You will need to gather the logs (we’ll provide instructions).
You need to edit the server.cfg file.
EnableUPnP noneCheck out the article online which explains where to find the server.cfg. See the penultimate paragraph “Disabling UPnP/NAT-PMP port mapping”
How to connect to NoMachine when the server is behind a NAT router or a firewall
https://www.nomachine.com/AR11L00827No it’s not a new default feature, it’s been like that since the beginning which makes me think that maybe you are connecting to a desktop with a user account which is NOT the owner of the desktop you want to connect to. The default behaviour, as explained here: https://www.nomachine.com/AR04K00663, is when connecting to the remote desktop of a NoMachine host (server), the server asks for authorization to the remote desktop owner when this owner is different from the user who is requesting to connect. The connecting user must have a system account on the remote machine.
If you need to connect automatically to the remote desktop you have 2 options:
1) Run the connection as the same user who is logged-in to the remote desktop. If the connecting user is also the desktop owner, no authorization is necessary.
2) Configure the server on the remote machine to accept connection requests without asking for desktop owner’s authorization.
If you can confirm that you are doing exactly as stated in option 1) then we need more information:
i) what version of NoMachine on the server and connecting client
ii) what NoMachine product is installed on the server
iii) what OS is on the server
