Guro

[Guro]

Current known problem with Windows is related to NoMachine installation folder.

If you install Windows in a folder which is located in mounted disk (as shared folder), the service is unable to start because it can’t match NoMachine module path.

Please ensure that your NoMachine install path is located in the standard logical disk or allow NoMachine to choose default path.

For user DaveXS, could you send compressed NoMachine log data to us, so we can check?

You need to compress folder C:\ProgramData\NoMachine\var\log

[Guro]

Hello

Could you reinstall NoMachine with disabled Firewall(if it enabled) and disabled Antivirus (if it installed)?

We try to reproduce this issue in our labs.

Thanks

[Guro]

Hello.

Could you provide opened pipe name information?

You just need to open PowerShell and input

[System.IO.Directory]::GetFiles(“\\.\pipe\”)

Please, check if listed pipe name contains pipes with nx prefix.

like:

\\.\pipe\nxdevice-bc72a506-0e0c-4bff-b6f8-c2b6aa32e906

\\.\pipe\nxfsd-709fd562-36b5-48c6-9952-302da6218061

\\.\pipe\nxserver-WqJhjF9jm0-l0dmS-Hs8dXKc0

\\.\pipe\nxsspi-ef0b693a-97e0-4d61-8582-a24f630526e1

You can use  pipelist.exe tool for this, also.

Thanks.

[Guro]

Hello

Did you use ‘password’ or ‘kerberos’ authentication?

And could you send client session and server debug logs to us? You can attach them here or submit the to forum[at]nomachine[dot]com.

Instruction to take logs are here: https://www.nomachine.com/DT10O00163

Thank You.

 

[Guro]

Hello.

Yes, you can continue using keys generated by nxkeygen.

Thanks.

[Guro]

Hello

We working to fix this issue. For temporary solution we recommend to use system (Linux,osX) native ssh.

You can edit nxplayer configuration file. First close nxpayer window.

On client side. This file located ~/.nx/config/player.cfg

File has xml format. Please find <option key=”SSH client mode” value=”library” /> and change

library on native. Like this: <option key=”SSH client mode” value=”native” />
Close file and start nxplayer. Instead NX protocol switch on SSH for your connection.

Thanks

[Guro]

Hello

Currently we are unable to reproduce this issue in our test environment.

To take more detailed information of lsass to the NoMachine service, we need to prepare a debug package. Would it be possible for you to install this NoMachine package and then and send us the logs to us for further analysis?

[Guro]

Hello

Send logs to us if you happen to notice further problems 🙂

Thanks

[Guro]

Hello.

No, you’re not doing anything wrong.

Could you provide NoMachine logs to us?

You can find it in C:\Documents and Settings\All Users\NoMachine\var\log,

just zip this folder and send to us.

 

Could you also try doing this:

1. Open “NoMachine Service” switch on “Server Preferences” tab.
2. Choose devices tab.
3. Switch off all check boxes.
4. Click “done”.
5. Restart server.
6. Check connections again.

If you still notice problem, report to us please.

Thanks.

[Guro]

Hello.

This bug was described as TR and solution released with NoMachine 6.2.4 version.
Please update your NoMachine installation.

Sorry, for late answer.

[Guro]

Hello

Did you notice whether Kerberos tickets are getting lost on both OSes( mate 16.04 and ubuntu ?18.04).

Are all OSes in the same kerberos REALM? Are they in the same domain?

[Author]

Posts