Forum Replies Created
-
Posts
-
Just to clarify a small detail. When you mention NoMachine session, which is on Ubuntu, knowing which desktop environment you are connecting to is useful for us. By “desktop environment” I mean KDE, Gnome or any other. OK, thanks for letting us know that the problem is solved. If it happens again, by all means open a support enquiry.
Hi, it’s strange that after 1.5 years of working perfectly that your NoMachine server suddenly starts doing strange things 🙂 That can happen if you have changed something on the headless Ubuntu host, like updating it or changing some configuration perhaps?
I (and others) cannot create new sessions on the server.
What desktop environment are you trying to connect to? Does this mean that you can reconnect sessions already created before the problem started, and that it’s only new sessions which are not possible?
I noticed from the logs that you are running a licensed Small Business Server. This means that you are entitled to receive technical assistance from our support team. Since the forums are public, it might be better to open a ticket and have our support team investigate directly. This will also avoid any sensitive information being accidentally published here. Full debug logs will be required, the ones you sent to us don’t appear to be the full set.
We’ll check this out, but in the meantime, can you tell us the result of the command:
sudo netstat -anlp | grep eglFirst you need to tell NoMachine which printer to use. What you have to do is add the printer you want to use from within the session (whether it’s the default printer or not on the computer you are connecting to or from).
See here:
https://kb.nomachine.com/DT10R00167
If you have an open document in the remote session, you will be able to print it on your local printer. Likewise, if you have a document open on your local desktop, you can send it to the remote printer (server-side) for printing provided you have a connection open.
Step 1 – Click on Connect a printer
Step 2 – Select from the available printers (Fig. 8)
Step 3 – Click ‘Import/Export this printer at session start-up’ if you want this to be available each time you run the remote session. Check the box ‘Make this the default printer’ if required
Step 4 – Click Connect, and wait for a green dot to light up next to your selected printer
Step 5 – Click the back button to close the menu
Hi Dennis,
we are not aware of problems with private key authentication using NX protocol. You’ve mentioned ssh protocol and I am not sure from what you’ve written if this means you’ve tried to run an SSH connection to connect to the NoMachine server from the NoMachine player. Connections via SSH protocol are not possible with the free version of NoMachine, just to be clear.
Can you tell us the version of openssh which you used to generate the RSA key? macOS version and Linux distro and version will also be helpful so we can try and reproduce here. Also useful will be screenshots of what how you have configured the NoMachine connection file (in the Configuration panel of the Add/Edit of the connection you are using).
The logs show a crash in the Intel graphics drivers. You can check to see if there is an update for the driver and if this fixes the problem.
If not, please try disabling hardware decoding in the NoMachine Windows client configuration.
You can disable it completely in the player.cfg. Please edit the file $HOME/.nx/config/player.cfg and set the configuration key “Enable hardware accelerated decoding” to “disabled”. Before changing the configuration key, you should first quit the NoMachine Player (you can do this by right clicking on the !M icon in the system tray and selecting ‘Quit NoMachine Player’.Hi Vincent, the logs you originally attached could not be opened. For this reason I have detached them from your topic. Please send them directly as attachments to forum[at]nomachine[dot]com.
the interaction between gdm and awesome wm must disable some key setting that allows NoMachine to recognize GUI.
We weren’t able to find out what because the logs we received were not sufficient and we have not been able to reproduce the problem either since our set-up in our labs correctly detects the display when Awesome is running there. We’ll consider this topic closed now that you have found a workaround.
dsat2002, your issue appears to be a different one. Please open a separate topic including details of NoMachine products, versions (client and server), OS and version (client side and server side) and steps to reproduce. Screenshots of any error dialogs you see should be attached.
Logs from after you have reproduced the problem would also be useful. On the Windows server machine, please enable logs as described in these instructions and then send them to us at forum[at]nomachine[dot]com making sure that you include the title of your new topic. Thanks!
The document is indeed aimed at enterprise usage, so far NoMachine on Windows server, what you can do is integrate Kerberos/AD and implement 2FA there. Or wait for NoMachine Network to be released in NoMachine 9.
Hi, floating windows is a feature of the NoMachine Linux Terminal Server range. I suggest you try the Workstation:
https://www.nomachine.com/product&p=NoMachine%20Workstation.Remove the free edition of NoMachine, install Workstation and then from your connecting client, start a custom session.
Further information is also available in the online knowledge base: https://knowledgebase.nomachine.com/AR03L00795 and in chapter “4.2. Connecting to the Remote Host and Choosing Session Types” https://knowledgebase.nomachine.com/DT04O00140#4.2.
From the logs you attached we can see that you have a huge screen size (server side):
Info: Using screen size 8960x3600and there is not enough memory to allocate the frame buffer.
13256 6708 15:45:08 034.568 MirrorPoller: ERROR! Can't allocate 129024000 bytes for the texture dataWhen we release version 8, we will release Windows packages explicitly for 64-bit. It could be what you need. Until then, I suggest you reduce the size of the server-side monitor.
Hi, thanks for taking the time to report this. We have yet to add Fedora to our officially supported list and will do soon. Initial tests have not shown similar issues, so we will need logs from you of the two cases you are describing 🙂 I take it you are using the NoMachine v7.9.2 both sides? Reproduce and submit logs
1) of when you get the grey screen when connecting to the login window
2) in the moment you start the desktop session after having changed WaylandModes to “drm,egl,compositor”.For instructions on how to enable logs, please see this guide:
https://knowledgebase.nomachine.com/DT11R00182You can send both sets as attachments to an email to forum[at]nomachine[dot]com. Please insert the title of the topic in the subject of your email. Thanks!