J_Worth Posted September 6, 2012 Posted September 6, 2012 Hello everyone, We have the following setup for our terminal server environment: SERVER-TSG: RD Gateway RD Licensing RD Connection Broker RD Web Access SERVER-TS1: RD Session Host SERVER-TS2: RD Session Host We are finding that when connecting to a "full" remote desktop connection it hangs on Configuring Remote Connection for about 1-2 mins before actually connecting. This is also the same when launching a RemoteApp. We have configured our certificate on all of the servers and we are not getting any certificate errors. We have a dns record: RD-FARM.SCHOOL.LA.SCH.UK which points to both of the session hosts. Our main question is: Is there anyway of reducing the amount of time it takes for a remote desktop connection to be established? Thanks in advance! J.Worth
pritchardavid Posted September 7, 2012 Posted September 7, 2012 Were having the same problem too, im thinking its to do with the ssl certificate. Were using a wildcard from ipsca which is free for education. But what im noticing is most computers don't seem to find the level 1 certificate for ipsca. Thinking it may have to be a paid certificate. Or would this be a different problem? Sometime we even have problems remoting onto the servers when needed.
J_Worth Posted September 8, 2012 Author Posted September 8, 2012 We have a wildcard SSL certificate from GlobalSign and from what I am aware of - we have no problems with the certificate
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now