Forum Replies Created
-
Posts
-
kusspuss, the advice you were provided above is for the machine you want to connect to. We assumed you were trying to connect to a Linux VPS, so we gave you some tips to help you set up your Linux VM.
If i want to connect to Linux vps than how can I do that?
Can we ask what VPS you are using? We might be able to give you more precise instructions.
If you are not in control of the machine or VM you want to connect to, then you need to check with the administrator of that machine what the IP address is and check with them that the right port is open. Then from your Windows client (the computer you are connecting from) you should use that information to connect (like in the Getting started guide here: https://www.nomachine.com/getting-started-with-nomachine#internet, see fig. 8).
I suggest that you are clearer about the computer you want to connect to. We understand that you are using Windows as the connecting client, but what’s the OS you want to connect to? Have you installed NoMachine on it?
My mix-up, I thought they were new logs that Cato had asked for. He has identified the TR as a potential problem, so you should signup to receive notification of its fix. In the meantime, the other error you mention is discussed here:
https://www.nomachine.com/forums/topic/error-descriptor-fd_____-not-available
There is a patch available, not yet released, if you are interested we can send you a package to download.
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/AR11L00827
