Forum Replies Created
-
Posts
-
Just to confirm that we received the crashDump. We’ll update the topic once with the results of any further investigation.
It’s not quite clear what the set-up is. Is the problem that your work’s computer is part of a restricted corporate network and your cannot access to it from home?
I thought I had updated this topic. Sorry for the delay. Right now it’s not possible to install the client without services. We are evaluating whether it can be possible to allow users to do that.
Hi, can you just confirm that it is Fedora? Is that 32bit or 64?
Also, just to be sure, are you using any brightness changing apps like f.lux on the server side?
jn505, I supposed you are using the free version on the server side. If you are using the free version on the server side, this will only ever allow you to connect to one of your display options (1 connection, 1 physical display). If you had a Workstation installed (which doesn’t limit the connections being created), for example, you would be given the option to choose which one you want to connect to rather than just one.
Hi, the address is forum[at]nomachine[dot]com. Apologies for that. Can you send them again? I believe Cato was referring to the client logs on the server side.
We’ll need logs (see here on how to extract them https://www.nomachine.com/DT07M00098) and the stack trace. Send to forum[at]nomachine[dot]com referencing your topic.
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:
