Quantcast
Viewing all articles
Browse latest Browse all 25135

Connect Remote Desktop Client to RemoteApp via Remote Desktop Gateway and a HTTPs Proxy with Authentication

We published an application as RemoteApp on a Windows Server 2008 R2. The clients must connect to this Remote Desktop Service over a firewall. So no open port for RDP exists. Now we installed the remote desktop gateway on the same server with the Remote Desktop Service. The gateway works well. We can connect via HTTPs and use the RemoteApp. But with these clients behind the firewall we have a problem. Near the firewall is a HTTP proxy. We can (und must) use the proxy to connect the Remote Desktop Clients to the remote desktop gateway. The problem is the authentication. The proxy wants a HTTP authentication (HTTP error 407).

If we use a Windows XP (with SP3), we can define the proxy and store the proxy credentials in the Internet Explorer. Now the Remote Desktop Client use this credentials, can connect to the RemoteApp and all ist okay.

But this doesn't work with Windows 7 (mstsc.exe version 6.1.7601). What must i do, to define the credentials in Windows 7?

We have testet it with NTLM authentification. In the production environment the basic authentification is used, too. The WinHTTP library, used in Remote Desktop Client, didn't use a basic authentification automatically. Is there a way to define the proxy credentials (including basic authentication) to use for the Remote Desktop Client in Windows 7?

Thanks and Greetings from Germany

M. Hoffmann-Vetter



Viewing all articles
Browse latest Browse all 25135

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>