Forum Replies Created
-
Posts
-
Hi Zom-B, would you also like to try the debug package for us and send us the logs from the Windows server host?
@mcvitas please check your email inbox because we have sent you details concerning the debug package.
So this was most likely to do with your system’s configuration, and not something broken in NoMachine. Thanks for letting us know.
You don’t mention what the Workstation Linux distribution is nor the Desktop Environment (KDE, Gnome, other?). Maybe these were in your previous reply as well, under ‘Desktop version’ and seems to be missing. The images you posted can be added as separate attachments (not in the body, unfortunately) Can you send them again? Also, were you able to connect to this desktop previously?
Are you the administrator of the Linux computer that you are connecting to? Please confirm the version of the NoMachine Workstation software that you have installed. Logs would be useful from the Workstation host. You can extract them using the instructions here:
https://knowledgebase.nomachine.com/DT11R00181
If you are not the administrator, please contact them and request them to open a ticket in the customer center so the support team can investigate why you are not able to connect.
Strange problem and not one we have seen in our tests.
Open a terminal on the affected host execute ‘xdpyinfo’ and ‘xrdb -query -all’ . What’s the output?
If you change the font in the NoMachine Player settings, does the problem go away?
Hi, are you using the latest version of NoMachine software? If not, I recommend you update all machines.
We would need to see the NoMachine logs of the affected Windows host as well. Please take a look at this document for instructions for Windows: https://knowledgebase.nomachine.com/DT11R00181#1.4. Enable debug ‘restart nxserver’ not the machine, connect and if there is still ‘no available’ collect logs and send to us.
Does this problem come up after changes in the user that is opening the desktop? So multiple “fast user switches”?
EDIT: This issue could possibly be related to the TR we solved in 7.8.2 -> https://knowledgebase.nomachine.com/TR05S10241.
You posted this in the Windows forum, but without specifying if you are connecting to or from Windows 🙂 Please tell us:
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Remote and local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.).
– If connecting to Linux, desktop version (GNOME. KDE, whatever) on server.
– Steps to reproduce as well
plus send the attachments which failed to attach directly to forum[at]nomachine[dot]com.
You sent the .nx folder from the server side, but what we need is the server logs.
It could be worth trying a reinstall of NoMachine first. If that doesn’t help, enable debug, restart, reproduce and send us /usr/NX/var/log. To enable debug, please see the instructions here: https://knowledgebase.nomachine.com/DT11R00181#1.1. Send the logs to forum[at]nomachine[dot]com using the title of the topic as the subject of your email.
I managed to recuperate it and added it to your original topic. Sorry for the hassle 🙂
Can you tell me what Linux distribution and version this is?
The free version of NoMachine, installed on the computer you are connecting to, allows one connection. To connect to the remote computer, you can install any of the following on your local devices: NoMachine, Enterprise Client, the NoMachine app for mobile. If you try to run two connections from different client devices to the same RPi where you have installed the NoMachine free edition, it won’t be possible. However, since you have two separate RPIs, each one with their own NoMachine installation, running one connection on each of them at the same time from the same connecting client will be possible. What is counted (on the server side) are the permitted connections running on the machine you are connecting to.
There’s something wrong with your configuration maybe? Try removing completely and install again.
sudo /usr/NX/scripts/setup/nxserver –uninstall && sudo rm -rf /usr/NX /etc/NX /var/NX .nx
We don’t actually support Arch but we did check on the fly. Since Arch is a rolling release and it’s possible that a new system update might have broken something, we downloaded it to make sure, and installed it with the same set up as you, and were able to connect.