Hello there,
Urgent attention is needed here-
I have one 2012 server runnning RD webaccess, RD gateway, RD connection broker and another 2012 server running RD virtualization host with HYper-v. I have published webaccess and gateway via TMG using the web publishing rule and allowed /* in the path. I can access RD webaccess URL from internet and can see the published desktops, but when I click on it it throws error-
Kindly note that I am using split namespace, it means my internal domain is the child of public domain. One thing I am getting confused.....when I click on published desktop....it gives me a untrusted verifier dialog box (I am using internal certs) and there i could see the RDgateway name as - RDgateway.internal.domain.com? shouldn't his be issue as this domain namespace is not public ...only "domain.com" is public and thus name resolution failing for rdgateway?
This is only my assumption as I have no idea how rd web access server redirects to rd gateway...??
Also sometime I can't login to rdweb access url..it keep prompting me for creds..?
Kindly note that I am using virual desktop pooled infrastructure and not using session based deployment. Thus I don't have RD session Host server, is this role still necessary if I am using virual machine based deployment?
Please help
MCTS|MCSE|MCSA:Messaging|CCNA