Forum Replies Created
-
Posts
-
Can you check if home directory of user exists on the system which you want to connect (user “idempiere” in your case)? If not – please create it with correct permissions. If it exists, enable debug and send logs to forum[at]nomachine[dot]com. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098
Which Desktop Environment do you use on that server? Can you try “Create a new virtual desktop” (not “Create a new custom session”) and check that it works?
Node keys DefaultDesktopCommand and DefaultXCommand are responsible for starting -in sequence – a new virtual desktop and default X client script.
Can you paste here the output of the command:
grep -E “DefaultDesktopCommand|DefaultXCommand” /usr/NX/etc/node.cfg
Are you sure that you have 32-bit system? We recommend you install dedicated version on 64-bit systems. Please try the ‘nomachine_5.3.9_6_amd64.deb’ package. Before installing remove completely the previous version (sudo dpkg –purge nomachine && sudo rm -rf /usr/NX /etc/NX /var/NX).
To increase the download speed you can navigate to NoMachine main menu inside the session (Ctrl+Alt+0) -> “Display” -> “Change settings” and move the slide in the “Quality” section to maximum.
Are you sure that you forwarded the correct port in your router settings? Second thing – after changing the NX port, it’s necessary to restart nxserver. If you restarted right after changes, please restart it again and check connection. You can do it from nxclient monitor – click on NoMachine icon in the tray – navigate to “Show the server status” and press “Restart the server” button.
We didn’t notice the clear difference in cases with just installed pavucontrol on similar machines. Can you send some recording with your issue to forum[at]nomachine[dot]com?
Problem is known. It should be fixed in next software update which should be in a few days. Possible workaround you can find there: https://www.nomachine.com/TR02O07604. Please use the notify me tool to know when a fix is available (i.e when we’ve released).
Disabling the anti-virus shouldn’t be necessary.
Did you reboot Windows after installing NoMachine? It’s necessary for proper operation of the nxserver.
NoMachine server processes need about 20 seconds for start on Raspberry Pi 3 with Ubuntu Mate 16.04. We couldn’t reproduce problem on the same environment (Ubuntu Mate 16.04, armv7, Raspberry Pi ver. 3, SD card class speed: 10).
Can you send system (`/var/log/syslog`) and NoMachine logs to forum[at]nomachine[dot]com? Please enable debug, restart nxserver (`sudo /usr/NX/bin/nxserver –restart`) before you reproduce problem. Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098#1.
You said that your application works locally – do you mean that it works on the odroid when you’re physically ON the odroid and you see the app on the TFT monitor? If you use NoMachine, are you connected to the same desktop which you see on the TFT?
Generally, when installing NoMachine (free) it looks for an X server and if it cannot find one NoMachine Player shows “Cannot detect any display. Do you want NoMachine to create a new display and proceed to connect to the desktop?”. After accepting it will create a new display.
Do you see this message?
It is possible that you need to set or export DISPLAY value to start your app.
After you’ve removed NoMachine “Programs and Features” and rebooted the machine (like indicated in the “Installation Guide” https://www.nomachine.com/DT07M00078#2.3.) remove directories related to nxplayer configurations i.e., .nx (in default: C:/Users/<username>/.nx) and to connection files of NoMachine (default path: C:/Users/<username>/Documents/NoMachine).
Despite hard efforts we weren’t able to reproduce such problem. Can you enable debug and restart nxserver (sudo /usr/NX/bin/nxserver –restart)? After that check again if external IP and port shows in the welcome screen with enabled firewall.
If you can still reproduce issue check it also in –upnpstatus command output (sudo /usr/NX/bin/nxserver –upnpstatus). If not – please collect logs from server side and send them to forum[at]nomachine[dot]com. Send also file with SuSEfirewall2 configuration (sudo SuSEfirewall2 status > /tmp/output_of_susefirewall2.txt).
Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT07M00098#1.
It’s up to the user to perform system authentication if a login screen is displayed.
As for the disabling of permission request, navigate to the Show the server status on the NoMachine tray icon -> Server Preferences –> Security –> and uncheck option: “Require permission to let remote users connect”
More info you can find there: https://www.nomachine.com/AR04K00663.
Thank you for the report. We were able to reproduce problem in our labs. The issue has been queued up for fixing. Please follow this trouble report: https://www.nomachine.com/TR05O07729 and check the “notify me” box to know when a fix is available.