[squid-users] Issue with NTLM/Exchange in squid-3.0

Hi list,

I am investigating a problem with squid and Exchange at the moment. We are using a self-compiled squid-3.0.stable15 and people can not use Exchange OMA/OWA through the squid proxy. It does not display a login prompt, the page that is returned by Exchange shows a "HTTP Error 401.2".

Using a squid-2.7.stable5 rpm from a SLES11 server does not show this behavior. The OMA/OWA is accessible through the proxy.

--
Squid Cache: Version 2.7.STABLE5
configure options:  '--prefix=/usr' '--sysconfdir=/etc/squid' '--bindir=/usr/sbin' '--sbindir=/usr/sbin' '--localstatedir=/var' '--libexecdir=/usr/sbin' '--datadir=/usr/share/squid' '--mandir=/usr/share/man' '--with-dl' '--with-maxfd=4096' '--with-valgrind-debug' '--enable-snmp' '--enable-carp' '--enable-auth=basic digest negotiate ntlm' '--enable-basic-auth-helpers=LDAP MSNT NCSA PAM SMB YP getpwnam multi-domain-NTLM' '--enable-ntlm-auth-helpers=SMB fakeauth no_check' '--enable-digest-auth-helpers=ldap password' '--enable-external-acl-helpers=ip_user ldap_group session unix_group wbinfo_group' '--enable-ntlm-fail-open' '--enable-arp-acl' '--enable-htcp' '--enable-underscores' '--enable-stacktraces' '--enable-delay-pools' '--enable-useragent-log' '--enable-referer-log' '--enable-forward-log' '--enable-multicast-miss' '--enable-ssl' '--enable-cache-digests' '--enable-auth-on-acceleration' '--enable-storeio=aufs,coss,diskd,null,ufs' '--enable-linux-netfilter' '--enable-removal-policies=heap,lru' '--enable-icmp' '--with-samba-sources=/usr/include/samba' '--enable-large-cache-files' '--enable-x-accelerator-vary' '--enable-follow-x-forwarded-for' 'CFLAGS=-march=i586 -mtune=i686 -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fPIE -DLDAP_DEPRECATED -fno-strict-aliasing' 'LDFLAGS=-pie'
-- 
Using a self-compiled squid-2.7 on Solaris 10 with the following options, works as well (login to Exchange is ok).
--
configure options:  '--enable-icap-client' '--enable-ssl' '--prefix=/apps/squid-3' '--enable-storeio=aufs' '--with-aio-threads=N' '--enable-removal-policies' '--enable-snmp' '--enable-icmp' '--enable-htcp' '--enable-cache-digests'
--
Using a squid-3.1 (3.1.0.15) on Solaris10 with the same options as above works (login to Exchange is ok).
--
configure options:  '--enable-icap-client' '--enable-ssl' '--prefix=/apps/squid-3' '--enable-storeio=aufs' '--with-aio-threads=N' '--enable-removal-policies' '--enable-snmp' '--enable-icmp' '--enable-htcp' '--enable-cache-digests'
--
But using a squid-3.0.stable15/stable20 on Solaris10, same options - the Exchange server returns a "HTTP Error 401.2"
--
configure options:  '--enable-icap-client' '--enable-ssl' '--prefix=/apps/squid-3' '--enable-storeio=aufs' '--with-aio-threads=N' '--enable-removal-policies' '--enable-snmp' '--enable-icmp' '--enable-htcp' '--enable-cache-digests'
--
Is this a problem with connection pinning (http://wiki.squid-cache.org/Features/ConnPin), that has been re-implemented in 3.1? Any help appreciated. 
Regards,
Christian
P.S. Sorry for the broken mailer.
This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp