Outlook Anywhere...

[mrbios]

I'm trying to get exchange 2010 outlook anywhere to work, going through ISA 2006 server...

I've used www.testexchangeconnectivity.com to find out where im going wrong and it's telling me it's being blocked by the ISA server, I've allowed /rpc/* on the paths of the same OWA publishing rule that allows OWA

OWA has been working fine for weeks, when I test the rule http:// for the /rpc/* path is ok, but https:// errors

I've set the rpc folder on exchange IIS to require SSL and enabled basic authentication

Am I missing anything? I'll edit this with the error I'm getting on the rule test in a bit, have to remote in to work to get it though

 

[mrbios]

http doesn't work as it always asks for an SSL connection

This is the error im getting:

Testing URL https://webmail.**************.net:443/rpc/
Category: General error
Error details: The authentication delegation method defined in the rule does not match the authentication method selected for the published directory on the server hosting the site. Publishing rule authentication delegation method: None. Published server authentication methods: NTLM, Negotiate.
Action: You can change the authentication method on the published server or change the authentication delegation method in the publishing rule.

and the error testexchangeconnectivity.com gives me is:

Testing Http Authentication Methods for URL https://webmail.*****************.net/rpc/rpcproxy.dll
Http Authentication Test failed

Additional Details
An HTTP 403 was received because ISA denied the specified URL

EDIT: oh first time i've noticed this....im assuming published rule authentication delegation method needs to match published server authentication method? qui ou non?

EDIT AGAIN:
Progress, new error message:

Testing URL https://webmail.***********.net:443/rpc/
Category: General error
Error details: An unexpected response was received from the server. HTTP response: 503 Service Unavailable
Action: Verify that the intended server is published and that virtual directories exist. Ensure that you can browse the published site directly from an internal client computer.

EDIT FOR THE LAST TIME:

I got it working yaaay outlook at home, no more crappy web mail for me