Error is 99: Cannot assign requested address

Forums / NoMachine for Linux / Error is 99: Cannot assign requested address

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #25606
    Avatarmgibbons
    Participant

    Hello,

    I’m trying to access a remote NoMachine server from an android tablet.

    Host is on NAT and local connections work normally. External connections from host client to other NoMachine hosts works normally also.

    Host NoMachine: nomachine-enterprise-desktop_6.9.2_1_amd64.deb Ubuntu 18.04.3

    Client host  NoMachine Server shows to connect to nx://72.130.27.203:26300 and GW port 26312

    On the host –upnpstatus and ifconfig -a shows:

    Local IP                   192.168.5.158
    Gateway IP                 192.168.5.1
    External IP                72.130.27.203
    NX port 4000 mapped to:    72.130.27.203:26300

    My router shows 192.168.5.158 26300 > 4000 TCP and UDP

    My android log shows

    3556 3767 10:14:58 448.706 ClientSession: Going to start session ‘/sdcard/NoMachine/Connection to 72.130.27.203.nxs’.
    3556 3767 10:14:58 484.653 Connection: Finishing connection at 0xc416d1e0.
    3556 3767 10:14:58 484.745 ClientDaemonConnector: Stopping the current connection.
    3556 3767 10:14:58 484.779 Connection: Finished connection at 0xc416d1e0.
    3556 3767 10:14:58 484.797 Connection: Initializing connection at 0xc416d1e0.
    3556 3767 10:14:58 485.134 Connection: Initialized connection at 0xc416d1e0.
    3556 3767 10:14:58 485.179 Connection: Starting connection at 0xc416d1e0.
    3556 3767 10:14:58 485.209 ClientDaemonConnector: Starting a new connection to host ‘72.130.27.203:26300’ on port ‘4000’.
    3556 3767 10:14:58 485.645 Connection: Started connection at 0xc416d1e0.
    3556 3767 10:14:58 495.308 ClientSession: Started session at 0xdc5fd800.
    3556 16146 10:15:09 117.968 Io/Io: WARNING! Can’t resolve IP host ‘72.130.27.203:26300’.
    3556 16146 10:15:09 118.358 Io/Io: WARNING! Error is 99, ‘Cannot assign requested address’.
    3556 16146 10:15:09 118.439 TcpConnector/TcpConnector: ERROR! Can’t resolve host ‘72.130.27.203:26300’.
    3556 16146 10:15:09 118.486 TcpConnector/TcpConnector: ERROR! Error is 7, ‘No address associated with hostname’.
    3556 16146 10:15:09 118.534 TcpConnector/TcpConnector: ERROR! In method ‘start’ context [D].
    Error: Can’t resolve host ‘72.130.27.203:26300’.
    Error: Error is 7, ‘No address associated with hostname’.
    Error: In method ‘start’ context [D].
    3556 3767 10:15:09 132.983 Connection: Connection at 0xc416d1e0 failed.
    3556 3767 10:15:09 133.189 ClientSession: Runnable at 0xc416d1e0 caused the session at 0xdc5fd800 to fail.
    3556 3767 10:15:09 133.251 ClientSession: Failing reason is ‘Could not connect to the server.
    Error is 99: Cannot assign requested address’.
    3556 3767 10:15:09 156.375 ClientSession: Stopping session at 0xdc5fd800.
    3556 3767 10:15:09 216.949 Connection: Stopping connection at 0xc416d1e0.
    3556 3767 10:15:09 217.352 ClientDaemonConnector: Stopping the current connection.
    3556 3767 10:15:09 217.545 Connection: Stopped connection at 0xc416d1e0.
    3556 3767 10:15:09 283.828 ClientSession: Stopped session at 0xdc5fd800.
    QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: Permission denied

    and my host nxserver.log shows

    2020-02-11 12:19:12 880.025 25573 NXSERVER Read ‘Local IP                   192.168.5.158\nGateway IP                 192.168.5.1\nExternal IP                72.130.27.203\nNX port 4000 mapped to:    72.130.27.203:26300\n’ on FD#7
    2020-02-11 12:19:12 880.104 25573 NXSERVER Something to read from accepted nxserver monitor socket on FD#7.
    2020-02-11 12:19:12 880.142 25573 NXSERVER Connection was closed.
    2020-02-11 12:19:12 880.175 25573 NXSERVER Closing connection to nxserver –daemon.
    2020-02-11 12:19:12 880.225 25573 NXSERVER NXClose FD#7 from NXClientSystemDaemons::closeConnection.
    2020-02-11 12:19:12 880.435 25573 NXSERVER Finalize process.
    2020-02-11 12:19:12 880.495 25573 NXSERVER Connection to client open or nulled.
    2020-02-11 12:19:12 880.530 25573 NXSERVER Closing client connection.
    2020-02-11 12:19:12 880.620 25573 NXSERVER NXClose FD#3 from NXBegin::finalizeProcess.
    2020-02-11 12:19:12 880.678 25573 NXSERVER NXClose FD#2 from NXBegin::finalizeProcess.

    Please advise how to resolve.

    Thank you

    #25634
    AvatarTor
    Contributor

    Hi. I suppose you’ve created a new connection and used 72.130.27.203:26300 in the hostname field. You can set the correct hostname by selecting the connection in the list and tapping Edit, then setting 72.130.27.203 as hostname and 26300 as port. Please let me know if this helps or, in the contrary case, tell me how you configure the connection so we can detect possible issues.

    #25641
    Avatarmgibbons
    Participant

    Yes, that was the problem. When I did as you suggest  it worked correctly. I think the NoMachine server prompts are somewhat misleading.

    Thank you.

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

You must be logged in to reply to this topic.