This post is about a problem where Outlook was working fine through TMG publishing rule, however when TMG Admin tried to access OAB and OOF through Outlook he got an error. To bypass Outlook he tried to access https://mail.contoso.com/ews/exchange.asmx and got 403. The 403 was coming from Exchange vdir /EWS/, here an example of the header:
10.20.20.11 10.20.20.1 HTTP HTTP:Response, HTTP/1.1, Status Code = 403, URL:
/ews/
– Http: Response, HTTP/1.1, Status Code = 403, URL: /ews/
ProtocolVersion: HTTP/1.1
StatusCode: 403, Forbidden
Reason: Forbidden
Server: Microsoft-IIS/7.5
Set-Cookie: exchangecookie=599fc2a7540e4e66b1169d9d5c358aa5; expires=Sat,
17-Jul-2011 21:39:05 GMT; path=/; HttpOnly
XPoweredBy: ASP.NET
Date: Fri, 29 Jan 2010 21:39:05 GMT
ContentLength: 0
HeaderEnd: CRLF
Check out Yuri Diogenes blog for the resolution and an explanation at: http://blogs.technet.com/b/yuridiogenes/archive/2011/07/18/unable-to-view-oab-and-oof-via-outlook-anywhere-published-through-tmg-isa.aspx
HTH,
Deb
DEBRA LITTLEJOHN SHINDER
MVP (Enterprise Security)
“MS SECURITY”
[email protected]