Britgirl

[Britgirl]

Apologies for the late response.

Try defining the key as:

UserScriptAfterSessionStart “C:\test.bat”

And the body:

@echo off
mkdir C:\Users\tester\anydir

Bear in mind that custom scripts need to finish within 30 seconds otherwise the session will be terminated. So if you would like to be able to open a program or carry out some kind of activity for longer, you will have to run an application in the background.

[Britgirl]

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 🙂

[Britgirl]

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.

[Britgirl]

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?

[Britgirl]

To Topnotchprincess, submit those attachments from your earlier reply to forum[at]nomachine[dot]com. Thanks

[Britgirl]

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!

[Britgirl]

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?

[Britgirl]

To brokewood, we got your screenshots thanks and we will remove them once this topic has been resolved.

[Britgirl]

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/AR04T01159

[Britgirl]

This was fixed in the 7.9.2 update https://knowledgebase.nomachine.com/SU03T00231.

[Britgirl]

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 packages

So in your case I would:

1) uninstall with

sudo /usr/NX/scripts/setup/nxserver --uninstall
sudo rm -rf /usr/NX/ /etc/NX/ /var/NX .nx

2) Check architecture using:
uname -m

3) Download and install the correct package.

[Britgirl]

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/AR04Q01027

[Britgirl]

I switch to a new wifi

Do 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/AR10R01099

[Britgirl]

In 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

 

[Britgirl]

TomasM, please check your inbox for emails from us 🙂

[Author]

Posts