omgzwhitepeople

[omgzwhitepeople]

@Britgirl, any update on this?

[omgzwhitepeople]

Exciting! I should warn, I am not 100% convinced the ending of sessions is triggered ONLY by clipboard access. I think there have been other key combinations that have caused it too, not sure what they are though.

[omgzwhitepeople]

@Britgirl, I zipped everything in NoMachine/var/log from the client and sent it over. Let me know if you need anything else.

[omgzwhitepeople]

Hey, sorry for delay on this. I have gathered the server logs and sent to the email address you shared. Let me know if you need any other types of logs or for me to reproduce the problem.

I was able to regenerate the problem (kind of). It seems to happen when I do a combination of click between session 1 session 2 and my clients hosts and/or use clipboard. At some point one of the client sessions with just end abruptly, with no error message.

 

[omgzwhitepeople]

Client: Windows 10 Pro (systeminfo version: 10.0.19044 N/A Build 19044 ) — NoMachine version — 8.4.2 free
Server: Windows 11 Enterprise (systeminfo version: 10.0.22000 N/A Build 22000 ) — NoMachine version — 8.4.2 Enterprise desktop

Hmm after more testing, the different connections do connect to the correct monitor, I guess I was not testing properly before. Thanks for the tip!

[omgzwhitepeople]

@Britgirl, thanks for the details, looking forward to the feature implementation.

I did find a work around based off the link you shared. I actually found the link yesterday after posting. For now I do the following.
1) Connect one session to the host, and select monitor1
2) Connect second session to host, and select monitor2

This works with Enterprise Desktop. However it does not seem as stable as I would want it to be. The main problem I am running into right now, is randomly a session window will just crash / close. No Error to reconnect, no error message box, just disappears. Then I am forced to reopen the session and select the monitor I want. I never had this issue when just connecting one session.

I tried the following troubleshooting:
1) made sure I was using ethernet not wireless. Be aware I am connecting inside of the same LAN.
2) tried rebooting the client and server.

Is it expected that that connections would disconnect like this? Is this a known bug? Any recommendations to troubleshoot more, or fix this issue?

 

[omgzwhitepeople]

Thanks @Britgirl. But it sounds like there is no way for a connection to remember to use “monitor 2”. I literally need to login, then use the hot key to switch each time, is that correct?

[Author]

Posts