Britgirl

[Britgirl]

To be able to connect to a remote computer using NoMachine, you must have a user account on that computer. If the computer is not yours, the person in charge of that computer must create a system account for you and provide you with the credentials (username and password). Once NoMachine is installed, you use those credentials to access the remote desktop. This might be useful: https://www.nomachine.com/getting-started-with-nomachine

The local user can control what level of control is possible and what notifications they prefer to receive by setting the appropriate security settings. This document indicates the default settings: https://www.nomachine.com/DT10O00154&dn=quick%20guide#3.2.

[Britgirl]

Glad to hear that the latest update fixes the issue. We’ll close this topic soon. If you need to report any unusual behaviour, please open a new topic (to avoid confusion between versions and issues reported herein) Thanks 🙂

[Britgirl]

Thanks for letting us know.

[Britgirl]

See the FAQ here:

How do I share my desktop with another user if I have the free version installed?
https://www.nomachine.com/AR10K00703

[Britgirl]

There is a little or nothing we can do for your case and NoMachine Network will solve the problem when it comes out – it’s in its final stages.

Your mobile internet modem gets a private IP address (non-routable) which is assigned by your ISP to a public IP. ISP routers don’t permit UPnP operations, NoMachine cannot therefore open a port in the router and detect the public IP.

[Britgirl]

@ggarcia, can you try uninstalling NoMachine and reinstalling the latest update from scratch?

[Britgirl]

@rshuck, we need the logs from you from the Mac on which you had the installation issues. Please check this article and submit directly to forum[at]nomachine[dot]com. https://www.nomachine.com/AR10K00697

[Britgirl]

The logs that you sent us were empty. Please make sure that you follow the instructions for extracting logs from the server side and those from the client side. On the client side make sure you tick the box “Don’t delete log files on exit” or, if possible, extract them whilst the session is open and you are reproducing the problem.

Send to us as you did before. Thank you.

[Britgirl]

Please update to the latest release for Mac, NoMachine 6.8.2.

[Britgirl]

Hi, NoMachine can be installed and works on Arch. However, it’s not in the official list of supported distributions (Redhat, Fedora, Debian, Ubuntu, Suse/Opensuse) for which we offer rpm and deb packages. The fact that a particular OS is not among our official list should not be taken as an indication that the NX software is not suitable, or doesn’t work. There are so different flavours of Linux that it would be impossible for us to support all of them, but we do try and test with as many as possible 🙂

This is why we also provide the tar.gz packages for those who are not able to install rpm or deb versions. To install, check out this article: https://www.nomachine.com/AR03L00789

All our subscription software is available in evaluation for 30 days, so you can test it out with your system first.

You could also check out the Arch user community (https://aur.archlinux.org/).

[Britgirl]

We can see from the server.cfg file you sent in privately that UPnP is enabled. We see NXUPnPPort 27468. Maybe this port is blocked by firewall or is being used by another application maybe?

Can you find the line: NXUPnPPort 27468 in the server.cfg and comment it out by adding # on the beginning? Then do from a terminal:

"c:\Program Files (x86)\NoMachine\bin\nxserver" --restart
"c:\Program Files (x86)\NoMachine\bin\nxserver" --upnpmap

The output should look like this:

Local IP 10.0.1.2
Gateway IP 10.0.1.1
External IP 11.222.333.444
NX port 4000 mapped to: 11.222.333.444:23484

[Britgirl]

Send any attachments to forum[at]nomachine[dot]com directly, make sure you put the title of the topic as the subject.

Thanks.

[Britgirl]

You didn’t paste output of the commands 🙂 Are you sure that EnableUPnP key has ‘NX’ set as its value?
Anyway, you still can use port forwarding. Perhaps these instructions are clearer: https://portforward.com/d-link/dir-890l/ You can see in the last picture there is TCP Port and UDP Port. You should set these to 4000. Then you need to set your static IP (again as shown in the how-to). Please also make sure you reserve IP address for your host or set the static IP.

The upcoming release of NoMachine Network will mean that port-forwarding won’t be necessary, and you won’t need to know your IP address. Watch out for that. You can follow the Feature Request here: https://www.nomachine.com/FR07J02731.

 

[Britgirl]

Hi,

Considering some changes in the latest kernel codes, it is necessary to apply a patch to build nxusb.ko on that version of the kernel. We can send it to you if you agree.

One of the next releases of NoMachine will include this patch.

[Britgirl]

I try those suggestions

The instructions about port-forwarding here? https://www.nomachine.com/AR11L00827

Can you describe more about your environment? Where are you connecting from? Where is the computer that you want to connect to? If you have enabled UPnP, it should show External IP and Port.

Can you paste here output (from within a terminal):

"c:\Program Files (x86)\NoMachine\bin\nxserver" --upnpstatus
"c:\Program Files (x86)\NoMachine\bin\nxserver" --upnpmap

Can you answer these questions?

– does your computer have a permanent IP ?

– is port 4000 on the router redirected to the IP address of the your computer?

– does your home IP address change often ? Can you check what your public-facing IP address is? (https://forums.nomachine.com/topic/public-ip)

For your router try the instructions to enable port-forwarding correctly: https://www.dlink.com.sg/how-do-i-open-ports-on-my-dir-890l/. Does this help?

[Author]

Posts