Forum Replies Created
-
AuthorPosts
-
graywolfParticipant
It looks you have some application probing display :1001, repeatedly, one time per second. Is it possible?
graywolfParticipantPlease collect the server logs with
sudo /etc/NX/nxserver --debug --collect
. Send the created log archive to forum (at) nomachine (dot) com.August 25, 2021 at 15:26 in reply to: Can’t control mouse and keyboard (Windows server, multiple clients) #34989graywolfParticipantPlease 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?
graywolfParticipantHello. 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?
August 19, 2021 at 14:00 in reply to: Can’t control mouse and keyboard (Windows server, multiple clients) #34912graywolfParticipantHello.
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
graywolfParticipantHello, 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
graywolfParticipantWould 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
graywolfParticipantWould 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?graywolfParticipantPlease uncheck the permission box in system preferences, then re-enable it. Let me know if it is effective.
July 9, 2021 at 11:24 in reply to: Higher screen resolution without scaling Windows (server) & Mint (client) #34389graywolfParticipantHello. 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.
graywolfParticipantwhy 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.
graywolfParticipantI 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:
July 2, 2021 at 09:37 in reply to: NM crashing with error: Display failure detected on display #34295graywolfParticipantWindows placed at 0,0 should not cause any harm. It is a valid position for a window like any other. Have you got any sample program to reproduce such problem? Or would you name the software you are using? If it is in-house software, would you tell me which graphical library it is built on?
You could send such information to forum (at) nomachine.com if you prefer.July 1, 2021 at 15:13 in reply to: NM crashing with error: Display failure detected on display #34275graywolfParticipantHello. Is it a well know application? I’d like to reproduce that problem.
graywolfParticipantWe need to know if grabbing is not working properly. Please run xev on Ubuntu and check if KeyPress/KeyRelease events are logged when Ctrl and Shift are pressed together.
-
AuthorPosts