Forum Replies Created
-
Posts
-
If the problem occurs when you are connecting to server 3.5.0, you need to contact the team via the website. The forums only deal with version 4 on server and client.
Hi everyone, there is a Trouble Report open on this: https://www.nomachine.com/TR08L04502
You can sign up for notification of its fix.
Do any of these posts help?
https://www.nomachine.com/forums/topic/error-is-138-connection-timed-out#post-4339
https://www.nomachine.com/forums/topic/cannot-connect-to-server
Are you able to connect from the PC (the desktop you were trying to reach) to the first laptop?
Hello, I see that you fixed the keyboard issue. Just so it’s clear. If you are running the free version of NoMachine, so you are attaching to the physical display, the keyboard you get will be the one on the remote server. This allows the user to simply change the keyboard layout by selecting the keyboard in the control panel of the desktop environment, as you did. The keyboard on your Ubuntu server must have been set to US.
If previously you were using one of the terminal server products, then when running a session, it is the client keyboard which is ‘passed’ to the virtual desktop. (Local German -> Remote German) Just so you know, in version 4 the keycodes are sent by the client untranslated and the translation happens inside the target X server, according to the keymap selected by the user. So in your case, a local German keyboard will mean you get a remote German keyboard, unless of course you configure it differently.
….the screen hot corners which I use to switch between desktops no longer work.
A TR has been opened: https://www.nomachine.com/TR08L04502
You can submit your email address to know when the fix has been released.
@fdelpin, did you manage to create a new connection with the wizard?
This thread will be closed. I understand that the developers are investigating possible ways to improve the page-peel.
Please make sure you have updated both client and server installations to the latest version, and tell us if you are still having problems.
Just to update everyone. We are aware of problems with Tegra2 devices and are investigating how we can overcome the technical issues. For now, we have to say that NoMachine on Tegra2 is not supported. I will close this thread. Feel free to open a new topic.
I know that the core developers are working on this (it’s a known problem). A temporary workaround is to connect an additional usb mouse
and share it to the remote side as a USB device. Nice to know that you play games with NoMachine 😉We will need logs in order to see what’s happening. Please follow the guidelines in the article here and submit to issues[at]nomachine[dot]com