Remote Desktop accross WAN command line?

[kingull]

I can Remote Desktop Connect accross my LAn using Belkin Wireless router.
I have this working from Internet Explorer and by normal Remote Desktop
Shortcut.

Every article including Microsofts bulletins do not show precisely how to
connect over the internet.

Would appreciate some help. Thanks in advance.

 

[Shenan Stanley]

I can Remote Desktop Connect accross my LAn using Belkin Wireless
router. I have this working from Internet Explorer and by normal
Remote Desktop Shortcut.

Every article including Microsofts bulletins do not show precisely
how to connect over the internet.

Would appreciate some help. Thanks in advance.

Configure your wireless router to forward the proper port to the proper
machine (port 3389 by default) and know your external IP (the one your
router gets from your ISP) and utilize it to connect to the machine(s)
behind said router whenever you are not behind it.

 

[kingull]

I know all that and have configured the Belkin Wireless router to open port
3389.
have even amended the registry to try port 5800.
It makes no sense to me to type in, for example: 192.168.2.2:3389 when
thousands must use that address. I have tested it using my WAN tcpip:3389 and
just about everything else. It seems that no one can provide a logical answer
to my question.

My current WAN is 61.68.100.160 ISP (Domain aapt.com 69.25.142.48 current),
My network gateway is 192.168.2.1 IP address 192.168.2.3 with computer name
kingul and user name franko. So how do i assemble that to run RD?

 

[kingull]

No point in asking the experts as they do not know how to answer a question.
The answer to my question is quite simple. (BY TRIAL AND ERROR)
WAN ADDRESS:3389 (NOT LOCAL LAN CARD ADDRESS AS GENERALLY INDICATED)
BELKIN ROUTER ( SERVER) AMENDED TO COMPUTER NAME:
DOMAIN :: "kingul"
ROUTER SERVER SET TO OPEN PORT 3389 ON LAN CARD ADDRESS (NOT GATEWAY)
FIREWALL SET TO OPEN PORT 3389 FOR ALL ENTRIES.(UDP AND TCP)
RUN TEST ON CAN YOU SEE ME (PORT CHECK ON 3389)
http://www.canyouseeme.org/
If page shows success, Remote desktop works WAN\tcp:3389 (not LAN)

 

[Shenan Stanley]

http://groups.google.com/group/micr...e5700ab4444/4b3da6923b6437b9#4b3da6923b6437b9

I can Remote Desktop Connect accross my LAn using Belkin Wireless
router. I have this working from Internet Explorer and by normal
Remote Desktop Shortcut.

Every article including Microsofts bulletins do not show precisely
how to connect over the internet.

Would appreciate some help. Thanks in advance.

Configure your wireless router to forward the proper port to the
proper machine (port 3389 by default) and know your external IP
(the one your router gets from your ISP) and utilize it to connect
to the machine(s) behind said router whenever you are not behind it.

I know all that and have configured the Belkin Wireless router to
open port 3389.
have even amended the registry to try port 5800.
It makes no sense to me to type in, for example: 192.168.2.2:3389
when thousands must use that address. I have tested it using my WAN
tcpip:3389 and just about everything else. It seems that no one can
provide a logical answer to my question.

My current WAN is 61.68.100.160 ISP (Domain aapt.com 69.25.142.48
current), My network gateway is 192.168.2.1 IP address 192.168.2.3
with computer name kingul and user name franko. So how do i
assemble that to run RD?

No point in asking the experts as they do not know how to answer a
question. The answer to my question is quite simple. (BY TRIAL AND
ERROR)
WAN ADDRESS:3389 (NOT LOCAL LAN CARD ADDRESS AS GENERALLY INDICATED)
BELKIN ROUTER ( SERVER) AMENDED TO COMPUTER NAME:
DOMAIN :: "kingul"
ROUTER SERVER SET TO OPEN PORT 3389 ON LAN CARD ADDRESS (NOT
GATEWAY) FIREWALL SET TO OPEN PORT 3389 FOR ALL ENTRIES.(UDP AND
TCP)
RUN TEST ON CAN YOU SEE ME (PORT CHECK ON 3389)
http://www.canyouseeme.org/
If page shows success, Remote desktop works WAN\tcp:3389 (not LAN)

Actually - if you read my answer - it told you what you have pointed out...

Quoting my answer:
"... know your external IP (the one your router gets from your ISP) and
utilize it to connect to the machine(s) behind said router whenever you are
not behind it."

And there is no need to put 3389, as that is the default port used. So when
utilizing the RDP client - port 3389 is assumed unless you ammend the IP
address with the colon and another port number... (Yes - you have to
forward the port through the router and open any local firewalls to allow
port 3389 traffic through.)

Not sure how you missed it and then decided you came up with it on your
own - but glad you figured it out.