Forum Replies Created
-
Posts
-
We reproduced the issue in our labs and it will be fixed in the next release. Thanks for reporting!
You probably mean this feature: https://knowledgebase.nomachine.com/FR12K02799. This is already implemented, but only in virtual desktops, that are available in the NoMachine Terminal Server product line (e.g. NoMachine Workstation). When connecting to a physical desktop, you are limited by the number of monitors actually present on the server.
It’s a bit strange that disabling the pointer grab can have an effect on this issue. Would you double check?
Please also try to check the ‘Show remote cursor pointer’ option. Now you should see two cursors in the session, the local one and the remote one. Do they both look large or just one of them? Which one?
Hi Mark,
server side logs look clean, so I would need some more information. Is the Linux machine on the login screen when you connect to it? Is it headless (no monitor attached or turned off)? In case it is headless, can you try to attach a monitor and check?
Hi mjordam,
at that stage the OS is asking all applications to terminate now, including NoMachine. It looks like some other application is misbehaving here, not NoMachine. I don’t know if any trick would be possible to allow NoMachine wait for all other applications, but I’m afraid it wouldn’t feel right.
Thank you for the files, they help to narrow possible causes down. Would you be willing now to install a debug package and collect some logs for us?
Hi,
in the meanwhile we reproduced something similar in our labs, but we would need a confirmation. Do you have the possibility to physically look at the server monitor while reproducing the slowness in the NoMachine session? Is the monitor in stand-by mode?
Sorry for the delay. Probably we managed to reproduce this issue in our labs, but we would need a confirmation. Do you have the possibility to physically look at the server monitor while reproducing the slowness in the NoMachine session? Is the monitor in stand-by mode?
Sorry for the delay, still not able to reproduce it here. Anyway your last findings gave some food for thoughts, but we would need a confirmation. Please use the ‘Take a screenshot’ button in the Connection panel of the session menu. Take a screenshot with ‘Show remote cursor pointer’ off and again with this option turned on, and see how many cursors are shown in the image and their size. Then, if you are available to do so, you can use session recording to record the NoMachine session (Recording panel of the session menu). Again, see how many cursors and size. You can share the screenshots and the recording file here, if you wish.
Thank you in advance 🙂
Hi,
we can’t reproduce the issue with black screen in our labs. To start an investigation, we would need server side logs. You can find instructions in https://knowledgebase.nomachine.com/DT11R00182#1 and you can send them to forum[at]nomachine[dot]com. Collect them while reproducing the black screen.
From further descriptions provided by the both of you, it looks like the issue that you are reproducing is not the same we reproduced in our labs (that anyway only affects the initial cursor size, as changing the cursor shape would fix it immediately). So please let us know:
– What happens when you drag the cursor (move the mouse while the left button is pressed)? No matter where you do that, it can be on the desktop. Do you still see two cursors, the huge one and the normal one?
– What happens if you enable the ‘Show remote cursor pointer’ option in the Input menu? Do you still see the same two cursors?
– Could you record a video of your screen showing the problem?
We are reproducing something similar to the “huge cursor” issue in our labs and we can send you a possible fix as soon as it is ready, if you are willing to give it a try. In the meanwhile, can you confirm that the cursor goes back to the normal size as soon as you force it to change its shape (for example by hovering on a window’s corner to change it to the ‘resize’ shape)?
We can’t reproduce the issue with the “double cursor” (local and remote cursor both visible). Does leaving the lid open have any effect on this problem?
Hi,
Primarily inconsistent latency, regardless of where I connect from, being on my local network or remotely through cellular or wifi, latency seems to spike or the connection seems to stall. This is especially evident when I am typing as many times it will just miss characters. I have tried different encoding and turning the different hardware encoding and acceleration on and off to no avail.
This looks like an issue with your network. You say this occurs also in the local network. Does it mean that you have these problems even if both the client and the server are connected through an Ethernet cable?
Next I seem unable to switch users, I have two users on my computer that I constantly switch between and more often than not after logging out of the first or initiating fast user switching, if I don’t type the next account password fast enough the connection stalls and the display turns black, unable to switch users or reconnect.
To investigate this issue, we would need debug logs. Please follow the instructions in https://knowledgebase.nomachine.com/DT11R00182. You can send them to forum[at]nomachine[dot]com, referencing this topic.
Also if my computer is asleep I seem unable to wake it for a remote connection, something I never had issues with when using other Remote Desktop software.
If you connect from LAN, you can try to enable the ‘Wake up the indicated server on the LAN if powered off’ (Wake on LAN) option by editing the connection file, Configuration tab. This should solve the problem. Do you connect from LAN with the other Remote Desktop software?
Finally if I restart my computer it appears the server never starts prior to me logging in. Now maybe this is a limitation with the Mac version, but again, never had this issue with other Remote Desktop software.
We would need debug logs also for this case.
Hi,
sorry for the delay. Logs don’t point to any specific issue. To rule out any driver issue, please try and disable hardware encoding on the server:
1)Â Edit the node configuration file, /usr/NX/etc/node.cfg
2) Uncomment and disable the EnableHardwareEncoding key:
EnableHardwareEncoding 0Hi Michael,
just a guess: did you try to check the ‘Disable frame buffering on decoding’ option in the session menu panel, Display settings (on the Mac)? By default, when there is no local input, NoMachine assumes that there is no user interaction with the desktop and starts buffering few frames on playback.