Forum Replies Created
-
Posts
-
Hi, NoMachine’s first and foremost use case is for access to the desktop of the remote computer. Connecting to the computer without connecting to the display is not possible. Perhaps consider using NoMachine for all your remote desktop needs rather than another software? That way you would also decrease the resource usage 🙂
Hi dg, we are aware of this problem and a fix will be released in the next update. We can pass you a patched package to test if you are interested.
Are the IP address and port number correct? The message indicates that the IP address is not available from your network. Could it be that IPSEC VPN is blocking NoMachine? Can you try disabling VPN as a test to verify if problem is in the VPN configuration?
To Topnotchprincess, submit those attachments from your earlier reply to forum[at]nomachine[dot]com. Thanks
Hi the logs (which were long and for this reason were extracted and attached separately) were from the Player side. We need logs from the server side to understand why the NoMachine server cannot create a new display.
You should also tell us what desktop environment your VM is running. From what you submitted in your original question, I can’t see a desktop GUI running there. You can install one using
sudo apt-get install ubuntu-desktop.Please take a look at our tutorial for Google Cloud users:
https://www.nomachine.com/accessing-your-remote-desktop-on-google-cloud-platform-via-nomachine
If none of our tips and suggestions work and you can submit logs from the server which can be extracted using the instructions here: https://knowledgebase.nomachine.com/DT11R00182
Please submit them to forum[at]nomachine[dot]com using the title of this topic as the subject of your email. Thanks!
Can you submit a screenshot showing the problem? From what you describe it sounds like a rendering issue on the client side. Please try disabling hardware decoding on the Ubuntu 22.04 computer (client). You can do that by connecting to the server, opening the menu with Ctrl-Alt-0 -> Display -> Change settings -> Modify and ticking the box “Disable client side hardware decoding”. Does this help?
To brokewood, we got your screenshots thanks and we will remove them once this topic has been resolved.
An update to the issue described in this topic:
Depending on the sound card on the Windows host, it might not be possible to mute audio on the NoMachine server side. If the Windows audio driver doesn’t provide functionalities like ‘mute control’, the WASAPI loopback capture can intercept only silence, when the server is muted.
Unfortunately there is no way to workaround this behaviour, but it’s possible to install and use the NoMachine Virtual Audio Adapter (NXVAC). On recent Windows versions like Windows 10 and 11, NoMachine installs only the Microphone Adapter, but it’s still possible to install the Audio Adapter manually.
More details here:
Muting audio on the server side on Windows 10 and 11
https://www.nomachine.com/AR04T01159This was fixed in the 7.9.2 update https://knowledgebase.nomachine.com/SU03T00231.
This looks like you might have installed the wrong package for your device.
For Raspberry see the installation notes that we link from the download page here: https://knowledgebase.nomachine.com/AR07N00896. For other ARM devices see here: https://knowledgebase.nomachine.com/AR03M00842
The package you select depends on the architecture of your device. To check this, open a terminal on your device and run the uname -m command. Some examples:
armv6l – means that you should useARMv6 packages
armv7l – means that you should use ARMv7 packages
aarch64 – means that you should use ARMv8 packagesSo in your case I would:
1) uninstall with
sudo /usr/NX/scripts/setup/nxserver --uninstall sudo rm -rf /usr/NX/ /etc/NX/ /var/NX .nx2) Check architecture using:
uname -m3) Download and install the correct package.
Thanks for posting that.
We have an article that would be useful in this case:
How to handle possible conflicts between NoMachine USB module and third party drivers
https://knowledgebase.nomachine.com/AR04Q01027I switch to a new wifiDo you mean completely separate network i.e you are at home and you are connecting to your work’s computer in the office?
Are you using the correct (public) IP address of your work’s computer? If you are connecting from an external network to your work’s computer, you will most likely need to configure port-forwarding on the router there. Take a look at the following article:
How to connect over the internet to NoMachine behind a NAT router
https://knowledgebase.nomachine.com/AR10R01099In the meantime change VirtualDesktopMode 0 -> VirtualDesktopMode 2 as per my previous suggestion. I also noticed you’ve changed PhysicalDesktopMode to 0. Setting it to 0 means that access is in view-only. So change:
VirtualDesktopMode 0 -> VirtualDesktopMode 2 and
PhysicalDesktopMode 0 -> PhysicalDesktopMode 2
User1’ is running a desktop ‘U1D1’
I want another ‘person’ to connect 2nd session with same ‘User1’ to the same virtual desktop U1D1 in full collaborative mode. Is it possible or does he have to be another user2, user3 ?Thanks for clarifying. Yes, it is possible, you don’t need a second username to be able to connect and interact. Once session migration has been disabled, this is the way it works. We checked on the fly just to make sure that Workstation for Debian is working out of the box, which it is. The only setting we changed is the automigrate key. To enforce it, you can remove the #. So we have in server.cfg
ConnectPolicy autocreate=1,autoconnect=1,automigrate=0,desktop=0,dialog=0,xsessions=0,udp=1
We were able to connect to the same desktop in two separate sessions as the same user and both users can interact. Maybe you inadvertently changed something else in the server.cfg file?
Check this key in the server.cfg: ‘VirtualDesktopMode’ ? It should be set to 2, which is the default setting.
If that does not work, send us your server.cfg so we can take a look.