Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 149
  • Last Modified:

certain OU gets Wrong Autodiscover settings

Hi Guys, I really ope you can help me out.
I'm baffeled by a most bizzare issue.

I have an exchange cluster on which we give "Hosted Exchange" services - meaning it's not serving our company - we have an internal exhcnage server that works fine - the hosted exchange enviroment however works differently with it's own AD and domain and all that.

Currently I have a domain that is using our hosted exchange services - Desheli-r.co.il and I have the most bizzare issue with it - If I try to use autoconfigure with it and I get this:
Capture.PNG
Any other Domain gives me the normal reply that looks like that:
Capture1.PNG

Information that might be helpful, the exhcange enviroment is 2010. tried to test on outlook 2007/2010/2013
I can't make heads or tails of this. Can you please Assist?
0
David Sankovsky
Asked:
David Sankovsky
  • 3
  • 2
1 Solution
 
Manoj BojewarCommented:
Please verify below two things

1)The first outlook Profile you are testing looks like configure with IMAP SSL. Please configure this outlook profile with autodiscover method

2)Verify autodiscover record for this domain is properly setup.
0
 
David SankovskySenior SysAdminAuthor Commented:
!) It's not a configuration attempt, it's a build in tool in Outlook that tests the autodiscover settings for a domain - I just put in the mailbox and the password -outlook tests it itself.

2)Verified :
Capture.PNG
The adresses are corect.
0
 
Manoj BojewarCommented:
Is it possible for you to share one test account and password of this domain to verify autodiscover configuration from my end.
0
 
David SankovskySenior SysAdminAuthor Commented:
I seem to have found the answer myself while looking at the log of the outlook configuration tester.
It appears that outlook has a certain sequence it follows when trying to connect.

The very first thing it checks is not a CNAME record but it tries to access the autodiscover.xml file on the server that hosts the website so if I'm talking aobut contoso.com it'll first go to https://contoso.com/autodiscover/autodiscover.xml

It'll only check the cname if the abovementioned xml file is not found, if it is found however, that file will catch on first and the server won't even proceed to check pther records.
0
 
David SankovskySenior SysAdminAuthor Commented:
I was able to solve the case myself. Marked it as a solution so if anyone encounters such an issue in the future, they'll have an answer ready.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now