how to open port 3389 on DIR-655

check the manual here

http://www.dlink.com/us/en/home-solutions/connect/routers/-/media/Consumer_Products/DIR/DIR%20655/Manuels/DIR655B1manual070312v23pdf.pdf

Look at port forwarding section

Follow the steps mentioned in this link
Just replace it your port number and application.

http://www.cctvcamerapros.com/D-Link-Port-Forwarding-s/286.htm






Ded9

Here is another link to port forward Remote Desktop.

http://portforward.com/english/routers/port_forwarding/Dlink/DIR-655/Remote_Desktop.htm

It sounds like you already have it setup correctly.
i.e. that site *should* say
Success: I can see your service on
your.ip.addr.ess on port (3389)
Your ISP is not blocking port 3389

If you mean how do you make it work, from the remote site when prompted for the machine you want to connect to in Remote Desktop, you enter
yourcustom.DDNS.domain
as the remote computer then click Connect...

To enable Remote Desktop inbound, click the 'start' orb, type in sysdm.cpl and click the one that appears at the top, under Programs (1).
Go to the Remote tab
Pro, Enterprise and Ultimate will look like Home Premium, Home Basic and Starter versions will look like XP Pro looks like (Start->Run, sysdm.cpl [Enter]) - sorry, I don't have a copy of XP Home to get a screen shot.

When making those settings above with Windows Firewall enabled, it should automatically open TCP port 3389 in the firewall for you.e.g.or, in XP
If Windows Firewall was disabled at the time it WON'T automatically make the opening... in that case, enable the firewall, disable remote access on the Remote tab, Apply/OK, then re-enable remote access on the Remote tab and it should make that opening on port 3389 for you in Windows Firewall.

If using a 3rd party firewall, consult its documentation for opening TCP 3389 inbound.

Note that you should be able to make a Remote Desktop Connection to any version of Windows like that, but to initiate a Remote Desktop Connection you must be on a Professional or higher (e.g. Enterprise or Ultimate) version of windows.

edit: Hmmmm - I always thought that last statement was true, but I was just able to make a connection *from* Win7 Home Premium to a remote XP Pro machine, and I don't remember doing anything special to enable that.

Thank you for all of the answering but i still can't remote to the server by the DDNS name but i can remote it by IP Address, if i'm in the LAN Network.

The think that i have done from the previous comment is:
Fig.1.png
Fig.2.png
Fig.3.png

I think you should have distrubutd the point we all helped here

Looking at the screenshots - I think you also need to enable the RDP port in the "firewall section settings of your router" -That is probably why it works on internal Ip but not externally?

ie. The port forwarding rule marks where to pass the traffic but the firewall is not allowing the inbound traffic on that port to be passed ?

In fig2.png, you're forwarding TCP 3389 on the outside to UDP 3389 on the inside (should be TCP 3389 on the inside, too).

Since your router's port forwarding allows specifying different outside and inside ports (not all do), you don't *need* to change the port RDP listens on in the registry... just change the outside port on the router, to, say, TCP 33344, and the inside port to TCP 3389... then when you tell Remote Desktop where to connect, use

yourcustom.DDNS.domain:33344
and click Connect.
The router should then forward that to 192.168.0.44 TCP port 3389 on the inside.
Then you could forward a different outside port to a different inside IP address on port 3389.

The registry change to make RDP listen on a different port is to allow multiple windows computers to be accessed remotely on the routers that DON'T allow specifying different outside and inside ports in their Port Forwarding setups, not to make Remote Desktop more secure.
You make Remote Desktop secure by employing 7+character complex passwords that use mixed-case letters, numbers and symbols (like !@#$% et al). If you use a 10-character complex password, composed of the 94 characters allowed in passwords by windows, a hacker trying 5,000,000 combinations per second would take over 3 trillion millennia to go through every combination.

Fully agree with the above
I was Just keeping it simple by changing the port on the server rather than port mapping on the router (you will note I did not have the benefit of the screenshots in my original post)

But as I have pointed out this still  needs the firewall to pass the packets however the forwarding is set up

(Your stats  assume the hacker does not get lucky first time or use social engineering to trick the user into revealing even the most complex password,etc)

Personally I use 8+ digit passwords with complex symbols and alpha numerics