Bilbotine

[Bilbotine]

Hi Thomas,

Could you please send us a full set of logs to forum[at]nomachine[dot]com (making sure you reference this topic) ?

If needed, the procedure to follow is explained in the article “How to gather debug logs for support requests” (https://www.nomachine.com/AR07K00677)

[Bilbotine]

Hello G,

We need debug NoMachine server logs to investigate further. Please follow the instructions here: https://www.nomachine.com/AR07K00677

and send them to forum[at]nomachine[dot]com.

After enabling debug logs on problematic machine please execute: /etc/NX/nxserver --restart

and after that try to reproduce the issue.

Please send first set of logs just after ‘restart’ and next part when the issues occurs again.

Please also provide the exact version of OS X Yosemite that you are using.

• This reply was modified 9 years, 8 months ago by Bilbotine.

[Bilbotine]

Hi Quantum,

The key should not change by itself over the night. It can change only after reinstallation of the software.

Can you confirm that you didn’t reinstall it in the meantime ?

Also, do you use the same access details (IP, port) as the ones used initially for the first connection to a host ?

[Bilbotine]

Hello Steve,

Logout from virtual session should terminate all the processes opened by this session. Currently we know issues with remaining system processes after terminating. Hopefully the update of systemd (part of your Linux distribution) will fix it.

We have not been able to reproduce the issue with shells and running applications not exiting during termination in our laboratory.

Could you please collect the content of /home/<userdir>/.nx and /usr/NX/var/log directories (server side) while reproducing this problem and send it with the list of remaining processes to forum[at]nomachine[dot]com?

There are several options to terminate virtual sessions:

– to restore the possibility to decide if a session should be terminated by dialog during disconnecting, set in:  /usr/NX/etc/server.cfg  the key  ConnectPolicy … dialog=1  and restart the server.

– when you are connected to the server, you have a list of running sessions. You can right-click on a virtual session and select a “Terminate session”.

– log out from session.

– terminate a virtual session via terminal by running as root  /usr/NX/bin/nxserver –terminate [<sessionid> | <display> | <username>]

sessionid and display the number of virtual sessions you can get by running  /usr/NX/bin/nxserver –list

[Bilbotine]

Hi keyxmakerx,

Do you mean to access your server from a different device by using NoMachine?

In this case you need to install NoMachine (server) on the machine you want to reach. On the device from which you connect, install NoMachine client, that also exists for Android tablets and iPads.

We will be happy to reply to more specific questions. You may also contact us privately by sending a contact request (the contact form can be found here: https://www.nomachine.com/contact-request)

[Bilbotine]

Hello drastrogeek,

I can confirm that the trial version is not slowed down on purpose. This is not our aim.

That said, it is difficult to compare the current version with the one you tried years ago.

The slow down you experienced could be caused by various parameters: bandwidth limitations, a more modern remote desktop that is more graphicaly intense, etc.

[Bilbotine]

Hi songjiang,

It looks like the problem is the home router configuration. Could you please check if NoMachine works OK on the local lan ?

Please also send us the logs to forum[at]nomachine[dot]com, making sure you reference this topic. It will allow us to check if the problem comes from the router or not.

If needed, the procedure to follow is explained in the article “How to gather debug logs for support requests” (https://www.nomachine.com/AR07K00677).

[Bilbotine]

Hi Quantum,

Please try this command: /usr/NX/bin/nxplayer —session session_file.nxs

[Bilbotine]

Hi again Quantum,

Let me first clarify that this file cannot by executed from bash or with nxclient/nxnode, like you have tried.

What you have to do is: move session file (.nxs) from Documents/NoMachine (or from .nx/config if you have some session files created by NX 3.X) and then click on the icon.

Let us know if you still encounter problems.

[Bilbotine]

Hi tonymc,

In order to help us investigating, could you please send us the logs files ? Please send them to forum[at]nomachine[dot]com, making sure you reference this topic.

If needed, the procedure to follow is explained in the article “How to gather debug logs for support requests” (https://www.nomachine.com/AR07K00677).

[Bilbotine]

Hi bgmarchand,

The free 3 worked as a terminal server limited to 2 users. This functionality (virtual desktop) is no longer available in the free version.

In order to have this feature, you can try the NoMachine Workstation. You can download a 30-days evaluation version here : https://www.nomachine.com/download-enterprise#NoMachine-Workstation.

[Bilbotine]

Hello songjiang,

In order to help you, we need to know:

– does your Mac have a permanent IP ?

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

– does your home IP address change often ?

– do you use noip.com or something similar ?

– when you are in the office, do you have the possibility to check if the home IP address has changed ?

– is the router at work redirected to port 4000 on the IP address of your Linux?

 

You don’t need to set the HTTP proxy if you have forwarded the port on the router.

The following article describes how to connect to NoMachine when the server is behind a firewall: https://www.nomachine.com/AR11L00827

[Bilbotine]

Hi Quantum,

Yes it is possible; NoMachine stores connection files in the following paths:

Linux:  ~/Documents/NoMachine

Windows: C:/Users/<user name>/Documents/NoMachine

Mac: /Users/<user name>/Documents/NoMachine

It should be enough to move a connection file from that directory to the Desktop and the client on it to start a session.

[Bilbotine]

Hi npn,

Thank you for reporting this issue.

We have opened a TR for it, you can find it here: https://www.nomachine.com/TR04M05259.

If you would like to be notified when it will be solved, please tick the box “Notify me when the TR is closed” at the bottom.

[Bilbotine]

Hi keyxmakerx,

Currently NoMachine tries to configure automatically a router to allow incoming connections. If it is successful, details of an IP and a port to use to connect are available in the Player GUI.

Routers supporting UPnP or NAT-PMP are configured automatically to pass connections to NoMachine and all required informations are displayed at initial screen (Welcome to NoMachine).
Routers not supporting UPnP or NAT-PMP and Firewalls have to be configured manually to pass traffic to port 4000 (NX protocol), 22 (SSH protocol on Linux/MacOSX) or (4022) (SSH protocol on Windows).

What you ideally need is NoMachine Anywhere. It will be perfect for users who either don’t know their IP or are not able to configure their router for whatever reason.
NoMachine Anywhere is in its final stages of development and will be introduced along the development of the new version 5.

[Author]

Posts