Forum Replies Created
-
Posts
-
NoMachine Network (formerly Anywhere) is in its final stages. Then it will enter the testing phase. I can’t give a precise date of release at the moment.
Security is utmost priority for all our products. If you don’t feel comfortable opening a port on your router, NoMachine Network is what you need.
There was no evidence of a session having been started in the logs you sent us, so we can only assume that you sent us the logs from the client side (the machine you are connecting from) rather than than server side (from the machine that you want to connect to).
Enabling debug on the server side is essential for us to see why you are not able to connect to that machine. Once enabled, start a session and then zip up the logs that will have been created.
To enable these logs, go to the folder of the NoMachine installation on the machine you want to connect to, and in the /etc/server.cfg, uncomment (remove the #) where it says SESSION LOGS and set it to 7. This is the same place where you can append the key “PhysicalDesktopAuthorization 0″ in which Nars suggested you do in an earlier reply. Placing it at the end is fine.
-
I have not updated the AVC pack since I updated the NoMachine version, would this be important?
The version of the pack should not be causing compatibility problems.
Send the logs to forum[at]…..
Darknite999, please read the article here about enabling debug logs https://www.nomachine.com/DT07M00098
Reproduce the problem, zip them up and send to forum[at]nomachine[dot]com. Sorry this wasn’t mentioned in Nars’ reply.
At the moment NoMachine gives you access to the physical desktop of the Mac host. However, we are evaluating whether to insert the possibility to stream the application’s Window content into our development roadmap.
Linux can be frustrating, especially if you’re coming from Windows or Mac. To install NoMachine (or any other tar package) from command line you need to go to the directory/folder where you placed the package. For example (in this case I am installing to /usr):
$ cd /usr
$ sudo tar xvzf nomachine_5.0.63_1.tar.gz
$ sudo /usr/NX/nxserver –installOnce installed correctly, NoMachine is already up and running. A NoMachine icon (!M) will appear in your system tray. This is the NoMachine Monitor, which indicates that remote connections are ‘on’ and you can connect to this computer from another device. Another way to check it’s installed is to go to the Applications menu->Internet.
As a Linux newbie though I’d recommend you download the .deb package and not the tar.gz (and that’s for any Linux software you want to install, not just NoMachine). Downloading the .deb on to your Mint desktop is so much easier than doing things from the command line.Simply double clicking on the what you’ve downloaded will trigger the Mint package manager and install it for you.
See the screenshots I have attached. You’ll need admin rights to proceed with the installation.
I recommend this website: http://linuxnewbieguide.org/?page_id=106 for easy explanations about the different packages available for Linux OS, and how to use the Linux commands. Also this: https://linuxacademy.com/blog/linux/linux-commands-for-beginners-sudo/
From what you’ve written I don’t know what version, nor which product has been installed on your computer. I have verified that there are no issues with CentOS 6.x with the latest version of our software: the fact you can’t see anything listed in the Program/Application menu like the attached was a problem on CentOS 5 with earlier NoMachine packages. And you can see the Trouble Report was fixed in 5.0.43: https://www.nomachine.com/TR05M05492.
Do you confirm that you don’t see what I have attached in the screenshots? You need to check the version of NoMachine that you found installed on this inherited PC. If you can’t see either, tell us what version is installed by running from from an xterm or console the following command: <installationpath>/bin/nxserver –version, e.g. /usr/NX/bin/nxserver –version.
As for the documentation, the Enterprise and Terminal Server products ship the documentation for administrators who wish to configure the product with particular settings. The free version doesn’t include documentation which is taken from a selection of the guides, which you can find here incidentally: https://www.nomachine.com/all-documents. The product once installed works out of the box and should already be up & running, meaning you can connect to your computer from another PC or device, or you can use it as a client to connect to another computer where NoMachine is installed.
Any feedback about documentation is welcome as we are always interested in improving it. Perhaps you could submit an email to us about what you think is missing from the installation & configuration documents, and selection of illustrated tutorials.
Thanks for notifying Graywolf, one of our developers, that updating the client fixed the issue.
As a P.S, if you’re connecting to a NoMachine server which is covered by technical assistance, your administrator can always open a ticket via the official support channel and get a reply within the response time provided by the subscription. This is what I recommend you do if you have further issues when using the latest Player with the server version being deployed at your organization.
Try the workaround available here:
A black screen is displayed when running virtual desktops on Unity 3D or GNOME 3 and proprietary drivers
From the message you’re getting, NXWmRunningHelper: WARNING! Failed to open display ‘:0′, it looks like you’re attempting to connect to the physical display (and not virtual desktop sessions). We are not aware of similar problems. Ideally, we’d need to see the logs of both client and server to be able to understand why this specific user has trouble connecting. Please refer to the article about extracting logs and send them to forum[at]nomachine[dot]com. https://www.nomachine.com/DT07M00098.
If you wish to install any of the NoMachine packages from command line, for example because you are installing from remote by SSH or similar tool, please read the instructions here: https://www.nomachine.com/AR01L00775.
The desktop environment you have running there, whether it’s XFCE or any other Linux DE amongst the tens of variations available, doesn’t matter to NoMachine.
We consider physical desktops all desktops that are either really physical (in the sense that they are running on physical hardware) or that are running as physical desktops inside a virtual machine. Any of our server products perfectly fit this scenario, and that includes the free version which permits access to the physical display.
Your screenshot shows KVM running Debian instances, but these virtual machines could be any of the other supported operating systems, so Windows and Mac, running inside VMware, Xen, among others and even in a Docker container. You configure and run NoMachine inside such VM instances as you do on a physical computer.
The question here is not a technical one, rather a licensing one. The free version is for individual use (and that can be in a private or work environment). Section 2. GRANT OF LICENSE AND TERMS OF USE of the EULA is quite clear about how it can and can’t be used. https://www.nomachine.com/licensing-5. If your scenario doesn’t fit into the use cases that we describe in a) and b), I suggest you contact the sales team to get further guidance. Click Contact Us in the footer of the website and select Sales Enquiries.
-
