Member Avatar for xav.vijay

Hi

I have Windows 2003 server at home. I want to access this machine from the internet.
Instead of opening port 3389 to the internet, I would like to have it accessed via the RDP web connection. So I installed IIS... created a self signed SSL.
Withing the network at home, when I use I get the RDP web page..and when I enter the IP of the machine...I can login...working fine... no problems with that....

But from the internet, I am not able to do the same. I have opened port 443 b/w router and the Win2000 box.
From the internet I get the same RDP web page...but when I enter the IP of the machine or the router IP (this I saw in some website).. to connect, I get the following error.

VBScript: Remote Desktop Disconnected
The client could not connect to the remote computer. Remote connections
might not be enabled or the computer might be to busy to accept new
connections. It is also possible that network problems are preventing your
connection.

What am I missing here?

Regards

Xavier

Edited by xav.vijay because: n/a
  • 2 Contributors
  • 4 Replies
  • 272 Views
  • 9 Hours Discussion Span
  • Latest Post Latest Post by xav.vijay

Dani AI

Generated

A few clarifications and practical steps that follow on from what and have already described.

The TS/Remote‑Web page you see in the browser only delivers and launches the Remote Desktop ActiveX/RDC client — the actual RDP session is started by the client machine (the browser/ActiveX control) and must be able to reach the server’s RDP listener. That is why serving the web page over HTTPS alone won’t make a remote desktop session succeed if the client cannot open a direct RDP path to the target host. (learn.microsoft.com)

To diagnose quickly:

  • On the server check the RDP listener and service:
    netstat -an | findstr 3389
sc query termservice
  • From an Internet client test reachability to the public address/port (replace <public-ip>):
    telnet <public-ip> 3389
# or in PowerShell
Test-NetConnection -ComputerName <public-ip> -Port 3389

    If these fail, the RDP flow from the Internet to your internal machine is being blocked or not forwarded. The Microsoft KB article on Terminal Services troubleshooting shows the same listener/tests and how to interpret results. (learn.microsoft.com)

If you cannot (or do not want to) expose RDP directly, these are safer alternatives:

  • VPN into the home network and then use RDP as if local (recommended).
  • Publish an RDP gateway (TS/ RD Gateway) that tunnels RDP over HTTPS so clients only need TCP/443 to reach the gateway, which then forwards to internal hosts. That is the supported Microsoft solution for tunneling RDP over SSL. (itprotoday.com)
  • If router features are too limited, consider a reverse‑tunnel/VPS or a managed remote‑access tool instead of opening ports on a cheap consumer router.

Quick checklist: ensure RDP is enabled on the server, the server has a fixed LAN IP, local firewall permits the RDP listener, verify router/NAT mapping or use a VPN/RD Gateway, and review the Term* event logs on the server for specific error IDs when a connection is attempted. (learn.microsoft.com)

Recommended Answers

All 4 Replies

Member Avatar for Freaktech

RDP Web Connection still requires port 3389 to work. All it does is run the RDP in a browser window via ActiveX rather then it's own program. The easiest way to do what you want is to pick a random port and forward that port to 3389 and your server IP.

Member Avatar for xav.vijay

:( ... port 3389 is not open from office ... i didn't want to open 3389 to internet... looks too exposed to me...
Well.. Thanks anyway... at least i can stop meddling with this anymore...

Member Avatar for Freaktech

You don't have to open port 3389. Open a random port and then forward that port to 3389 on the inside.

Member Avatar for xav.vijay

My simple home router doesn't have that provision. :(

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.