Forum Replies Created
-
Posts
-
We have created Feature Request, you can find it here: https://www.nomachine.com/FR06P03628. You can sign up to the ‘notify me’ in order to know when it has been implemented.
Unfortunately with custom sessions in the web player there isn’t such an option. The only way is to start a window manager together with application. For example if you want to run xterm and your windows manager is xfwm4 – choose “New desktop” –> “Create a new custom session” –> “Run the following command” and enter command:
xfwm4 & xterm.Do you have the same problem on other applications as well? Does it happen on the physical machine even if NoMachine is not involved?
Please do some tests. Open another terminal in the background and execute command
xinput test-xi2 --root. Then run konsole. Does something show up in the output when you reproduce the problem?Hi,
Apologies for the late reply – we managed to get hold of the board and we carried out quite a few tests.
We were able to reproduce the problem on Ubuntu, but it looks like it’s an issue on Xorg side. We were able also to find a workaround.
You can stop LightDM service (
sudo service lightdm stop), restart nxserver (sudo /usr/NX/bin/nxserver --restart) and then connect to the host.We couldn’t reproduce this problem. But it looks like a system bug to me.
Can you try this fix: https://support.microsoft.com/en-us/help/2328240/event-id-4107-or-event-id-11-is-logged-in-the-application-log-in-windo#bookmark-letmefixitmyselfalways.
Can you send logs to forum[at]nomachine[dot]com? Please tar .nx folder (it’s in the home directory) from client side and /usr/NX/var/log from server side. More instructions about collecting logs are available here: https://www.nomachine.com/DT10O00163#1.
Did you try to connect to that Mac from Ubuntu? Does the connection from iPad to Ubuntu work? Is the latest version of NoMachine installed on each machine?
Please take a look on this article which contains some tips for troubleshooting: https://www.nomachine.com/AR09O00937.
Did you reboot system after installation NoMachine? Please check if nxserver is running (click on NoMachine icon in the system tray -> Show the service status).
Can you zip and send logs from server side to forum[at]nomachine[dot]com? Logs are in %ProgramData%/NoMachine/var/log (you need to be administrator to collect logs). More instructions about collecting logs you can find there: https://www.nomachine.com/DT10O00163.
Is your Debian a headless system? Please send output following commands:
grep CreateDisplay /usr/NX/etc/server.cfggrep DefaultDesktopCommand /usr/NX/etc/node.cfgIf you don’t have a headless system and CreateDisplay key is set to “1”, please edit server.cfg and set key to following value:
CreateDisplay 0
If it’s not the case, please enable debug, restart nxserver (
sudo /usr/NX/bin/nxserver --restart), reproduce problem, collect logs and send them to forum[at]nomachine[dot]com? Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT10O00163.You can change the default port from the NoMachine User Interface in the Server preferences → Network services panel or by editing the server configuration file (namely server.cfg), uncommenting and setting a different value for the NXPort key.
For example:
NXPort 3389After changes nxserver needs to be restarted.
Did you try solutions from similar posts? For example: https://forums.nomachine.com/topic/error-is-138-connection-timed-out-4. You didn’t send much information about the problem (like: which systems are involved? What NoMachine version is installed there? Isn’t there installed some antivirus or non-native firewall? Is that connection inside local network?).
It is possible that firewall is blocking connection, so please also check firewall rules.
We tried to reproduce on the fly but weren’t able to. We would need to know:
– connection to what kind of session shows error? Is it connection to physical desktop, virtual or custom? (if custom – is it terminal or other app?)
– which Ubuntu version did you have before the upgrade?
– did you install NoMachine after the system upgrade?
Can you enable debug (nxserver restart is needed –
sudo /usr/NX/bin/nxserver --restart), reproduce problem, collect logs and send them to forum[at]nomachine[dot]com? Please send also node.cfg file (it’s in /usr/NX/etc/ directory). Instructions about debug and collecting logs you can find there:
https://www.nomachine.com/DT10O00163I have done port forwarding on Router A to Router B’s IP for all ports (20400, 4000, 22, 4022).
It’s not necessary to forward all ports. I can suggest to undo all your changes.
Please check if UPnP is enabled on the router B. On the router A add port forwarding: port 20200 to the router B IP (in your case: 192.168.1.2).
When connecting to the NoMachine Server using for example NoMachine Player, provide external IP, in your case 122.170.23.X and as a Port set the one opened on router A – 20200.
Please also check all firewalls that may be enabled/running on each router and servers involved. If you will still cannot connect to NoMachine Server I would suggest to disable them all and try again.
In Local network – LAN A connected to router A – you should be able to connect to NoMachine Server inside LAN B – connected to router B using IP: 192.168.1.2 and port 20200. If you still cannot connect [ 192.168.1.2 and port 20200 ] in that scenario, that could be reason of not working/disabled UPnP or something blocking connection – like firewall.
First of all changes on the server preferences require system administrator password. There are two easy ways to hide server settings GUI.
1) Hide NoMachine Client monitor on the tray. To do that edit
/usr/NX/etc/node.cfguncomment and setDisplayMonitorIcon 0.
2) Disable server settings GUI. To do that edit node.cfg uncomment and setEnableServerPreferences 0If that’s not enough and you want to prevent non-admin users from accessing any NoMachine settings, changing nxclient.bin rights is a possibility. But if you want to connect to the desktop you need to have original rights on the system. So as a workaround, a solution could be to create a startup script which changes the rights which you have mentioned if the nxclient process has started already.
I’m wondering if I should manually set up both TCP and UDP.
Setting TCP should be enough.
I’ve continually gotten the error message about not being able to map the port.
Could it be a router configuration error? Did you set port 4000? Please check if Firewall isn’t block 4000 port.
Are you able to open ports for other services – for example SSH?