Forum Replies Created
-
Posts
-
I just realised you have Ubuntu 17.10. This uses the Wayland protocol which NoMachine doesn’t support yet. There’s a Feature Request in the Knowledge Base which also includes a workaround until its implementation. https://www.nomachine.com/FR10N03221
Welcome aboard 🙂
I assume you have the latest version 6 from our website.
Whilst we queue up for investigation, please take a look at this section from the Quick Guide to the NoMachine GUI: https://www.nomachine.com/DT10O00154#3.6. This is how you can identify the version you are using.
In the logs we see:
2017-11-16 03:10:52 591.999 12555 NXNODE NXTryBindLocal for port: 4001 return: -1
2017-11-16 03:10:52 592.047 12555 NXNODE tcp port ‘4001’ is used by another applicationTry allocating a different port.
NoMachine lets you blank the screen and lock the keyboard/mouse whilst an unattended computer is in use (remotely) I.e if your computer is on a table where there are others walking by, they don’t see what is being displayed.
Until the following FR is implemented, https://www.nomachine.com/FR05N03110, after you’ve finished working, it’s important you remember to log out of your account before disconnecting from NoMachine.
You can sign up to receive notification of its implementation.
We received the logs that you sent but they included on the nxdevice.log. We need to see “Setup Log” from the installation which should be in C:\Users\<username>\AppData\Local\Temp\
It’ll have a name similar to ‘Setup Log 2018-01-04 #001.txt’. Send us the newest file.
What you need is NoMachine Network (Anywhere) which hasn’t been released yet. Please sign up to the Feature Request to know when it has been implemented, https://www.nomachine.com/FR07J02731.
The public downloads provide links to the latest version. Naturally we keep a strict timeline of versions in our repository for customers which make special requests.
getting rid of backward compatibility
If you are referring to backward compatibility between version 6 and 3.5.0, the latter became legacy quite a while back, and the reason for dropping support for the NoMachine login is because we have over the years offered more and more authentication options in order to provide the most flexible and most secure integration with existing configurations available on the server host. Customers who have subscriptions with us can put in a special request to receive a download link to the earlier version if they are not able to update the server, or if they are still using NoMachine login even with version 5 (or 4). They can then distribute it to their users privately. Perhaps your administrator has already been in touch with us?
If you’re not sure, or you are the admin, please reach out to the Info team to request a download, https://www.nomachine.com/contact-request.
Are you sure you are not connecting to a Linux host (you opened the topic for Windows)? If that’s the case, can you tell us what is installed on that Linux host – NoMachine product and version, Linux distro and version?
It seems to be the bug that we already fixed, https://www.nomachine.com/TR01N06360. Can you update the software and check again?
I suggest you contact the administrator of your NoMachine server. The NoMachine login is no longer supported with version 6, please refer to the following article: https://www.nomachine.com/AR11O00947
The person in charge of the server should contact us via the website to know what options are available for environments still running legacy NX 3.5.0 and/or the NoMachine login method.
NoMachine 5.3.12-14 (Linux Mint 18.3 Cinnamon) from repository
In a previous post you wrote this. I’m not sure which repository you mean since our official packages are only available directly from our website. Can you confirm where you downloaded from?
You need to enable debug, reproduce the problem and submit the logs, send them to forum[at]nomachine[dot]com. Instructions are here:https://www.nomachine.com/AR07K00677
Congratulations 🙂
Enterprise Desktop, for access to the physical display, lets unlimited users connect. They will see the same GUI which is running on the remote host. I suggest you also take a look at the following articles which outlines the differences between NoMachine free, Enterprise Desktop etc.
https://www.nomachine.com/AR07L00808
https://www.nomachine.com/AR10K00702
By default when a user connects to a server where that same user is already connected, NoMachine migrates the running connection to the new device which is requesting to connect, it assumes you are the same person because you are using the same session file (in the Recent connections panel). To change this, create more than one NXS file, each one with a different name, so the client will not match the running session.
Hi, sorry for delay. We reproduced it and published the Trouble Report here: https://www.nomachine.com/TR12O08313
Sign up to receive notification of the fix when it has been released 🙂