Forum Replies Created
-
Posts
-
Hi, we are regular users of Proxmox in our labs and we have not come across disconnects as you’ve described.
When you connect from other client machines, do you see an error message of some sort? Can you show us the dialog that you see when you get disconnected?
Can you send us the logs of the client and server sides? See the following article for further instructions: https://kb.nomachine.com/DT11R00181.
You can submit them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
They didn’t reveal anything useful either.
So to sum up: the NoMachine logs don’t show anything strange (just a couple of restarts) and the system logs didn’t show anything that could suggest reasons for a crash.
So, either the problem is not there or the logs are not catching it.
All we can suggest is that you keep debug enabled and then should the issue occur, you should collect the logs and then send them in (nomachine player and server, as well as system logs).
A feature is planned which will allow multi-monitors on the server side to be treated as separate windows on the client side. In each of theses separate windows it will be possible to apply all the usual settings, like applying a different scaling factor, resizing the window to any size and placing the window in any desired location. It comes close to what you would like to achieve, in that n in your case, you could keep 2 monitor windows open whilst minimizing the third one.
Unfortunately, we cannot give a definitive ETA. Development priorities are currently on NoMachine Network (www.nomachine.com/network) and v9. Work on the feature you are interested in may start after that.
Can you show us a screenshot of the “Edit connection” panel and the options you have available in the Host field?
What actually happens when you try connecting the IPv6 address? What is the error dialog you receive/see when attempting to connect with the IPv6 address?
Please open a new topic with specific steps of what the problem is. Can you connect? Do you see the desktop and interact with your remote desktop? Open a new topic with details of your client and server set up and any relevant screenshots. Thank you.
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?
Mubasher, your problem seems to be a different one given that you reach the login screen and then access your desktop. I suggest you open a new topic with clear steps on how your reproduce the problem. Screenshots illustrating the problem will be useful.
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 has 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?