Error is 110: Connection timed out

Forums / NoMachine for Linux / Error is 110: Connection timed out

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #3229
    swarnendubiswas
    Participant

    Hi,

    I am using NX 4.2 to connect from my Ubuntu laptop to my workstation which is an RHEL 6.5 machine. I have tried connecting over both NX and ssh protocol, but both doesn’t work. The connection times out with the following error message “Error is 110: Connection timed out”. I am not sure where the error lies, whether on my client or server machine. It would help if you can suggest pointers to narrow down where the error lies.

    I was earlier extensively using version 3.5. But suddenly, it started throwing authentication errors and the client is not able to connect anymore. That is why I am trying to setup version 4.

    #3258
    Britgirl
    Keymaster

    Are you able to SSH in to your RHEL machine from your laptop?

    The logs would be useful from both sides to see what is happening. Please follow the instructions here and either attach them to your reply or forward them to issues[at]nomachine.com.

    https://www.nomachine.com/AR07K00677

    If you have had issues connecting to a 3.5.0 server from a version 4.2 client, you should submit further information via the link above. 3.5.0 issues are dealt with via the traditional support channels whereas the forums are dedicated to version 4 server/client questions.

     

    #3252
    swarnendubiswas
    Participant

    Info: Starting NoMachine version 4.2.21.
    Info: Loading settings from ‘.nx/config/player.cfg’.
    18483 18483 09:02:11 990.695 Main: Creating the client session.
    18483 18483 09:02:11 990.751 ClientSession: Initializing session at 0x252eda0.
    18483 18483 09:02:12 384.228 ClientSession: Initialized session at 0x252eda0.
    18483 18483 09:02:12 384.274 Main: Entering the GUI event loop.
    18483 18483 09:03:02 141.868 ClientSession: Starting session at 0x252eda0.
    18483 18483 09:03:02 143.598 ClientSession: Going to start session ‘/home/xxx/Virtual Desktops/Connection to xx.xx.xx.xx.nxs’.
    18483 18483 09:03:02 155.757 Connection: Initializing connection at 0x2878880.
    18483 18483 09:03:02 155.823 Connection: Initialized connection at 0x2878880.
    18483 18483 09:03:02 155.838 Connection: Starting connection at 0x2878880.
    18483 18483 09:03:02 155.847 ClientDaemonConnector: Starting a new connection to host ‘xx.xx.xx.xx’ on port ‘4000’.
    18483 18483 09:03:02 155.959 Connection: Started connection at 0x2878880.
    18483 18483 09:03:02 160.636 ClientSession: Started session at 0x252eda0.
    18483 18483 09:03:32 157.538 Connection: Connection at 0x2878880 failed.
    18483 18483 09:03:32 157.628 ClientSession: Runnable at 0x2878880 caused the session at 0x252eda0 to fail.
    18483 18483 09:03:32 157.687 ClientSession: Failing reason is ‘Could not connect to the server.

    Error is 110: Connection timed out’.
    18483 18483 09:03:32 200.458 ClientSession: Stopping session at 0x252eda0.
    18483 18483 09:03:32 202.136 Connection: Stopping connection at 0x2878880.
    18483 18483 09:03:32 202.168 ClientDaemonConnector: Stopping the current connection.
    18483 18483 09:03:32 202.195 Connection: Stopped connection at 0x2878880.
    18483 18483 09:03:32 202.208 ClientSession: Going to kill all children.
    18483 18483 09:03:32 210.000 ClientSession: Stopped session at 0x252eda0.
    Fontconfig error: “/home/xxx/.config/fontconfig/fonts.conf”, line 1: no element found
    Fontconfig error: “~/.fonts.conf”, line 1: no element found
    18483 18568 09:03:44 101.824 FileBrowser: File ‘/home/xxx/Desktop
    ‘ is selected.

    #3282
    Britgirl
    Keymaster

    Are you able to SSH in to your RHEL machine from your laptop?

    Server side logs as well.

    #3316
    swarnendubiswas
    Participant

    Thank you for your suggestions.

    Here are the logs with Nx player 4.2 both for the server and the client. Please let me know if I need to provide further information.

     

    #3333
    swarnendubiswas
    Participant

    Hi,

    I have attached the nxclient and server logs as well.

    #3352
    Britgirl
    Keymaster

    From the logs of your connection to server 4.2.21, port 4000 is somehow being filtered or blocked. Port 22 (SSH) is open, so you have two options:
    1) Check your firewall settings and allow connections via NX to port 4000

    2) Or you can connect via SSH instead of NX provided you have a version that supports SSH (any of the Enterprise Server/Terminal Server products).

    I have removed your logs of the 3.5.0 server. As I mentioned earlier, our traditional support channels are available for 3.5.0 users. If you have a subscription, log in and submit your enquiry there.

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