CaGeN
asked on
Remote Desktop via RDWeb
Hi All,
I hope someone out there would be able to tell me where I'm going wrong.
We have :
•1 Windows 2008 AD/DNS/DHCP controller
•1 Windows 2003 DNS controller
•5 Windows 2003 Terminal Servers
Newly configured
1 Windows 2008 r2 server with the following services for remote access
•Remote Desktop Session Host
•Remote Desktop Connection Broker
•Remote Desktop Gateway
•Remote Desktop Web Access
With this we can RDP via the gateway server successfully and join any of the Terminal Servers.
Internally
We can access the RDWeb site https://domainname.com/rdweb
Login successfully
Select the Remote Desktop tab
Enter the DNS Terminal Server name
And vola!..
This does not work externally.
What have I missed out?
ALSO
In the meantime, I am also having problems getting the RDP application to work via the RemoteApp Programs tab.
I've been adding the /v:servername switch to the arguments area. This displays the fact that it's accessin the Gateway server and not the terminal server.
Regards,
Michael
I hope someone out there would be able to tell me where I'm going wrong.
We have :
•1 Windows 2008 AD/DNS/DHCP controller
•1 Windows 2003 DNS controller
•5 Windows 2003 Terminal Servers
Newly configured
1 Windows 2008 r2 server with the following services for remote access
•Remote Desktop Session Host
•Remote Desktop Connection Broker
•Remote Desktop Gateway
•Remote Desktop Web Access
With this we can RDP via the gateway server successfully and join any of the Terminal Servers.
Internally
We can access the RDWeb site https://domainname.com/rdweb
Login successfully
Select the Remote Desktop tab
Enter the DNS Terminal Server name
And vola!..
This does not work externally.
What have I missed out?
ALSO
In the meantime, I am also having problems getting the RDP application to work via the RemoteApp Programs tab.
I've been adding the /v:servername switch to the arguments area. This displays the fact that it's accessin the Gateway server and not the terminal server.
Regards,
Michael
ASKER
Hi Jsierra1,
It sounds like you're referring to the Remote Desktop Connection application.
If I create an Remote Desktop Connection (a .rdp file) with the gateway details inserted. This works fine externally so ports look fine for that service.
I am approaching this to enable our users to either :-
a. Use the icons I place onto the RemoteApp Programs area within RD Web Access
b. Use the Remote Desktop tab within RD Web Access to jump onto one of the internal terminal servers
It sounds like you're referring to the Remote Desktop Connection application.
If I create an Remote Desktop Connection (a .rdp file) with the gateway details inserted. This works fine externally so ports look fine for that service.
I am approaching this to enable our users to either :-
a. Use the icons I place onto the RemoteApp Programs area within RD Web Access
b. Use the Remote Desktop tab within RD Web Access to jump onto one of the internal terminal servers
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The SSO suggested link also worked a treat.
Try these steps from the client machine that is external:
Ping domainname.com
Verify that the name resolves to the correct external IP address
If name resolution is working then try
Telnet domainname.com 443
You’re testing to see if the port is open from the outside
if both fails then try the public ip address and see if it is accessible.