Slowly connect to Remote Desktop firstly through RD gateway

We setup a wildcard SSL certificate forone Remote Desktop gateway server and some Remote Desktop Servers.

At the first connection from a windows client to a remote Desktop server through RD gateway, it always takes about 45-60s for a wan client to logon the Remote Desktop Server. After this first connection setup successfully, it will be very fast for the same client connecting through RD gateway with about 10s.

We use the command “netstat -n” to check the connection status in RD gateway, and find that when firstly connecting from a client to a Remote Desktop Server through RD gateway, a 80 web access (182.50.136.239:80) will take place in this RD gateway. This access will last for about 40s, after which the client will setup connection to Remote Desktop successfully. When there is not this access, the connection time will be only about 10s.

We check the 80 web access and find this IP address maps to crl.godaddy.com. This access is mainly for checking crl updating.

Then we search in google and want to shut off this crl checking. We tried several tests from some posts.

1. In http://serverfault.com/questions/404156/how-can-i-disable-crl-checks-for-a-windows-2008-app-using-winhttp, we set the registry keys in RD gateway. These registry keys are：

But this access still takes place.

2. We also set the hosts file in RD gateway with crl.godaddy com mapping to 127.0.0.1. The 80 web access to Godaddy still exists.

3. We also tried to block 80 output accesses in RD gateway firewall, but it also does not work out.

We tried these tests in both windows server 2008 and windows server 2012 RD gateway having the same results.

This problem troubled us for a long time,but we still can notsolve it effectively, the user experience is very bad. How can we shut off this web access to crl.godaddy.com in RD gateway? How can we make the connection from a wan client to Remote Desktop through Gateway server fast?