Exchange / Outlook 2010 Autodiscover / Outlook Anywhere [Solved]

[RabbieBurns]

hmm.. ive changed it all to Basic auth and it seems to be working again..

[sukh]

I'm assuming you set the ClientAuthenticationMethod and Outlook to Basic?

[RabbieBurns]

yes set both exchange and outlook to basic and it seems to work. Does that mean its sending passwords in plaintext or is it still encrypted as its over https?

[sukh]

Password/username is sent in cleartest, however is encryted if HTTPS is used.

 

Did you have the original issue using NTLM? As from your output it indicates that both basic and NTLM were specified.

 

Sukh

[RabbieBurns]

Im sure it used to work with NTLM auth, and then it stopped working. But if its working now with basic, I guess that will do. Thanks again for your help!

[sukh]

@Rabbie - Yes, it should work with NTLM. Only thing from the logs I can see is that both authentication were set ( MaxValidValue) even though, it should have used NTLM. Also, in IIS, the authentication methods must be configured too.

 

If it's working using Basic and you dont want to use NTLM then it's ok, if you want to try NTLM then we try to do that.

 

Sukh

[PiqueABoo]

I've been having very vaguely related fun with an EWS app to Live@Edu through a proxy (may be fine with others).

 

Without the proxy in the way it works. If I use standard autodiscovery to get the EWS url, any subsequent action e.g. bind to an Inbox fails to authenticate with the server: Negotiate -> NTLM 3 = Auth. failed. If I manually set the EWS url then any subsequent action works i.e. the NTLM authentication succeeds. It all over HTTPS so in the end I got my app to force basic authentication which lets me happily autodiscover and then do normal EWS things with or without that proxy in the way.

[PeteLong]

Outlook Anywhere Does use 443

 

 

Exchange 2010 - Setup and Deploy Outlook Anywhere