none
OOO not working, SBS 2008 standard RRS feed

  • Question

  • HI, i have a starnge problem on two server configure at diffrent sites.

    Both the server have multiple domain names registerd on them.

    Both the servers have all the latest updates installed.

    Problem OOO dosent work, (It works from owa), and when we do test email autoconfiguration we get

    autodiscover TO autodiscover.xml failed (0x800C8208)

    autodiscover TO autodiscover.xml failed (0x800C8203)

    Local autodiscover Failed (0x8004010F)

    SRV record lookup failed (0x80072EE7) (there are no srv records defined for autodiscover)

    I tried to find the solutions on the web and found an article which i followed and everything keeps working for one day but next day we have same problem.

    steps followed were:- Go to IIS Manager, expand the domain, got to sites, go to SBS web applications, highlight autodiscover, in the ceter pane find SSL Settings and double click on it. we will get three options and Ignore will be selected. change to accept and then click apply, change it back to ignore and then click apply.

    The behaviour is same on both the servers, and both are new Setups.

     


    Tx n Re, NSB Please click the Check Mark As Answered On This Page If this post helps to resolve your issue as it helps others.
    Tuesday, June 14, 2011 7:49 AM

All replies

  • The "solution" that you found isn't one that I have needed to do and doesn't really achieve anything.

    The fact that you are using multiple domains will complicate matters.

    OOTO uses the availability service, which accesses Exchange through Autodiscover.

    Therefore the first thing you have to do is decide which autodiscover method you are going to use.

    SBS 2008 presumes SRV records are going to be used - that requires your external DNS provider to support SRV records.
    The other main method is DNS host name - autodiscover.example.com - and that host name would need to be in the SSL certificate. If you have multiple domains then you would need each domain listed.

    Are you using a commercial SSL certificate? Was it installed through the SBS management console?

    Was the server in general configured through the wizards?

    Simon.

     


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    Tuesday, June 14, 2011 9:09 PM
  • The "solution" that you found isn't one that I have needed to do and doesn't really achieve anything.

    The fact that you are using multiple domains will complicate matters.

    OOTO uses the availability service, which accesses Exchange through Autodiscover.

    Therefore the first thing you have to do is decide which autodiscover method you are going to use.

    SBS 2008 presumes SRV records are going to be used - that requires your external DNS provider to support SRV records.
    The other main method is DNS host name - autodiscover.example.com - and that host name would need to be in the SSL certificate. If you have multiple domains then you would need each domain listed.

    Are you using a commercial SSL certificate? Was it installed through the SBS management console?

    Was the server in general configured through the wizards?

    Simon.

     


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.


    Agree.

    Since OOF is working fine in OWA, then the server site related configuration appears to be fine. the issue is most likely resided in the client side.

    Firstly you need to make sure the "Test Email AutoConfiguration" is working fine in Outlook client, and it returns the correct Autodiscover URL as well as OOF URL.

    And then make sure the Autodiscover URL and the OOF URL is available from the client computer.

    To troubleshot this issue, please follow the steps above and provide more description on the issue you are encountering, like the screenshot, the organization topology or configuration.

    Thanks,

    -Fiona

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, June 16, 2011 3:07 AM
    Moderator