DaemonGreeter error

Forum / NoMachine for Windows / DaemonGreeter error

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • December 18, 2015 at 10:13 #9378
    grosmar
    Participant

    Hi,

    I’m stuck with NoMachine. I try to use it between two windows pc’s, and i got a strange error that you see in the title. Tried to search for it on the net, but no success.

    I use 3389 instead of 4000 because our office keep this port opened. Also stopped RDP services on this port.

    When i use telnet i reach the server on this port it’s open, but when i try to connect with NoMachine client it end’s with connection reset by peer.

    Also tried to disable UDP but it didn’t help me.

    Here is the log, i’ve marked the crappy part.

    9436 7008 17:40:34 215.078 ClientSession: Starting session at 0x00a9d4d8.

    9436 7008 17:40:34 215.078 ClientSession: Going to start session ‘D:\Documents\NoMachine\Connection to 192.168.206.47.nxs’.

    9436 7008 17:40:34 230.718 Connection: Finishing connection at 0x057c1278.

    9436 7008 17:40:34 230.718 ClientDaemonConnector: Stopping the current connection.

    9436 7008 17:40:34 230.718 Connection: Finished connection at 0x057c1278.

    9436 7008 17:40:34 230.718 Connection: Initializing connection at 0x057c1278.

    9436 7008 17:40:34 230.718 Connection: Initialized connection at 0x057c1278.

    9436 7008 17:40:34 230.718 Connection: Starting connection at 0x057c1278.

    9436 7008 17:40:34 230.718 ClientDaemonConnector: Starting a new connection to host ‘192.168.206.47’ on port ‘3389’.

    9436 7008 17:40:34 230.718 Connection: Started connection at 0x057c1278.

    9436 7008 17:40:34 246.328 ClientSession: Started session at 0x00a9d4d8.

    Info: Connection to 192.168.206.47 port 3389 started at 17:40:34 261.954.

    9436 6928 17:40:34 996.671 DaemonGreeter/DaemonGreeter: WARNING! Read from FD#1504 failed.

    9436 6928 17:40:34 996.671 DaemonGreeter/DaemonGreeter: WARNING! Error 108, ‘Connection reset by peer’.

    9436 8340 17:40:34 996.671 DaemonClientApplication/DaemonClientApplication: WARNING! Session terminated abnormally.

    9436 8340 17:40:34 996.671 DaemonClientApplication/DaemonClientApplication: WARNING! Error is 108, ‘Connection reset by peer’.

    Warning: Connection to 192.168.206.47 port 3389 failed at 17:40:34 996.671.

    Warning: Error is 108, ‘Connection reset by peer’.

    9436 7008 17:40:34 996.671 Connection: Connection at 0x057c1278 failed.

    9436 7008 17:40:34 996.671 ClientSession: Runnable at 0x057c1278 caused the session at 0x00a9d4d8 to fail.

    9436 7008 17:40:34 996.671 ClientSession: Failing reason is ‘Could not connect to the server.

     

    Error is 108: Connection reset by peer’.

    9436 7008 17:40:35 012.262 ClientSession: Stopping session at 0x00a9d4d8.

    9436 7008 17:40:35 012.262 Connection: Stopping connection at 0x057c1278.

    Info: Slave server running with pid 3864.

    9436 7008 17:40:35 012.262 ClientDaemonConnector: Stopping the current connection.

    Info: Listening to slave connections on port 55933.

    9436 7008 17:40:35 012.262 Connection: Stopped connection at 0x057c1278.

    9436 7008 17:40:35 027.905 ClientSession: Stopped session at 0x00a9d4d8.

    December 18, 2015 at 16:12 #9396
    reza
    Participant

    It looks like there something other then NX daemon listening on your server side.

    Please verify that port 3389 is used by nxd process.

     

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)

This topic was marked as solved, you can't post.