Forum Replies Created
March 29, 2021 at 10:37 in reply to: After remote session freezes and killed, user kept logged without any connection #32647
We received the logs. Thank you! We will investigate and provide some feedback soon.
I’ve sent you the debug package. Please check your inbox 🙂
I’ve sent you the program to download with instructions. Check your inbox 🙂
Unfortunately, the logs you submitted didn’t help us. We would like to send you a debug package and extract the logs again (after you’ve reproduced the problem). Would this be ok for you?
Since the user’s db is enabled, it is in use.
To check current users inside you can use
To delete you can use
nxserver --userdeland to add you can use
When the user’s db is disabled the users are automatically added to it, and this is the reason why it is not empty.
In V7 we are not using file users.db anymore.
Thank you, Coleman! The link was corrected.
We’ve opened a Trouble Report for this issue:https://www.nomachine.com/TR03S10162.
You can sign up to receive notification of a fix when it’s available.
Thanks for reporting.March 25, 2021 at 16:40 in reply to: After remote session freezes and killed, user kept logged without any connection #32600
Can you send us logs from both the client and server-side, please? You can see the following article for guidance: Collect server and client logs manually.
Please send them as an attachment to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email. Thanks!
Can you try to add the following line to node.cf on the server-side:
DisplayAgentExtraOptions "-yuvgrab 1"
The node.cfg is located here: /Applications/NoMachine.app/Contents/Frameworks/etc
If the problem persists, a video will be very useful indeed. Thank you!
We suggest as a first step to assure that the connection is arriving at the intended machine (the one at your workplace). This can be done by examining the nxd.log file and checking if there is any info about incoming connections at the time you tried.
If there is no incoming connection, you can try to set up access to the intended machine according to the following article: How to connect to NoMachine when the server is behind a NAT router or a firewall
Thank you for letting us know. We are glad it works!
Logs are not required at this point. As the problem is solved, the logs are now overwritten.
In case there is the need to collect logs for future cases, you can check the following article: Collect server and client logs manually.
The MacOS version you’re using is 10.4.6 or 10.14.6? Thanks!
The username and password required by the NoMachine are your usual account credentials from your remote machine (fig. 6 here https://www.nomachine.com/getting-started-with-nomachine).
The TR associated with this forum post was closed in the software release 7.1.3: Incorrect mouse pointer offset when dragging the cursor in a macOS session
Please update, if you have not done so yet 😉March 12, 2021 at 17:31 in reply to: Server capacity: reached for user, when user is logged on at physical desktop #32375
The TR associated with this forum post was closed in the software release 7.2.3: Error ‘The session negotiation failed’ occurs when a user is already logged on at the physical desktop
NoMachiners, please update 🙂