Can't get WAN to work

[juanpg]

Hello,

First thing, congratulations on a great product! This thing is amazing. I've been using it on my local network with no problems, and it really works great. Now, I want to use it remotely, but I'm missing something.

I have my PC on an ethernet connection, with a fixed IP set, and I'm using Remoter version 2.4.1 on an iPad2.

I have open in my router ports 5900 and 9.



I have a password set to use VNC, using UltraVNC, like this:



and I checked that the port is being opened with canyouseeme.org



The WakeOnLan works just fine. But when I click on "Start", I get the "Disconnected" error. (Host: XXX.XXX.XXX.XXX" Port:5900 Unable to Connect to server. This usually indicates the computer is not reachable in the current network..."

I tested again with http://www.gotomyvnc.com/, and it works

Checking you out at IP address "186.112.XXX.XXX"...

186.112.XXX.XXX is accepting connections on Display 0 (TCP port 5900).

186.112.XXX.XXX is not responding on Display 1.

186.112.XXX.XXX is not responding on Display 2.

186.112.XXX.XXX is not responding on Display 3.

186.112.XXX.XXX is not responding on Display 4.

186.112.XXX.XXX is not responding on Display 5.

186.112.XXX.XXX is not responding on Display 6.

186.112.XXX.XXX is not responding on Display 7.

186.112.XXX.XXX is not responding on Display 8.

186.112.XXX.XXX is not responding on Display 9.

Scan of "186.112.XXX.XXX" is complete.

Hit 'reload' or 'refresh' in your browser to scan again.

Is there something else that I need to do? I don't get why the WakeOnLan is working, but not the connection itself...

I have registered with No-Ip.org as well, but I can't get it to work either with the external IP or the no-ip hostname.

[raf]

Hi juanpg!,

Looks like you're doing everything exactly right.
The only reasons that you might have problems that I can think of are that you're not using your public IP (or dyndns) in Remoter, or that somehow your iPad doesn't have connectivity.
Could you double-check your public IP address (the 186.x.x.x.x one) in Remoter's "VNC Hostname" field? Make sure there are no extraneous characters there. In fact, I would suggest creating a whole new session to make sure everything is OK.

Thanks,

Raf.

[juanpg]

Thanks Raf,

Still no luck. What I wish I knew is if its a PC setting, or a router setting. Am I correct in thinking that if I set the VNC hostname to 192.168.1.1 (The router's address), that it should connect me to my PC because of the port forwarding?

[raf]

Hi juanpg,

No, you shouldn't use the router's LAN ip (that is the internal, local ip used to access the router from within the LAN). You need to use your actual public IP address, the one you get when you go to http://whatismyipaddress.com/ . That's why I recommend using a service like dyndns; this way you don't use an IP address, but rather a text hostname, which updates if your public IP changes.

Raf.

[juanpg]

Hi Raf,

Well, it works externally, as long as I'm connected to an external network as well. I have no clue why it doesn't work when I'm using my own network, but I guess for that I can continue to use the connection through LAN. It makes it hard to test, especially yesterday when I was setting up SSH.

[raf]

Hi Raf,

Well, it works externally, as long as I'm connected to an external network as well. I have no clue why it doesn't work when I'm using my own network, but I guess for that I can continue to use the connection through LAN. It makes it hard to test, especially yesterday when I was setting up SSH.

I recommend you have two separate sessions in Remoter, one for when you're home, and one for when you're out.
That helps simplify this.

Raf.

[juanpg]

Yes, that's exactly what I have. One connects directly through VNC, the other connects through SSH.