[9.075][BUG] Outlook Anywhere 2013 and WAF does not work

peter.haag@centrotherm.de over 12 years ago

Hello,

today I've tested the WAF with Exchange OWA/ECP and Outlook anywhere integration.

OWA and ECP works, but there are errors with Outlook anywhere.

UTM 9.075-8 is used, and YES, Pass Outlook Anywhere is switched on in the FW Profile.

Please see attache LiveLog for errors.

Is there any solution available, or is it a configuration problem?

Please let me know if any further information is required.

BTW: I've done tests with Outlook anywhere without WAF, but with a NAT-Rule, this works!

0 Alex76 over 12 years ago

Hi,

i have tested it too and it works perfect in my case, please take a look to my configuration:
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mle over 12 years ago

Hi Peter Haag,

please make sure that Outlook Anywhere works with a DNAT rule that forwards the https traffic to your Exchange server. If it doesn't work with DNAT, then there is probably an issue outside the scope of the WAF, that you should fix first. Only after if it is working with a DNAT rule, then disable the DNAT rule and try to configure the WAF.

Regards,
mlenk
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Alex76 over 12 years ago

BTW: I've done tests with Outlook anywhere without WAF, but with a NAT-Rule, this works!

If you read his text, then you know that DNAT works. So the configuration problem must be on certificate or WAF side.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 peter.haag@centrotherm.de over 12 years ago in reply to Alex76

Hi Alex,

thanks for your reply, I use exact the same settings.
The difference seems to be that you use Exchange2010, I use Exchange2013, maybe this is the problem!?

Peter
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Alex76 over 12 years ago

Hi Peter,

this is possible, but you can check this with a Outlook 2010 client.

With Outlook 2013 and Exchange 2013, there is a extended RPC over HTTPS implimentation and this can make the problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 AngeloC over 12 years ago

Also ensure you are using the new 9.080 release for your testing.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 mle over 12 years ago in reply to Alex76

If you read his text, then you know that DNAT works. So the configuration problem must be on certificate or WAF side.

Sorry, I've overlooked that. I'll take a more detailed look on Tuesday.

Regards,
mlenk
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

0 mle over 12 years ago

2013:03:28-13:03:27 f1wall reverseproxy: [Thu Mar 28 13:03:27.460050 2013] [proxy_msrpc:error] [pid 11145:tid 2746211184] [client 84.171.209.28:1136] RPC_OUT_DATA: The Transfer-Encoding 'chunked' is unsupported by the MSRPC module, aborting request

Ok, apparently the MSRPC module needs to get fixed so that it supports 'chunked' encoding too.

Regards,
mlenk

0 peter.haag@centrotherm.de over 12 years ago in reply to mle

I tried UTM 9.080-10 and Outlook Client 2010, still the same problem.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Astaro Beta Bot over 12 years ago

Thanks for reporting. We are now tracking this as Mantis ID #24834
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel