Error is 138: Connection timed out

Forums / NoMachine for Windows / Error is 138: Connection timed out

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #4320
    Avatarmanu_sinha
    Participant

    NoMachine Version – 4.2.26

    I am using NoMachine to connect from my windows 7 machine to Unix (CentOS). I successfully installed NoMachine on my CentOS. I then installed NoMachine on my windows, but I am not able to connect from my windows to my unix machine using NoMachine.

    I always get the following error –

    Could not connect to the server.
    Error is 138: Connection timed out

    Please note, I can SSH from my windows machine to the unix machine. I tried VNC from my windows to my unix and that works perfectly. I also confirmed that unix machine doesn’t have any firewall.

    Logs –
    Info: Starting NoMachine version 4.2.26.
    Info: Loading settings from ‘C:\Users\mname\.nx\config\player.cfg’.
    2412 10880 00:36:14 017.664 Main: Exception handling library not loaded.
    2412 10880 00:36:14 017.664 Main: Creating the client session.
    2412 10880 00:36:14 017.664 ClientSession: Initializing session at 0x02672580.
    2412 10880 00:36:14 160.621 ClientSession: Initialized session at 0x02672580.
    2412 10880 00:36:14 164.620 Main: Entering the GUI event loop.
    2412 10880 00:36:16 336.968 ClientSession: Starting session at 0x02672580.
    2412 10880 00:36:16 337.967 ClientSession: Going to start session ‘C:\Users\mname\Documents\NoMachine\Connection to UNIX IP.nxs’.
    2412 10880 00:36:16 396.950 Connection: Initializing connection at 0x061218b0.
    2412 10880 00:36:16 398.949 Connection: Initialized connection at 0x061218b0.
    2412 10880 00:36:16 398.949 Connection: Starting connection at 0x061218b0.
    2412 10880 00:36:16 398.949 ClientDaemonConnector: Starting a new connection to host ‘UNIX IP’ on port ‘4000’.
    2412 10880 00:36:16 399.949 Connection: Started connection at 0x061218b0.
    2412 10880 00:36:16 405.947 ClientSession: Started session at 0x02672580.
    2412 10880 00:36:46 400.946 Connection: Connection at 0x061218b0 failed.
    2412 10880 00:36:46 400.946 ClientSession: Runnable at 0x061218b0 caused the session at 0x02672580 to fail.
    2412 10880 00:36:46 400.946 ClientSession: Failing reason is ‘Could not connect to the server.

    Error is 138: Connection timed out’.
    2412 10880 00:36:46 420.940 ClientSession: Stopping session at 0x02672580.
    2412 10880 00:36:46 446.932 Connection: Stopping connection at 0x061218b0.
    2412 10880 00:36:46 447.932 ClientDaemonConnector: Stopping the current connection.
    2412 10880 00:36:46 447.932 Connection: Stopped connection at 0x061218b0.
    2412 10880 00:36:46 447.932 ClientSession: Going to kill all children.
    2412 10880 00:36:46 461.928 ClientSession: Stopped session at 0x02672580.

    #4329
    Avatarreza
    Moderator

    Please assure that you set correct host name or IP address instead of ‘UNIX IP’.

    For example:

    10.0.0.1

    hostname

    hostname.domain.com

    #4332
    Avatarmanu_sinha
    Participant

    Hi Reza… I using correct host name or IP address… UNIX IP is a placeholder with which I have masked the actual IP address…

     

    I am using ifconfig to get the ip of the unix machine

    #4339
    Avatarreza
    Moderator

    Manu Sinha,

    Can you verify that you can connect from Windows machine to Linux port 4000?

    Thank you.

Viewing 4 posts - 1 through 4 (of 4 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.