Monday, April 02, 2012 10:21 PM
I didn't find an answer for my question after search so I would like to get some help here.
I have a Windows 2008 R2 RD Web Access and RD Gateway set up on the same server. I use a commercial SSL certificate for RDWeb publish via TMG 2010. My goal is to use a single DNS domain name to access the RDweb applications internally and externally. For example, I want to use "rdservice.company.com" for both internal and external use. So far, here is what I did:
1. Internally, I can use "rdservice.company.com" to access RD Web access. I don't have to type "rdservice.company.com/rdweb". That is easy to achieve since it is just a default page for site redirection under the IIS default web site.
2. For external usage, I set up a publish rule on TMG 2010 to publish "/rdweb/*" and "/rpc/*" paths under "rdservice.company.com", I can use "rdservice.company.com/rdweb" to get RD Web Access from Internet. I also set up the listener in TMG rule to allow HTTP redirection to HTTPS.
So, everything appears works fine for me. However, I just can't use "rdservice.company.com" to access RD Web Access from Internet. If I try "rdservice.company.com", I got the error: "The Page cannot be display. Error Code: 403 Forbidden. The server denied the specified URL. Contact the server administrator (12202)"
My question is: if we have published "/rdweb/*" and "/rpc/*" paths under "rdservice.company.com" site, what else should I do in TMG rule to publish the IIS default web site "rdservice.company.com" so that the traffic will be redirected to "rdservice.company.com/rdweb"?
Does anyone achieve such requirement? It would be nice if I can do that so users only need to remember "rdservice.company.com". They don't have to care about "rdservice.company.com/rdweb" or if they should type http/https.
If someone can provide some guidance on this, it will be greatly appreciated.
Tuesday, April 03, 2012 4:34 AM
copy the pubblishing rule for RDWEB, place this rule above the RDWEB publishing rule and change the action to deny and redirect to /RDWEB. In the path option of the publishing rule remove all path and add / as the path. It is the same as /OWA redirection:
regards Marc Grote aka Jens Baier - www.it-training-grote.de - www.forefront-tmg.de - www.nt-faq.de
- Marked As Answer by ddchn Tuesday, April 03, 2012 5:10 PM
Tuesday, April 03, 2012 9:03 AM
Please check this link, http://www.msserverpro.com/view/1178
I hope this will help you.
Best Regards, ----Naresh Man Maharjan,Nepal---- www.msserverpro.com
- Marked As Answer by ddchn Tuesday, April 03, 2012 5:11 PM
Tuesday, April 03, 2012 5:12 PMThanks Marc. That fixed the problem!
Tuesday, April 03, 2012 5:13 PM
Thanks Naresh. That fixed the problem!