NoMachine not starting

[esan123]

Hello,

After successfully installing latest NoMachine free version for Windows 10 64 bit and rebooting as requested, the server wont start. Even when trying to manually start the server it wont start. This is running inside a virtual machine on vSphere 6. Still can’t connect through NoMachine free client.

Please find the logs attached.

 

 

Thank you in advance

[Cato]

Hello esan123,

What kind of antimalware software do you use, if any? We’re aware of problems with NoMachine when lsass.exe system service runs in protected mode which is often enabled by installation of antimalware applications.

To verify that this happens in your case:

1. Download and install Process Explorer using this link:

 https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx

2. Start Process Explorer as Administrator.

3. Double click on lsass.exe process anc check the value of ‘Protected’

[esan123]

Hello,

Thank you for the reply, I use Free Avast antivirus and thats it. I used to use cyber reason ransomfree but removed it a couple of OS updates ago. (www.ransomfree.cybereason.com). I also have latest version of ccleaner.

 

The value of protected says PsProtectedSignerAntimalware-Light

 

 

Thank you

[Cato]

Hello esan123,

We created trouble report for your issue:

https://www.nomachine.com/TR03O07676

We’re intensively working on solution, you can follow the state of TR.

[esan123]

Thank you for the TR,

 

I have uninstalled Avast and any antivirus and sometimes it seems to work, now I notice that NoMachine suddenly stops on the server, sometimes when having any open application, but last time the machine was just idle. When trying to connect from a client I get “The session negotiation failed.

Error: Descriptor: FD#20352 not available”

 

Logs attached.

[Britgirl]

The logs that you tried to attach failed, so please send them to forum[at]nomachine[dot]com. Thanks

[Joel9576]

That’s where I sent them last week.  I intentionally didn’t attach them to the thread.  I’ll resend the email shortly.

[Britgirl]

My mix-up, I thought they were new logs that Cato had asked for. He has identified the TR as a potential problem, so you should signup to receive notification of its fix. In the meantime, the other error you mention is discussed here:

https://www.nomachine.com/forums/topic/error-descriptor-fd_____-not-available

 

There is a patch available, not yet released, if you are interested we can send you a package to download.

[Joel9576]

Esan, Britgirl: I’m an idiot; my apologies.

I thought I was responding to my thread.  I emailed my logs last week, but hadn’t received an update from Cato yet, although if I had to guess – we might be experiencing the same issue.

Sorry for the confusion.

[Author]

Posts