- This topic has 7 replies, 2 voices, and was last updated 2 years, 2 months ago by
.
-
Posts
-
I am working with one of my users and we are discovering behavior where the NoMachine server service stops sharing the desktop as soon as the user logs in. They are able to connect via the client and get to the login screen. Once they sign in past the login screen there is an issue and the desktop appears to stop sharing. I’ve seen the application also just go from “sharing the desktop” to “not sharing” only after just making one configuration change and restarting the server. This behavior is very new and we are unsure what is causing the problem Any help is appreciated.
Items that have already been tried:
uninstalling & reinstalling software
unchecking/checking the nxnode and NoMachine items listed under the privacy settings for access to the machine
Changing Settings on the Server such as turning off hardware acceleration, changing the stream codec, etc…
Running commands to make sure the user was trusted for remote use
Hi, the user has a Mac in office on 12.5 Monterey and the device they are using at home to remote in is a MacBook with 12.4 Monterey.
We would need server-side logs to be able to understand what is happening as we haven’t been able to reproduce on the fly. Please see the following document for instructions on how to extract the logs, https://kb.nomachine.com/DT11R00182, and submit them to forum[at]nomachine[dot]com making sure to put the title of your topic as the subject. Thanks!
No problem at all! I am working with the user and actively trying to break the software again to reproduce what we’ve seen. Of course now that I actually want it to not work it’s being cooperative. This has been a repeat issue so I know it will come back up. I just have to bide my time. I’ve got debug enabled and can collect logs ASAP.
Just bumping this – I’ve been in touch with the user and we still have debug enabled. Unfortunately this lined up with some time sensitive projects so I haven’t had the opportunity to try and replicate the problem again. Biding my time
I’ll say this and then something will come up of course. As of writing this though we’ve been unable to recreate the problem. With the release of v8 for Mac I’ve upgraded the user and so far so good. I’ll follow up and create a new post/reach out to support should anything come up. I know at least for the time being if any problems arise we can upgrade the software.
This topic was marked as solved, you can't post.