Forum Replies Created
-
Posts
-
See here:
How to check which version of NoMachine or NX Server you have installed
Now I understand 🙂 So that’s a bug and you can do the following as your workaround:
Edit the configuration file /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg to have:
DisplayServerExtraOptions “-oldeventapi 1”
I checked it and it works. Apple deprecated the old APIs which were used (in NM version 5 and earlier) and released new ones, which were also available in v5 but were disabled by default. From version 6 we enabled the new API as default. But you can still set the old ones by using the workaround above.
@graphixillusion, we need to send you another attachment to try, but emails to you come back to us undelivered.
further analysis showed that mouse clicks look OK. The cause could be a Ctrl or Shift key stuck in the “down” state. Running the attached test tool from command line will help to inspect the state of keys on mouse clicks. Run:
wintest.exe > wintest.txt
do some left clicks, close the wintest window and let us look at
wintest.txt.Can you get in touch?
   it disconnects whoever went first without warning.
This happens because PersonA and PersonB are connecting with the same username to the remote machine (‘session migration’). This is the normal behaviour.
If two people connect to the same remote desktop e.g first PersonA (Mickey) and then PersonB (Minnie), Mickey will see a message “User Minnie is requesting a connection to this desktop…Accept, view only, deny”. And Minnie will see “Waiting for the desktop user to authorize your connection”.
In the case of NoMachine free, Mickey will have to disconnect to let Minne connect because you have one connection to the remote desktop at any time.
If you use Enterprise Desktop, you get unlimited connections to the same desktop. I.e multiple user names can connect. So Mickey won’t have to disconnect.
I can see the screen of the second user on client pc, while I can work on the server pc, but after the update using mouse or keyboard on client’s side affects the server account.
The problem you have is not clear. Please tell us the specific steps to reproduce the issue you have with keyboard and mouse using version 6 which you didn’t have using the earlier version 5.
Thanks.
Check your permissions. It might be you don’t have the right permissions in place to remove that connection file?
Just so I understand the issue you have:
– you have installed NoMachine Workstation version 6 on OpenSUSE
– sometimes you can reconnect, other times you can’t?
– you are running a virtual desktop or custom session with NoMachine?
Please write here the typical steps to reproduce the problem.
Can you force VP8 encoding and see if the problem persists? If you’re still getting a blank screen, it’s not related to codecs, and we’ll need to investigate what’s causing it elsewhere in the software.
p.s the logs you sent still didn’t include the affected session directory.
I’ve added an article that explains what to do for both users and administrators 🙂
How to disable or re-enable Welcome panels shown at session startup
https://www.nomachine.com/AR11O00951Hi, Welcome panels appearing before the connection starts (i.e. the panel which publishes the local IP address of the computer and the connection wizard) can be re-enabled by using the “Restore default settings” button in the Settings panel of the client User Interface.
Welcome panels appearing when the connection to the desktop has been established, can be restored by checking the “Reset saved preferences and password” box while editing the corresponding connection setting.
See the images below.
The logs you submitted are from the server component of the connecting Linux client. What we need is the server logs from the Windows host that you are connecting to. Enable debug there, connect from your Linux client to reproduce the behaviour, and then gather up the logs, again following the instructions from the article in the KB).
Logs were already sent to that email…
The logs you sent for the other issue don’t actually contain information useful to Fra81. That doesn’t mean there is no info useful for the other topic though 🙂
What you need to ensure is that you enable debug and that you establish the connection. The logs you submitted earlier don’t show the server running, so there is no connection at all.
