NoMachine Error is 1332

Forums / NoMachine for Windows / NoMachine Error is 1332

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #36341
    pvm
    Participant

    One of the clients does not connect to the server. Here is such an error in the log. Tell me how to fix it

    Error code is : 0.

    Package’s response is : 0xc0000001.

    3956 3672 17:48:04 015 ExecuteNodeNXLsa: ERROR! NXLsa/exec failed and no password available.

    3956 3672 17:48:04 046 Info: Node process running with pid 1524.

    2324 2324 17:48:06 294.312 Redis: Foregroud saving started by pid 2324.

    Info: Connection from 178.34.151.153 port 18729 closed on Fri Nov 19 17:48:06 2021.

    Info: Handler with pid 2616 terminated on Fri Nov 19 17:48:06 2021.

    2616 4152 17:48:07 682.715 Io/Io: WARNING! Descriptor FD#512 type socket still open at exit.

    2616 4152 17:48:07 682.715 Io/Io: WARNING! Descriptor FD#624 type socket still open at exit.

    Info: Handler started with pid 632 on Fri Nov 19 17:48:45 2021.

    Info: Handling connection from 178.34.151.153 port 18737 on Fri Nov 19 17:48:45 2021.

    3408 3752 17:49:14 639 ConvertSidToGroupName: ERROR! Can’t get sid based on username.

    3408 3752 17:49:14 639 ConvertSidToGroupName: Error is 1332.

    3408 3752 17:49:14 639 nxexecAddGroups: ERROR! Could not get the group name.

    3408 3752 17:49:14 639 nxexecAddGroups: Error is 1332.

    3272 1680 17:49:15 186 NXLsaSendRequest: ERROR! Cannot send request to NXLSA package.

    Error code is : 0.

    Package’s response is : 0xc0000001.

    3272 1680 17:49:15 202 ExecuteNodeNXLsa: ERROR! NXLsa/exec failed and no password available.

    3272 1680 17:49:15 217 Info: Node process running with pid 3448.

    2324 2324 17:49:17 323.638 Redis: Foregroud saving started by pid 2324.

    Info: Connection from 178.34.151.153 port 18737 closed on Fri Nov 19 17:49:17 2021.

    Info: Handler with pid 632 terminated on Fri Nov 19 17:49:17 2021.

    632 3256 17:49:18 571.640 Io/Io: WARNING! Descriptor FD#512 type socket still open at exit.

    632 3256 17:49:18 571.640 Io/Io: WARNING! Descriptor FD#656 type socket still open at exit.

    3856 5168 17:49:39 701.078 Io/Io: WARNING! Found descriptor FD#512 with type socket.

    3856 5168 17:49:39 701.078 Io/Io: WARNING! Replaced descriptor FD#512 with FD#600.

    Info: Handler started with pid 3856 on Fri Nov 19 17:49:39 2021.

    Info: Handling connection from 178.34.151.153 port 18726 on Fri Nov 19 17:49:39 2021.

    6036 4752 17:49:48 517 NXKeepTokenForGssapi: ERROR! LogonUser failed.

    6036 4752 17:49:48 517 NXKeepTokenForGssapi: Error code is 1326.

    Info: Connection from 178.34.151.153 port 18726 closed on Fri Nov 19 17:49:48 2021.

    Info: Handler with pid 3856 terminated on Fri Nov 19 17:49:48 2021.

    3856 5168 17:49:48 626.294 Io/Io: WARNING! Descriptor FD#512 type socket still open at exit.

    3856 5168 17:49:48 626.294 Io/Io: WARNING! Descriptor FD#628 type socket still open at exit.

    Info: Handler started with pid 5444 on Fri Nov 19 17:49:49 2021.

    Info: Handling connection from 178.34.151.153 port 18741 on Fri Nov 19 17:49:49 2021.

     

    #36353
    Britgirl
    Keymaster

    It seems there is a problem with  nxlsa.

    Did you reboot the computer after installing NoMachine?

    If you did, what is the NoMachine version? What is the Windows version?

    Do you have an antivirus installed or is there LSA protected mode enabled?

    #36358
    pvm
    Participant

    Yes I have rebooted.

    Client version NoMachine 7.7.4. Windows 7

    Server version NoMachine 7.7.4. Windows Server 2008 R2. Updated NoMachine to the latest versions

    Avast antivirus on the client, I tried to disable it.

    Is LSA Windows Defender ?

    I have other Windows 7 clients, they connect successfully

    #36403
    Cato
    Contributor

    Hello pvm,

    If the problem is only with one of a few client machines this usually means some networking/connection issue. Can you ping server host from your client? If you make sure that server host is reachable, but problem persists, follow these instructions to gather full set of client and server-side logs:
    https://knowledgebase.nomachine.com/DT11R00181
    Send them to forum[at]nomachine[dot]com, referencing the topic in the email subject.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.