Forum Replies Created
-
Posts
-
Did you already look at and follow the instructions: https://www.nomachine.com/accessing-your-remote-desktop-on-google-cloud-platform-via-nomachine
We aren’t ware of any problems with audio in RPi4 sessions.
Are those fresh changes in the config.txt? You need to remember that the machine needs to be rebooted for changes to take effect.
What is your Raspbian version and architecture? Did you install pulseaudio by yourself or it was installed by default? With what output devices do you have a problem – is it headphones/speakers pluged with jack or usb, or maybe is that hdmi output? Please connect to the session with NoMachine and execute commands in the terminal
pactl list sinks >> /tmp/sinks.txtandpactl info | grep Default >> /tmp/sinks.txtthen attach /tmp/sinks.txt file here.We weren’t able to reproduce this problem on pop!os. Can you try to connect to physical session (with NoMachine) to that machine when you encounter the issue you are reporting? Does that session work ok? It could be that the desktop environment is actually failing. Are there any .xsession-errors file in the home directory?
In your picture, hit “back” and you will have the possibility to change My desktops to All desktops.
When a user authenticates and he doesn’t have any owned desktop sessions, the next step is to prompt the user to start one. Hitting “back” will allow to visualize All desktops label.
Please take a look at the attached screenshot. You need to enable the selected option on window with sessions to see other users’ sessions. To define a pool user who can connect without explicit permissions, keep the authorization request on (VirtualDesktopAuthorization 1) and give to the user ‘trusted’ permissions:
sudo /etc/NX/nxserver --useradd USERNAME --trusted virtualYou can find more information here: https://www.nomachine.com/DT03O00126#12.3
Attachments:
For LXQt please set:
DefaultDesktopCommand "/usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startlxqt"Output shows that there NoMachine was installed already. Did that previous installation work? Maybe indeed you have arm64 architecture but NoMachine armv7 package was installed already 🙂
To avoid further confusion, please uninstall NoMachine (
sudo dpkg --purge nomachine && sudo rm -rf /usr/NX). Check architecture (uname -afor example), download correct version and install it.First two points are clear.
Point 3)
I tried port forwarding and tried all the other things in the similar post and all combinations thereof – commenting out and port forward settings in router, leaving uncommented and setting port forward in router, etc. etc. I know port forwarding works as I successfully use it for other applications.
Port Forwarding rules won’t display in the command –upnpstatus output or on “Welcome windows” in the NoMachine Player, but a connection should still be possible. Please try to connect using Public IP and port 4000 if you have configured port forwarding rules on the router.
Point 4)
What does that exactly mean? How do I reserve? As I wrote, I have a dynamic public IP provided by my ISP that has stayed the same for years.
When I wrote “reserve IP on the router for your Windows machine” I wasn’t referring to the public IP. I meant the local IP of your Windows machine, and it’s for the port-forwarding rules on your router. Port Forwarding will work if you open port for the defined local IP. If on Windows there is no static IP, the local IP can change and you will lose the possibility to connect there.
Which version NoMachine version do you have installed? Is the machine was rebooted after installation? Did you tried to connect there from the local network?
Please check if EnableUPnP in server.cfg is uncommented and set to NX:
EnableUPnP NXYou can try also Port Forwarding to connect from outside local network. There is a lot instruncions for your router model (https://portforward.com/d-link/amplifi-dir-645/ https://openmyip.com/DLink-Amplifi-DIR-645-router-setup). Reserve IP for your Windows machine, and then set Port Forwarding for that IP with TCP and UDP port 4000.
We don’t seem to be any closer to helping you resolve your issue. Our test environment on AWS shows that there are no issues with connecting to OpenSuse (this is what you said you are connecting to). Setting the DefaultDesktopCommand key to “startxfce4” works as expected.
What we suggest is that you uninstall NoMachine (and remove config files
sudo rm -rf /usr/NX) on the remote Amazon instance and reinstall NoMachine to reverse any changes. Then check the DefaultDesktopCommand again and reset it to “startxfce4”, if it’s different. Then restart NoMachine server to make sure that changes are implemented (sudo /usr/NX/bin/nxserver --restart).Also, the logs from the server side, not the connecting client, would be useful at this stage if, after the reinstall, you continue to have problems.
To get the logs from the server host, follow the instructions here:Â https://www.nomachine.com/DT10O00162
We have not encountered such a problem on the same system OS and KDE Plasma version. Did you uninstall 32-bit NoMachine and remove /usr/NX directory? If not please try remove and install 64-bit version again.
If problem still appears please look for above mentioned logs.
This shows that you could be using XFCE but I asked you to check what is actually set in the DefaultDesktopCommand key in the /usr/NX/etc/node.cfg on the server side.
What is written there?
For example, it should be:
DefaultDesktopCommand /usr/bin/startxfce4that you could create a XFCE session.
Like I suggested before (maybe you didn’t see it) you need to check the DefaultDesktopCommand in the /usr/NX/etc/node.cfg (on server side). It should be set:
DefaultDesktopCommand /usr/bin/startxfce4If there is other value please modify it. Then it should start to work.
The server has the same user and password (network password).
Did you mean that it is network user? If yes, use these instructions: https://www.nomachine.com/AR08M00857.
