Link to home
Start Free TrialLog in
Avatar of fatcontroller82
fatcontroller82

asked on

Remote Web Desktop Connection won't connect over the internet

Hi,

I hope you can help with this because I have tried everything and can't work out where i'm going wrong.

I have a small test environment which is made of the following:

Domian Controller
Exchange Server  - 2003 Sp2
BES 5.0
BES 4.1
BES 4.0

Each Server is running server 2003 standard Sp2. On the DC I have installed Remote Desktop Web Connection. In the properties of the default website in IIS Manager I have set the http tcp port to 8080 (as not to interfere with OWA on the exchange server).

I then have a Netgear DG834GT Router connected to the ISP which i have forwarded port 8080 and port 3389 to the LAN IP address of the DC which is hosting RDWC.

This is where the problems begin, I can get to the RDWC page from internally on the LAN and connect to any machine on network.

I can RDP to the DC from any machine on the internet using either the public IP address or the FQDN.

I can hit the RDWC landing page from any machine on the internet using both http://81.xxx.xxx.154:8080/tsweb or http://mydomain:8080/tsweb however when I put the wither the machine name or LAN IP address of a machine on the network I want to connect to it get the error message "The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try connecting again later. If the problem continues to occur, contact your administrator."

I have made sure as well that I have enabled remote connections on the DC as well as allowing 'allow log on through terminal services' in the domain controller security policy'

Can Anybody advise why this is not working?
ASKER CERTIFIED SOLUTION
Avatar of jorlando66
jorlando66
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
Avatar of fatcontroller82
fatcontroller82

ASKER

Ah OK makes sense, as it does work over VPN. I guess it will ne terminal services gateway I need since it is server 2003.

I will look into this tomorrow. Thanks for all your help