Hi,This is an annoying problem...Basically, we have some Windows 2008 R1 servers running a Terminal Server Farm. This farm is setup with certificates containing the externally published computer names and is accessed via TS Gateway.However, if I try the RDC in Windows 7 internally, it absolutely refuses to allow me to connect because our internal name does not match the public name on the cert.It seems crazy to disallow this point blank with no option to continue. I really don't care if our internal system names don't match and upset Windows 7, I should be still be allowed to over-ride and connect to my own servers.I have to go back to XP or a Windows 2003 server to do this now and I am certainly not redoing all of our security certs to address this!Does anyone know how to get around this? That is, force Windows 7 to allow an RDP connection if it does not like the cert?Cheers,Rob

I "fixed" this by removing our ts-gateway cert from each terminalserver in the farm in rdp-tcpprops and setting the cert to "auto generated". This does not affect ts-gateway and then Windows 7 is ok internally. This is odd as the documentation suggests that this cert is used for encryption only, not for securityverification purposes.Can I please request that the Windows 7 RDC have an option to over-ride cert errors if required? It's quite dumb to deny all ability to connect when you know the remote system is perfectly ok (ie, a server you are trying to administer on your own internal network).Thanks,RobP.S. Vista and 2008 R1 have the ability to over-ride this.

Aaargh! Now Windows 7 won't let me connect because the name I specified does not match the server I tried to connect to! Of course it doesn't, Microsoft, TS-Gateway is redirecting me to the next available server!Honestly!