• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 581
  • Last Modified:

Remote Desktop Web Access

BACKGROUND
Have new Remote Desktop Server Deployed (2008 R2)
Properly Licensed.
Can access via RDC client inside and outside of firewall.
Have RD Gateway in place
Have Cert Installed (Actual SSL Cert not self signed).

If I run RD Web Access Manager it takes me to the login page for RD.

When I try to connect via a browser https://gateway.myclientsite.com it takes me to the IIS home page not the RDC login page.  I don't understand why this is happening or how to fix it.

I'm not very IIS literate so be gentle.
0
tech911
Asked:
tech911
  • 8
  • 3
  • 3
1 Solution
 
IanThCommented:
iis is using port 80 and so is webrdp
0
 
IanThCommented:
you will also need to configure your router I think
0
 
tech911Author Commented:
Sounds plausible...what changes need to be made and where?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
tech911Author Commented:
I thought that by using https:// I would be connecting over port 443 not 80, am I missing something?
0
 
jonyeltonCommented:
You are suppose to login into the rdgateway, and then the rdgateway forwards you to t he right rds server.

Based on the way you are talking, I don't think you want a rdgateway server.  Instead you want to enable rd access.  If that's the case, you add it via the roles and features, and configure your ports in the firewall to forward to your rds server.

http://technet.microsoft.com/en-us/library/cc731923.aspx
0
 
jonyeltonCommented:
Oh, if you want to keep the gateway server, make sure you have the users assigned to a rd server or vdi.  The gateway server should not be the rds server.
0
 
tech911Author Commented:
Sorry my description is so lame.
Let me try again

As it stands right now I can...

Open browser
type in https://gateway.myclient.com
Remote Web Page is displayed (this is good).
Enter domain\username, Enter password
Logs me in, I am presented with the page that has the remote desktop icon on it, at the top it says "Remote Desktop Services Default Connection"
When I click the Remote Desktop Icon, I get a message that says

This computer can't connect to the remote computer.  Remote Desktop cannot find the remote computer. Type the computer name or IP address again....

If I log into the remote server via rdp, then...
Open browser
type in https://gateway.myclient.com
Remote Web Page is displayed (this is good).
Enter domain\username, Enter password
Logs me in, I am presented with the page that has the remote desktop icon on it, at the top it says "Remote Desktop Services Default Connection"

I click the Remote Desktop icon, it asks me for a username and password.
I enter domain\username and password, click OK
It acts like it is connecting, then stops and says, Access Denied.

Basically it seems like it is not being allowed to log into the remote server...

Thanks for the help.
0
 
tech911Author Commented:
Looked at it, and everything looks correct, see screen shot.
Sal-IIS-ScnShot1.jpg
0
 
tech911Author Commented:
More info that may be helpful...

If I go to the clients office, it works from inside the office just like it is supposed to, perfect.

If I use it outside the office, that is when it doesn't work.

Thoughts?
0
 
tech911Author Commented:
Screen Shot

Here is the error I get... See Screen Shot Attached
Sal-RDP-Error-Connection.jpg
0
 
jonyeltonCommented:
What is the IP address configured for?  It's possible that you have the server pointed towards an internal IP address and not an external.  That would be the reason for it to work inside by not outside.

What IP address is your terminal server configured for?
0
 
tech911Author Commented:
After reading a ton of posts (like 4 hours worth).
Looking at various solutions
Trying various solutions, I figured it out.

When you install and setup the "Application Server" (Using the Remote App Manager) it automatically uses the internal name of your RD server (read: NETBIOS NAME) for your RD Session Host Server.  In order for this work from both inside and outside your RD Session Host Server must have the same name as your external FQDN.

So your app server should not be named InternalRDServer, but should instead reference your external link  rdserver.myclientsdomain.com

This will fix the problem.
0
 
tech911Author Commented:
This provides detail info on the fix to this configuration issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 8
  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now