Forum Replies Created
-
Posts
-
If necessary yes, but you’ll have to upload it to a service from which we can download it because it won’t pass our email server.
For your issue, we’d like to see the stack of the nxplayer and also NoMachine logs as well.
For any core files generated by nxplayer, please see https://kb.nomachine.com/AR09L00810.
For the NoMachine logs, on the device you are connecting from:
– launch the NoMachine UI on the user’s computer from Programs or Menu
– click on Settings -> Player -> Security
– check Don’t delete log files on exit option
– Connect to the server and reproduce the problem.
– Compress the user’s home/.nx directory containing logs.
– Send the compressed logs archive to NoMachine Support Team by e-mail.On the server side, please see: https://kb.nomachine.com/DT07S00244#1.1
And then the journalctl from the server side as well.
Also, is your Debian installation in a VM? We have not been able to reproduce any similar behaviour on our Bullseye test set-up.
ikfredje,
your issue us on the player side, so it’s best to deal with the problem in another topic.
I see that you have opened a separate topic https://forum.nomachine.com/topic/client-on-debian-bullseye-aborts-on-connect, so I’ve linked it here.
So these Linux Mint can just click on Firefox and log in on a UDS page.
Do the users download a connection file which the browser then opens using NoMachine client?
In the Windows computer you want to access, when prompted, you must insert the username and password that you usually use to log in to that computer, the same account you would use if sitting in front of it. It can be any of the formats here:
https://www.nomachine.com/AR03S01118
Pin numbers are not accepted.
Quoting from the article: Because of Windows policies, the password cannot be empty when connecting by remote. The PIN cannot be used as well. It’s necessary to set a password for entering by remote.
To do that (on Windows 10):
– Click the Start button -> Settings
– Click Settings
– Select Accounts -> Sign-in and create a Password for your account.Thanks for reporting this on Debian Unstable. Can you please try a different distro, one of those that we officially support, and tell us if you have the same issue? We are not able to reproduce it.
Hi,
The first thing is to understand if we’re speaking of machine sleep (stand-by) or display sleep. With display sleep, we don’t want to prevent the display from sleeping, but it has to be possible to wake up the display as soon as there is an event (keys or clicks) in the NoMachine session.
Machine sleep is another story and depends on the system settings.
What do you mean when you write ‘nomachine shows it’s dead’. What is the pre-sleep screen? Can you show us a screenshot?
What is the OS of the remote machine. You posted in Linux so I assume the server side is Linux, but what distro is it?
Does the machine have a physical monitor attached?
The only was to reconnect is to physically touch the server’s keyboard – not always possible.
Not always possible -> I am assuming that you mean that you can’t be physically in front of the server every time it happens in order to touch the server’s keyboard? And you confirm that touching the keyboard or moving the mouse in the session window from the client side has no effect whatsoever?
Hi, thanks for your feedback! 🙂
The ability to open multiple windows is definitely something we want to offer. Now that the huge work behind getting v8 desktop and mobile is done and that’s two major milestones out the way, we can plan to start work multi-windows on iPad soon.
Hi, the logs didn’t show anything strange occurring. Can you also send us the system logs (journalctl)? These would be useful. How about the workaround I suggested in my earlier reply. Have you tried that since submitting the logs?
Hi, is the desktop running in a VM or on a physical machine? Can you also tell us the specific graphic card and what drivers are installed (i. are they proprietary drivers?)
I sent you an email requesting output (for the file that didn’t attach, I am not sure if was a txt file or an image), anyway, we no longer need it.
The problem you are encountering is known. There is an API on Mac that the player (but also the agent, when the Mac is on server side) calls to detect if the keyboard is ISO or ANSI. These two keyboard types only differ in one key, the one that you report that is not working.
In some cases we observed that this API reports the wrong information. We are currently investigating possible solutions.
Can you tell us the exact keyboard model you are using on the Mac client-side?This is unrelated to the iPad but most likely a question of missing permissions on the MacBook side. I’ve moved your topic to the NoMachine for Mac section.
Please take a look at my reply to a similar topic:
The session file, or connection file as it is also called, is on the client side, the device you are connecting from. More details about how to locate it are here:
https://kb.nomachine.com/DT11R00186#3
You can check this yourself by opening the NoMachine Player, going to Player -> Settings -> Folders.
Did you try what I suggested and create and connect with a new connection for that user?