Cannot connect to NoMachine server

Forums / NoMachine for Windows / Cannot connect to NoMachine server

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #28470
    Avatarprattu
    Participant

    I’ve tried reinstalling NoMachine on this machine but I’m still unable to connect. The server status says its Running, the port is set to 4000, and I can remote into it through RDP. I checked the error log and this is what I’m seeing.

     
    
    5424 7112 17:40:34 956.090 ServerNetworkInfoHandler: WARNING! Obtaining network data failed.
    
    Info: Handler started with pid 10048 on Thu Jul 09 17:42:31 2020.
    
    Info: Handling connection from 10.0.46.248 port 35292 on Thu Jul 09 17:42:31 2020.
    
    5676 10092 17:42:38 424 NXLsaSendRequest: ERROR! Cannot send request to NXLSA package.
    
    Error code is : 0.
    
    Package's response is : 0xc0000001.
    
    5676 10092 17:42:38 424 ExecuteNodeNXLsa: ERROR! NXLsa/exec failed and no password available.
    
    5676 10092 17:42:38 439 ExecuteNodeToken: ERROR! Failed to create process as user.
    
    5676 10092 17:42:38 439 ExecuteNodeToken: ERROR! Error is '193'
    
    5676 10092 17:42:38 439 nxexecExecNode: ERROR! Failed to launch node process.
    
    5676 10092 17:42:38 439 main: ERROR! Could not execute nxnode.
    
    Info: Connection from 10.0.46.248 port 35292 closed on Thu Jul 09 17:42:38 2020.
    
    Info: Handler with pid 10048 terminated on Thu Jul 09 17:42:38 2020.
    
    #28516
    AvatarCato
    Contributor

    Hello prattu,

    Logs suggest that you might be experiencing dependency issue. It’s possible that one of dlls installed on your system is in different version than required by NoMachine. It’s also possible that some library is simply missing. You can try
    to copy POSIX.dll from:

    <NoMachine_installation_dir>\lib\perl\POSIX.dll

    to <NoMachine_installation_dir>\bin directory.

    If this helps, please provide us with output of where posix.dll command ran in cmd started as Administrator.

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

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.