Connection timeout issue connecting to Ubuntu

Forum / NoMachine for Linux / Connection timeout issue connecting to Ubuntu

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #50178
    aevans0001
    Participant

    Hi I recently started having issues connecting [removed] from Android or Windows to Ubuntu.  I only have 1 Ubuntu machine.

    The issue is either it doesn’t show up as online [removed] or the connection times out (NoMachine and [removed] ).  This problem started in the last month and is the reason I found NoMachine.  I am very happy and plan to use NoMachine exclusively but I need to find a solution.  What is the best way to provide the info you need to help diagnose my issue.  I am guessing it is a firewall issue but unknown.

    #50248
    aevans0001
    Participant
    #50341
    Britgirl
    Keymaster

    The logs show  ‘A connection timeout has occurred while trying to connect to ‘192.168.1.250’ on port ‘4000’. The issue could either be caused by a networking problem, by a firewall or NAT blocking incoming traffic or by a wrong server address. Please verify your configuration and try again.’.

    That indicates a problem with your router, it could be a double NAT for example, or you have not enabled port forwarding correctly. Please take a look at the instructions here:

    How to connect over the internet to NoMachine behind a NAT router
    https://kb.nomachine.com/AR04S01122

    The need for network configuration when using NoMachine to access remote computers over the Internet will be removed when we release NoMachine Network in version 9 (coming soon). You can read more about this feature here: https://www.nomachine.com/network.

    #50577
    aevans0001
    Participant

    So I have now tried a different router and some other fixes and still can not log in.  I am not trying to get to the ubuntu pc from outside my network, just from this pc to my ubuntu.  I have tried to access it from multiple computers from inside and outside computers.

    This is how i removed a different remote desktop service that created this issue (i believe)

    sudo apt purge rus****
    
    sudo rm -rf ~/.config/rus****
    
    sudo rm -rf /root/.config/rus****

     

    sudo rm -rf /root/.config/ru****

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

You must be logged in to reply to this topic. Please login .