Azure Pack Private Cloud RDP GateWay Configuration Console Access

Question

Hello,
We are in the process of deploying the Azure Pack Private Cloud and have run into an issue with configuration of the Console Access.  We have been able to successfully configure the Console to work internally but external access is not functional.  When
a user attempts to connect from Windows 8.1 to the RDP Console via the Remote Desktop Services Gateway they are seeing the error:
An Authentication error has occurred (code 0x607)
Internal access works flawlessly.
Environment: Windows Server 2012r2 Data Center, fully updated
Windows Azure Pack RTM - Distributed Installation - 7 VMs - wapadmapi1, wapadmauth1, wapadmprtl1, waptenauth1, waptenprtl1, waptenpriapi1, waptenpubapi1
System Center 2012r2 Components: VMM, Service Provider Foundation, SCORCH, SCOM
SQL Server 2012 Enterprise SP1 running on Server 2012r2
Hyper-V Failover Cluster 2012r2
Wildcard Certificate has been assigned and RDP Gateway/VMM/SPF/Hyper-V have been configured as per http://www.hyper-v.nu/archives/mvaneijk/2013/09/windows-azure-pack-console-connect/ (PS this article needs to be updated because the set-scspfvmconnectglobalsettings
cmdlet doesn't work on RTM) and http://technet.microsoft.com/en-US/library/dn469415.aspx
Thanks,
Rick

Answer 1

No problem Dennis, as noted in the two articles I referenced above:
http://www.hyper-v.nu/archives/mvaneijk/2013/09/windows-azure-pack-console-connect/  and http://technet.microsoft.com/en-US/library/dn469415.aspx
an RDP Gateway is required to connect the external user to the console access on the Hyper-V backend
server.  When the RDP file is downloaded it enables users to have more functionality than a standard RDP session and it also allows you access to internal resources, acting similar to a proxy.  I have checked the security logs and there is nothing
that jumps out at me.
Here is an excerpt from the logs:
The user "FedAuthDomain\FedAuthUser", on client computer "CLIENT_EXT_IP", met connection authorization policy requirements and was therefore authorized to access the RD Gateway server. The authentication method used was: "Cookie" and connection protocol
used: "HTTP".
The user "FedAuthDomain\FedAuthUser", on client computer "CLIENT_EXT_IP", met resource authorization policy requirements and was therefore authorized to connect to resource "HV_SERVER_INT_IP".
The user "FedAuthDomain\FedAuthUser", on client computer "CLIENT_EXT_IP", connected to resource "HV_SERVER_INT_IP". Connection protocol used: "HTTP".
The user "FedAuthDomain\FedAuthUser", on client computer "CLIENT_EXT_IP", disconnected from the following network resource: "HV_SERVER_INT_IP". Before the user disconnected, the client transferred 1254 bytes and received 1615 bytes. The client session duration
was 0 seconds. Connection protocol used: "HTTP".
I have removed the actual IP addresses from the logs but kept the user credentials that are being currently passed.  HV_SERVER_INT_IP = IP of Hyper-V Host, internal and CLIENT_EXT_IP = IP of client who is attempting to access.