This is a great write-up, which I now understand (I think) so thanks for that .RifRaf wrote:port forwarding is used to send the traffic on port :2233 from your routers LAN IP address to your servers lan IP address, this has nothing to do with the no-ip.org service. An example might be from 10.0.0.1:2233 (Router LAN IP) forwarded to 10.0.0.2:2233 (The internal IP of machine with Monkey Server)
the no-ip.org service is used to redirect traffic to your routers WAN IP or its internet IP address and is not essential for being able to access externally. The no-ip.org service needs to know your external IP address of router to be able to do this. You can then ccess your server using the no-ip.org domain name rather than the Routers WAN IP address. An example might be , your router has external ip of 18.104.22.168 so you could access your machine externally with the address http://22.214.171.124:2233 and if the port forwarding above has been configured you will access your monkey server externally. After setting up a no-ip.org account that redirects to your wan address you could use the addresss http://yourusername.no-ip.org:2233 to access the server externally (no-ip redirects the traffic from yourusername.no-ip.org to 126.96.36.199 for you so you don't need to remember the ip)
I am tryting to take this one step at a time...forgetting about no-ip for now...what I did was access my router (D-Link DIR-655) via my browser via http://10.0.0.1 (to use your illlustrative example) and under advanced settings, I added an entry for port forwarding using 10.0.0.2 (the internal IP of machine with Monkey Server) specifying port 2233. I rebooted the router (and verfied again the port forwarding was there), but when I enter http://10.0.0.1:2233 in my browser I get nothing( ie bad page) -
what step am I missing??