Tagged: nxserver windows7 permissions
July 11, 2016 at 09:06 #11801SnakeCoderParticipant
I am running the latest NoMachine client for Windows, downloaded on July 7, 2016 (5.1.26). When my computer starts up, there is a process (nxserver.bin) that starts and stops constantly causing other AV-related processes to scan it. Overall it causes my CPU to spike when this happens.
Further investigation has shown that in the log file (C:\ProgramData\NoMachine\var\log\nxserver.log) it is complaining of permission issues in accessing various *.lock files within the program files folder (C:\program files(x86)\nomachine\etc) … This is all tied to the “NoMachine Device Server”.
I have tried granting various access rights to the local “nx” user account for both folders (program data\nomachine\var\* and program files(x86)\nomachine\etc) to no avail. It seems that every time I try to fix one, another one pops-up in the error log.
At this point, I am just going to disable the service. I don’t use any sharing/drives/usb on my NX server connections anyway.
Is this just me? Has anyone else ever seen such behavior? If so, how do you fix it? Please note, I am only in need of the client itself — this Windows box will not be a NX server.July 13, 2016 at 14:20 #11838
Please send us the logs from ProgramData/NoMachine/var/log directory with increased debug level. Details on how to increase the level of debug are here: https://www.nomachine.com/DT07M00098#3
Send to forum[at]nomachine[dot]comJuly 15, 2016 at 11:12 #11856SnakeCoderParticipant
Unfortunately, administrative access on my machine is restricted — and I had a small window in order to troubleshoot this problem. So, at this time, I won’t be able to provide any of the logs requested. I am just surprised it’s never come up before — as far as I can tell. I’ll leave this here just in case anyone else runs into it. For me, the solution was just to disable the “NoMachine Device Server” service permanently. And I am OK with that.
Thanks for the response.July 29, 2016 at 15:13 #11957
Could be related to a couple of other issues we have been investigating and reported on the forums https://www.nomachine.com/forums/topic/clean-install-service-doesnt-start-win-10. We’ll update the topic once we have some more information.October 11, 2016 at 11:32 #12682
An update so far. What we see is that there’s a different dll path search order, but we don’t understand what might be causing changes in this path search order. What we can suggest is that you update to the latest version and tell us if the problem persists. If it does, we’ll send you over a debug package to install and continue the investigation on the latest version.
This topic was marked as solved, you can't post.