Squid 3 - Exchange 2013 SP1
-
in squid 3.3 (beta) there will be passthru auth implemented (which means you can pass all types of auth to the backend) :)
-
It's negotiate (if I remember correctly)
What could be a very (but very) good thing is to easily block the ECP ! (it's not that simple)
I'm eagerly awaiting for that new package !
-
The package is here !!! :D
-
Just to be curious, are you running an exchange dag ?
-
Nope it's just for my lab for the moment
BUT
It's one of my many project …The question about the DAG is because there is only one IP adress in squid RP ?
-
No,
As the reverse ip, just put the dag ip.
Just asked bacause of a config question ;-) -
ok
I have an issue with the update
Jun 7 14:30:49 squid: Bungled /usr/pbi/squid-amd64/etc/squid/squid.conf line 82: cache_peer 192.168.0.4 parent 80 0 proxy-only no-query no-digest originserver login=PASSTHRU round-robinname=rvp_xxx_80
Jun 7 14:30:49 php: rc.start_packages: The command '/usr/pbi/squid-amd64/sbin/squid -f /usr/pbi/squid-amd64/etc/squid/squid.conf' returned exit code '1', the output was '2014/06/07 14:30:49| parse_peer: token='round-robinname=rvp_xxx_80' FATAL: Bungled /usr/pbi/squid-amd64/etc/squid/squid.conf line 82: cache_peer 192.168.0.4 parent 80 0 proxy-only no-query no-digest originserver login=PASSTHRU round-robinname=rvp_xxx_80 Squid Cache (Version 3.3.10): Terminated abnormally. CPU Usage: 0.010 seconds = 0.005 user + 0.005 sys Maximum Resident Size: 38032 KB Page faults with physical i/o: 0'
-
Oh, i see…
There's a missing space after round-robin.
I'll patch this later this evening ...
Sorry ... -
patch checked in, should be committed tonight…
-
It should now work. The patch is online ;-)
-
It's the 3.3.10 PKG 2.2.5 ?
-
Yes
-
maybe a snapchot before to avoid a veeam restore ;)
-
Done and working ;D
-
Good news ;-)
-
Oupsy
Got a strange issue
The Microsoft Connectivity Analyzer is checking the host autodiscover.mydomain.com for an HTTP redirect to the Autodiscover service.
The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: <title>ERREUR: L'URL demandée n'a pas pu être trouvé</title>
ERROR
The requested URL could not be retrieved
L'erreur suivante s'est produite en essayant d'accéder à l'URL : http://autodiscover.sdskh.com/Autodiscover/Autodiscover.xml
Accès interdit.
La configuration du contrôle d'accès, empêche votre requête d'être acceptée. Si vous pensez que c'est une erreur, contactez votre fournisseur d'accès.
Votre administrateur proxy est admin@localhost.
Générer le Tue, 10 Jun 2014 08:46:04 GMT par localhost (squid/3.3.10)
I think I need some help ;)
EDIT: I created with GUI webserver exch80 and exch443
Then mapped to autodiscover.mydomain.com (map to both exch80 and exch443) then added mapi.mydomaine.com (map to exch44)
Everything works. I think there is an issue in the package -
are you running 32 or 64 bit pfSense ?
-
64
-
No idea what is the issue ? :o
-
autodiscover omly works with SSL (with the package) and the analyzer first tries 80 and then as a fallback solution 443, so by design there is no port 80 autodiscover…
does it not work at all without port 80 ?