Britgirl

[Britgirl]

You have two routers, and since you don’t control them, this makes things more difficult. You would need to contact the administrator to open the necessary ports to get access to the office network from home. The easiest option for you is to wait for NoMachine Network which will eliminate this problem altogether. You won’t need to know the IP address of your computer or worry about which router you have.

[Britgirl]

Can you send in what you tried to attach to the forum topic? Please submit everything to forum[at]nomachine[dot]com.

[Britgirl]

Can you give more details about the host environment, what Linux distribution? What product have you installed – NoMachine, NoMachine Workstation, Terminal Server?

Is the user connecting to a physical desktop or is it a virtual desktop session (Linux)? If it’s a virtual desktop session what’s the desktop environment?

[Britgirl]

Please check out these similar threads and follow the advice.

https://www.nomachine.com/forums/topic/error-138-cant-connect-to-office-computer-from-home

https://www.nomachine.com/forums/topic/remote-with-no-upnp

[Britgirl]

For sure you shouldn’t be killing nxserver, nxnode and nxd processes. Additionally, nxclient -monitor should remain as well.

[Britgirl]

Hi, we’ve tested again on Red Hat 5 and also Red Hat 6 just to make sure, but we are not able to reproduce this problem using the lastest version 5 NoMachine client whilst connecting to NoMachine 5 installed on the Red Hat instance running on Amazon.

Can you confirm what versions and products you are using from our website, on both client and server?

Were there any errors shown during the installation of NoMachine packages?

And did you install anything on the RH desktop before installing NoMachine?  I.e is this a RH with factory settings, or have you installed other programs?

[Britgirl]

Seems the image was too heavy. We’ve sent you an email. Just reply to that and attach the image. Thanks.

[Britgirl]

Hi, can you tell us if updating to .63 fixes the problem?

[Britgirl]

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.

[Britgirl]

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.

 

1. 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]…..

[Britgirl]

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.

[Britgirl]

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.

[Britgirl]

Send the logs directly. They may have been too big to upload here.

[Britgirl]

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 –install

Once 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/

Attachments:

1. 

   4.png
   

2. 

   6.png
   

3. 

   7.png
   

[Britgirl]

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.

Attachments:

1. 

   NoMachine-applications-menu.png
   

2. 

   NoMachine-monitor.png
   

[Author]

Posts