Britgirl

[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 🙂

[Britgirl]

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.

[Britgirl]

and now the second session connects well… however, only read-only mode. I can’t click or do any action on the second session connected to the virtual desktop.

Do you mean that ‘user 2’ connects to the same desktop as ‘user 1’ but user 2 is is read-only mode? Did you user 1, the owner, accept the connection in interactive mode? (as explained in the article above https://knowledgebase.nomachine.com/AR07P00993)

Or do you mean that ‘user 2’ can connect to their own virtual desktop but it is in read-only mode?

[Britgirl]

When connecting to the physical desktop which doesn’t have an X server running (e.g. it’s a headless machine), NoMachine is able to use its own display service (that is an embedded X server) to let users connect seamlessly to a physical desktop running in the background on the remote machine. In that case, the display variable 1001, for example, is created by NoMachine.

Display 0 or 1 is created by the native X server. When NoMachine can’t find it or access it, it asks if you want it to create one for you. Does it not ask?

Why NoMachine is not finding the X server or can’t access it is difficult to say. I’m assuming you are using the latest version of Enterprise Desktop on your server. You haven’t mentioned the distribution and version, nor what desktop environment is running there. You could try enabling debug and reproducing the problem. When you do, share the logs and we’ll take a look.

[Britgirl]

We didn’t reproduce issues on iOS with keyboard layouts, but we did notice that the swapped keys that you reported occurred when the iOS device uses an English layout. You should add a German keyboard in Keyboards system settings, and select the Deutsch layout in the popup opened by tapping the small world icon in the virtual keyboard before starting the connection to the desktop.

[Britgirl]

“Ooops! The connection with the server was lost”

We aren’t aware of problems with Bullseye, nor connecting from Samsung S10, so this would need to be checked further. It is probably on the server side, the computer that you are connecting to. Please submit the logs from the Android device using the instructions here: https://knowledgebase.nomachine.com/AR04M00843. You can send them directly to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thank you.

it said that the app was based on an older Android version

The next update will be based on new APIs so the warning message will be resolved.

We’d say that the major iOS and Android update is actually behind schedule. The reason is that the upcoming version 8 for desktop took more time than initially expected. Especially the major features that it will bring with it. The good news is that we plan to release the new version for mobile just after we release version 8 for desktop. The main problem with both the iOS and the Android versions is that we had to update the SDK used, for both. This required more time than expected, especially with the “further interactions” with the user, mandated by “policies”. But again, good news! New versions coming just after version 8 for desktop!

[Britgirl]

Hi, this question has been answered a few times in this forum. Take a look at this topic here: https://forums.nomachine.com/topic/curl-wget-download-urls#post-32477.

[Author]

Posts