Cannot connect over the internet

Forums / NoMachine for Mac / Cannot connect over the internet

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #33800
    Avatarkhsacc
    Participant

    Dear Contributors to NoMachine Forums,

    Hello, I’m trying to connect my MacBook Pro (10.15.6) to my Windows 10 (physical display) via the newest version of NoMachine. I’ve succeeded when the two computers are on a common local wi-fi network, however, it doesn’t work if they are on a different network (I mean, I want to manipulate my Windows in my lab room from home). I tried the following things: rebooting the OS, re-installing NoMachine, resetting my wi-fi networks.

    I guess this issue is very similar to the previous one (https://forums.nomachine.com/topic/issue-a-connection-timeout) but let me post again because so solution was found in the thread.

    Here I show one of the logs as an example of the failure.
    Info: Starting NoMachine version 7.6.2.
    Info: Loading settings from '/Users/<USERNAME>/.nx/config/player.cfg'.
    Info: Loaded translation files for 'English'.
    8682 775 08:23:19 737.270 Main: Creating the client session.
    8682 775 08:23:19 737.370 ClientSession: Initializing session at 0x7fc519009000.
    8682 775 08:23:23 079.289 ClientSession: Initialized session at 0x7fc519009000.
    8682 775 08:23:23 082.046 ClientSession: Starting session at 0x7fc519009000.
    8682 775 08:23:23 110.697 ClientSession: Going to start session '/Users/<USERNAME>/Documents/NoMachine/My-Windows-PC.nxs'.
    8682 775 08:23:23 120.134 ClientThread: Creating new thread.
    8682 775 08:23:23 122.093 Connection: Initializing connection at 0x7fc51669b360.
    8682 775 08:23:23 122.153 Connection: Initialized connection at 0x7fc51669b360.
    8682 775 08:23:23 122.164 Connection: Starting connection at 0x7fc51669b360.
    8682 775 08:23:23 122.172 ClientDaemonConnector: Starting a new connection to host 'xxx.xx.xx.xxx' on port '4000'.
    8682 775 08:23:23 122.345 Connection: Started connection at 0x7fc51669b360.
    8682 775 08:23:23 126.772 ClientSession: Started session at 0x7fc519009000.
    Info: Slave server running with pid xxxxxx.
    Info: Listening to slave connections on port 32322.
    8682 775 08:23:23 128.284 Main: Entering the GUI event loop.
    8682 775 08:23:53 123.045 Connection: Connection at 0x7fc51669b360 failed.
    8682 775 08:23:53 123.122 ClientSession: Runnable at 0x7fc51669b360 caused the session at 0x7fc519009000 to fail.
    8682 775 08:23:53 123.148 ClientSession: Failing reason is 'A connection timeout has occurred while trying to connect to 'xxx.xx.xx.xxx' 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.'.
    8682 775 08:23:53 135.533 ClientSession: Stopping session at 0x7fc519009000.
    Info: Slave server running with pid xxxxxx.
    Info: Listening to slave connections on port 23088.
    8682 775 08:23:53 145.962 Connection: Stopping connection at 0x7fc51669b360.
    8682 775 08:23:53 146.273 ClientDaemonConnector: Stopping the current connection.
    8682 775 08:23:53 146.297 Connection: Stopped connection at 0x7fc51669b360.
    8682 775 08:23:53 158.730 ClientSession: Stopped session at 0x7fc519009000.

    The log above is from when I tried to connect my Windows from Macbook, but the error was the same for the opposite directional connection.

    For both machines (Mac and Windows), NoMachine didn’t display the IP address WITH port number (like :xxxxx), I guess this might be the problem, but I’m not sure.

    Best regards,

    #33827
    AvatarCarin
    Participant

    Hi khsacc,

    Please take a look at this article and check also the “Solving possible problems” section: How to connect to NoMachine when the server is behind a NAT router or a firewall

    For both machines (Mac and Windows), NoMachine didn’t display the IP address WITH port number (like :xxxxx), I guess this might be the problem, but I’m not sure.

    This means that port forwarding failed and you have to manually adjust your router.

    #33861
    Avatarkhsacc
    Participant

    thank you. I’ll try and respond in a few days.

     

    Best,

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

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