Forum Replies Created
-
Posts
-
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.
The forums are open to everyone and are monitored by our developers in the time they have between handling support tickets coming from subscribed customers and their own development work. If you don’t provide all the information we need, it slows down the process of finding a solution (if the problem is indeed a NoMachine issue).
Our developers need as much information as possible from you in order to be able investigate as I have mentioned several times in your other posts that I have replied to. If you are the administrator submit the logs from the server side, not just the client side. Seeing these will allow us to check what the potential problem is and if it is known to us (the Trouble Reports section of the Knowledge Base shows all the current bugs and whether fixes are available and in which version).
Please understand that the forums are handled by the developers as quickly as possible given their commitments – if you have a valid subscription with us, you should consider opening a support ticket in the customer area so that your issue can be investigated according to your entitlements, and to avoid sensitive information being made public. If you wish to continue discussing possible solutions here, that’s fine as well, but please submit the logs and answer the following:
Client machines are running with Windows 7/10.
Are you unable to reconnect the session regardless of the connecting client? I.e you’ve tried from Win 7 and Win 10 to reconnect but without success? What’s the NoMachine version of the client?
What’s the remote desktop environment? On what distro? It would help to know more a little more about your environment. Also what client OS and what version of the NoMachine (Enterprise?) Client are you connecting with?
Are you the administrator of this server? If so, you’ll need to submit the server-side logs as per the instructions
If you are not the administrator, please contact them and ask them to open a ticket in the support center on your behalf or contact us via the website. Instructions for enabling debug and submitting logs are here: https://www.nomachine.com/DT07M00098
Do not paste them here. Send directly to forum[at]nomachine[dot]com.
We have opened a Trouble Report https://www.nomachine.com/TR11O08272 and there is a workaround available.
Please use the ‘notify me’ tool to receive a notification from us when the fix has been released.
