Forum Replies Created
-
AuthorPosts
-
BritgirlKeymasterAt a glance, it seems like a problem with access to the local xserver. Could something have changed on the system that would trigger this? Having a look in the session directory from var/log/node/ could reveal something useful.
It’s impossible for us to know why this is happening without taking a look at the logs. First of all, I would update to 7.8.2 if possible because there have been several releases since 6.9.1 and we can’t be sure that this isn’t related to something we already fixed. If the problem is still there after updating, enable debug, restart the server and then gather the logs up. Send them to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Instructions for enabling debug are available here: https://knowledgebase.nomachine.com/DT11R00182.
BritgirlKeymasterWhat version and product of NoMachine software are you using on the Linux side?
What is the distro?
What’s the desktop environment?Is it headless?Ā See the tips here:
Connecting to Linux headless machines with NoMachine
https://knowledgebase.nomachine.com/AR03P00973Is Wayland used?
Notes for connections to Linux physical desktops running Wayland
https://knowledgebase.nomachine.com/AR02P00969Is it a virtual machine? If so, check this article:
Connecting to a Wayland-based desktop running in a Linux virtual machine
https://knowledgebase.nomachine.com/AR04R01083
BritgirlKeymasterHi, we’re still working on this. We’ll update the topic once we have some news about a possible solution.
BritgirlKeymasterThe server shouldn’t be making any sound at all whilst someone is connected to it. And from what you write, I understand this is not happening.
Please, when you’re connected to the server, open the menu with ctrl-alt-session, go to Devices, select Audio and take a screenshot and attach it here. This will show me what I indicated in my previous reply when I referred to the Connection Menu Guide, picture 18.
Also please tell me the versions of Windows both sides otherwise we won’t be able to investigate.
March 7, 2022 at 18:07 in reply to: Problematic keys when connecting from Mac to KDE on CentOS #37821
BritgirlKeymasterJust a quick update on this. We decided to order a Logitech MX Keys for Mac to investigate, which we are in the process of doing now.
BritgirlKeymasterThe licenses cannot be stored in another location. However, upgrading /updating the software as per the documentation’s instructions is a safe procedure and does not touch the server.lic files unless users remove the entire .nx directory.
BritgirlKeymasterUpon connecting the person sitting in front of the computer you are connecting to should see the mouse being moved. Can you tell us a bit more about your set-up? What Windows version on the client side, what Windows version is on the computer you want to connect to remotely?
BritgirlKeymasterThis is a functionality supported in, for example, NoMachine Workstation, of the Terminal Server range. Take a look at this page: https://www.nomachine.com/terminal-server.
BritgirlKeymasterWe aren’t able to reproduce this. By default the sound on the server-side is muted and audio is heard within the session.
Please take a look at https://knowledgebase.nomachine.com/DT10R00167?#6.1 (section on Audio).
Note that pressing mute (Fig. 17) will mute sound in the session. Is this your case?
Can you tell me if the checkbox ‘Mute audio on server’ in Fig 18 is ticked or not?
March 7, 2022 at 13:02 in reply to: New Install of free version on Manjaro no admin credentials #37814
BritgirlKeymasterHi, Please provide clear steps describing the problem you are encountering.
I’m not sure what you mean by “close out of the service”.
You’ve downloaded the packages from the Arch repository and I don’t know whether those packages are the same as the official ones that you can download from our website, or whether something has been changed. Installing packages from the NoMachine website onto your computers requires admin privileges.
I was never prompted for a password setup or account setup.
In order to access a remote computer using NoMachine you need a system account on that remote computer. You use the credentials of the account (username and password) in the NoMachine login prompt. Are you the administrator of the computer you are accessing or is it managed by someone else?
BritgirlKeymasterHello,
as yet we haven’t made public an exact time frame or date of the release of version 8. It’s currently in its final stages and we’ll publish any news right here in this forum š
BritgirlKeymasterTry disabling the āUse acceleration for display processingā option in the Server settings -> Performance panel on the Windows machine.
March 1, 2022 at 15:48 in reply to: Always connect to virtual session instead of physical desktop session #37744
BritgirlKeymasterI would like not to have the choice at all, as my machines are actually machines used by my folks who do not care about accidentally selecting the wrong session type. So how do I get rid of the unwanted desktop environments?
You will have to do that at the system level, this is not something you set in NoMachine. For example, https://forum.kde.org/viewtopic.php?f=289&t=151924, or you can just set auto login, again at the system level. The OpenSuse user forums will be the best place to ask that question.
BritgirlKeymasterYou can modify the server.cfg (/usr/NX/etc/ directory on Linux) to prevent resizes:
PhysicalDesktopMode 1
# 1: Restricted. User connected to the physical desktop can
# interact with the desktop except for resize operations.Try this and let us know.
BritgirlKeymasterNoMachine’s cfg files are inĀ /usr/NX/etc/ and notin /etc/NX/server/localhost/server.cfg.
/etc/NX/server/localhost/server.cfg should not be edited by users.Ā Remove the line:
ServerSlaveBase 30000from that file and add it to /usr/NX/etc/server.cfg.
You can find more about the server and node.cfg files here: https://knowledgebase.nomachine.com/AR02N00877.
-
AuthorPosts
