Link to home
Start Free TrialLog in
Avatar of James Parsons
James ParsonsFlag for Canada

asked on

Connect Through Remote Desktop Externally

I've forwarded port 3389 to the IP. I can RDP into the IP internally, but not externally using the external IP address. Comes up with an error: Remote desktop can't connect to the computer. Remote desktop may be disabled or the computer may be off.

As I said I can RDP into it from within the network no problem. There is an SBS 2003 server that is doing DHCP. The router / firewall is a CISCO RVS2000.
Avatar of motnahp00
motnahp00
Flag of United States of America image

It doesn't sound like your firewall is properly configured with the port forwarding rule.
Avatar of James Parsons

ASKER

I've configured the port forwarding in the 'Port Fowarding' Section for TCP and UDP ports 3389 to point to internal IP 192.168.10.200 (IP of the computer we want to connect to).
ASKER CERTIFIED SOLUTION
Avatar of amenezes0617
amenezes0617
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
From inside the network I just connect to the internet IP from the RDP tool. I launch it through mstsc through run.  When  I try it from outside with the IP and port (xxx.xxx.xxx.xxx:3389) i get the same result. Inside however it works.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Works on the inside. Must be the router. I'm currently updating the firmware. Anything else it could be?
I'm sorry, I mistyped the port. 3389 is the default. I don't think so, unless you have some weird firewall rule. Which OS are you running on the machine?
@amenezes "the default port 389"

The default port for RDP is 3389.
Yeah I knew what you meant. I tried 3389. Works inside but not outside. It's running XP Pro.
I would check the windows firewall just in case, make sure it's turned off all the way. I still think it's probably your router/firewall, but there's always a change it's the windows firewall too. From the outside you can also try a telnet xxx.xxx.xxx.xxx 3389 to see if it answers.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
@bedind I'm wondering if you have a point about the default route back to the internet on the server. Are you referring to the server that hands out the DHCP addresses, or the computer that we're trying to connect to through RDP? It has a static IP set on it.
Can you get to the internet from the machine that you're trying to connec to?
yes
I wonder if the router is pooched
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I'm not able to telnet to the IP on port 3389 or any port. I've re-added the rule, updated the firmware and rebooted the router. Strange...
Yeah, then your firewall is blocking it. Is your rule limiting the "from" range? If so, try opening it up to everyone just to test. As in from "any". I am not recommending you leave it like that, just as a troubleshooting step.
thought of a third-party app like TeamViewer?  TeamViewer
Here's a screenshot of the port forwarding rule.
PortForwarding.JPG
Looks pretty straight forward to me, the only thing I can think of is that if in one of those "Applications" drop down they offer a built in one for terminal services, or soemthing like that that you could try.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Do you have another machine iwth that IP maybe? THat is strange...
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi,

When you are trying the RD from the outside you are using the PUBLIC IP, right?

If you are only opening and forwarding ports on you router, you should be able to connect from the outside using the public IP.

Hope this helps
That is a great point, sometimes we assume the most obvious points...I think he got it working though.
I changed the static IP on the machine and it worked - could have been a duplicate IP I suppose.