clundberg

No we are not working over a VPN.

May I ask you to describe your setup with the gateway?Not quite sure what to say. We have Resource Authorization Policies that allow users to the different Terminal Servers. Our gateway is gatewayname.betahg.com and our internal servers are TSservername.bhgdom.local.

Are you using separate credentials for the Gateway and the remote session?No I am using the same credentials for both

What version of windows are you connecting to?The Gateway is Windows 2012 R2 Standard and the Terminal Server is Windows 2008 R2 Standard SP1

Are you suing any certificate?We have a wildcard cert so when I connect using Microsoft Remote Desktop our Gateway has the correct certificate but our internal server gives us a warning: “The given hostname does not match the hostname in the server’s certificate” I click Continue and then I can log on.

I downloaded the latest and it's still not working. It seems like it isn't even looking at the gateway since it tells me "Unable to connect to host" and the host listed is my server behind the gateway. I tried using Microsoft Remote Desktop and I can get through so I know the problem isn't on our side. Any hope for being able to use this?

Any idea on when this might be fixed?