certificate revocation check fails

[alastair]

When using remote desktop on windows 7, and remoting into a server 2008 R2 machine, I get the message " certificate revocation check cannot be performed " The certificate is installed correctly, and works for windows 2003 servers, I've checked the security settins on the server, but can't find anything wrong, remoting in from windows xp machines work fine. How does certificate revocation check work, and do I need to allow access to a particular website through our firewall? If this is the case, what is the URL, and what ports does it need for revocation checks to work. The failure only occurs from within our organisation, and we access the internet through an isa server proxy, with a 10 min session timeout. remoting into the server from outside the organisation from a windows 7 macine works fine, so I can only assume it's something to do with internet access.

 

Has anyone any ideas?

[jamesb]

Where is the Certificate Revocation List actually held for your setup?

[benIT]

I am having the same issue as Alastair- Did you find a fix?

 

thanks

 

Ben

[alastair]

After extensive research, and a support call to comodo, who our wildcard certificate is with, I've finally cracked this issue. Firstly the problem is not with the certficate, or with remote desktop configuration. The RDP client app uses, winhttp protocol to connect, and check certficates, winhttp, by default doesn't use proxy settings. so here's the solution. open a command prompt on the machine you want to connect from, then type netsh, at the new prompt type winhttp, then type "import proxy source=IE". an alternative is to type the whole command " netsh winhttp import proxy source=IE, that's it job done, the only thing I've found is that you still need to log onto the internet before you try the remote desktop connection. As of yet I haven't found a way to set the proxy credentials using the winhttp command, but I'm sure there's a way of doing this. NOTE: if you're not using Internet explorer to access the internet, then set your proxy details in IE before you import them, including your exceptions list, otherwise you will just be importing blank proxy details. Hope this helps. I found the information after comodo responded with a link to a similar problem for exchange, the link it took me to suggested this site for reference Configure Proxy Settings for WinHTTP: Exchange 2010 SP1 Help