[squid-users] RPC over HTTPS for Terminal Services Gateway

From: Andreas Adler <fox_at_foxrecbin.com>
Date: Mon, 24 Nov 2008 10:23:42 +0100

Hi there

I am running Squid 3.0 PRE6 as a reverse proxy for many applications and services. RPC over HTTPS for Exchange/OWA is running fine for a long time. Recently I tried to pass the TS Gateway through Squid, but this is giving me a very hard time. TS Gateway is using RPC over HTTPS just like Exchange does, but I always get an authentication error. Here is what I get:

--
TCP_MISS/401 399 RPC_IN_DATA https://server.domain.com/rpc/rpcproxy.dll? - FIRST_UP_PARENT/server.domain.com text/plain
--
Here is my access rule:
cache_peer server.domain.com parent 443 0 proxy-only no-query originserver front-end-https=on ssl login=PASS sslflags=DONT_VERIFY_PEER
Does anybody run a Terminal Services Gateway (TS Gateway) being proxied through squid?  Could there be something wrong with some NTLM passthrough? I am pretty clueless on this, so any help is very appreciated!
Thanks a lot!
Andreas Adler
Received on Mon Nov 24 2008 - 09:23:53 MST

This archive was generated by hypermail 2.2.0 : Mon Nov 24 2008 - 12:00:03 MST