graywolf

[graywolf]

Thanks for reporting. You can expect a stable fix in the next update.

[graywolf]

Does the workaround in TR08S10329 fix the issue?

[graywolf]

Do you have to reboot the server? Restarting Xfce would be enough.

I cannot say that is a problem with NoMachine, maybe some stale grab from an application or for Xfce window manager.

[graywolf]

It looks you have some application probing display :1001, repeatedly, one time per second. Is it possible?

 

[graywolf]

Please collect the server logs with sudo /etc/NX/nxserver --debug --collect. Send the created log archive to forum (at) nomachine (dot) com.

[graywolf]

Please go to the server menu, Performance tab, and deselect “Use hardware encoder” and “Use acceleration for display processing”.

In the client menu, deselect “Grab the keyboard input” and “Grab the mouse input”.

Restart the server. Any changes?

[graywolf]

Hello. Is it possible that screen image is frozen? I mean: mouse and keyboard event are correctly forwarded to the Linux host that reacts accordingly but you don’t see anything in the client window.

Is a monitor screen attached to the Linux host when you try to connect to it from remote?

 

[graywolf]

Hello.

1. Has your Window 10 got any system update recently?

2. Please use the Linux NoMachine client to connect to the Windows host and press/release all modifier keys (Alt, Shift, Ctrl) one by one. Are keyboard/mouse input still blocked after that?

3. Run a command prompt on the Windows 10 host. Change dir to the installation path and run nxserver command to collect logs, i.e.:

cd %ProgramFiles(x86)%\NoMachine\bin

nxserver --debug --collect

Send the log to forum (at) nomachine (dot) com

4. Try to restart NoMachine service, and see if anything changed, i.e.:

cd %ProgramFiles(x86)%\NoMachine\bin

nxserver --restart

 

[graywolf]

Hello, otlichnik73.

It looks you got an issue with a headless server host. You would find this useful: How to solve black screen on Linux headless machines

[graywolf]

Would you try this:

1. Run a remote shell and connect to the macOS system

2. Use sudo to gain admin rights: sudo -i

3. Run these commands to unload NoMachine agents:

launchctl unload -wF /Library/LaunchDaemons/com.nomachine.server.plist

launchctl unload -wF -S LoginWindow /Library/LaunchAgents/com.nomachine.localnxserver.plist

4. Run these commands to reload:

launchctl load -wF /Library/LaunchDaemons/com.nomachine.server.plist

launchctl load -wF -S LoginWindow /Library/LaunchAgents/com.nomachine.localnxserver.plist

5. Restart nxserver:

/etc/NX/nxserver --restart

[graywolf]

Would you tell me whether the problem arises connecting to a physical or a virtual display?
Did you notice if remote desktop is actually updating (e.g. clock changes after a minute).
Would you collect the server logs and send to forum (at) nomachine (dot) com?

[graywolf]

Please uncheck the permission box in system preferences, then re-enable it. Let me know if it is effective.

[graywolf]

Hello. RDP leverages a virtual display driver to move the user session into a virtual screen which resolution can be undetermined. NoMachine captures the content of the physical screen, so user session keeps using a full-featured video hardware that impose resolution among a finite set of modes.

[graywolf]

why is MS RDP able to login immediately to the server desktop, whereas NoMachine connection requires entering the pw twice?

That would be a new feature. At the present moment it isn’t possible to do it.

[graywolf]

I think the Windows login screen defaults to English layout. You could copy your user settings to the login screen using the Windows control panel (see picture).

NoMachine always let user specify the proper account/credential to pass the Winlogon stage, without automatic forwarding of password strings.

Attachments:

1. 

   2021-07-02-154302.png
   

[Author]

Posts