Can’t connect to Linux from Android

[username]

I have a same issue with topic (https://forums.nomachine.com/topic/cant-connect-from-android-to-linux#post-18836). Had tried many manipulations but still can’t establish connection. I need some advice maybe to try another attempt to solve the problem.

1. My router support the UPnP and it’s enabled, also enabled NAT.
2. The NoMachine GUI indicated that I have to connect to nx://11.111.111.11:24040 address but port settings at the “server preferences” menu settled as 4000, so witch way should I connect? Anyway it doesn’t works no matter what the setting has been used.
3. What the address should I use? because the address at NoMachine GUI (nx://11.111.111.11:24040) is different then my public address confirmed by whatismyip.com-like sites and it is 222.222.222.222
4. At the router settings I have an option to port forwarding but it’s not working (I’ve tried to forward port 4000)
5. Also I’ve tried the router’s option called “Application rules” (Description of this option: “The Application Rules option is used to open single or multiple ports in your firewall when the router senses data sent to the Internet on an outgoing “Trigger” port or port range. Special Applications rules apply to all computers on your internal network.”), and also with 4000 port it not worked.
6. Put local computer into DMZ also was not useful, connections (24040 and 4000) still were refused.
7. The list of listening ports (where is the server? maybe this is the problem):

username@username-hp:~$ netstat -tulpn | grep LISTEN
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 0.0.0.0:4000 0.0.0.0:* LISTEN –
tcp 0 0 127.0.0.1:12001 0.0.0.0:* LISTEN 18769/nxnode.bin
tcp 0 0 127.0.0.1:20227 0.0.0.0:* LISTEN –
tcp 0 0 127.0.0.1:25001 0.0.0.0:* LISTEN 18804/nxclient.bin
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN –
tcp 0 0 192.168.100.1:53 0.0.0.0:* LISTEN –
tcp 0 0 192.168.123.1:53 0.0.0.0:* LISTEN –
tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN –
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN –
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN –
tcp 0 0 127.0.0.1:7001 0.0.0.0:* LISTEN 18769/nxnode.bin
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN –
tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN –
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN –
tcp6 0 0 :::4000 :::* LISTEN –
tcp6 0 0 :::139 :::* LISTEN –
tcp6 0 0 :::22 :::* LISTEN –
tcp6 0 0 ::1:631 :::* LISTEN –
tcp6 0 0 ::1:7001 :::* LISTEN 18769/nxnode.bin
tcp6 0 0 :::25 :::* LISTEN –
tcp6 0 0 :::445 :::* LISTEN –

[kroy]

It looks like you have double NAT in place. Is your router connected to the modem or router from your provider? If yes, NoMachine has to go through two devices. That is, a router facing the internet for which you have a private LAN with IP address of 222.222.222.222) and then another router for access to the private network/LAN for which you have an IP address of 111.111.111.111).

UPnP doesn’t easily support this type of scenario. If you have access to both routers, port forwarding should be set up on both (https://portforward.com/help/doublerouterportforwarding.htm).

With the release of NoMachine Network this won’t be necessary. You can read more about this upcoming functionality here: https://www.nomachine.com/FR07J02731.

[username]

Seems like your suggestion is true because the name of my internal ip starts on 10.0.0.0 . I already requested to my provider about my issue and waiting for response.

[username]

The problem was solved. My provider has assigned me a public IP directly at my router, so now my router doesn’t displays IP 10.0.0.0 as my IP, instead of this it displays my public IP. But on my router the function of port forwarding still has a crucial value on availability of connection.

[Author]

Posts