ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Skype for Business Autodiscovery Failing

    IT Discussion
    skype for business exchange 2013
    4
    12
    3.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • wirestyle22W
      wirestyle22 @dbeato
      last edited by

      @dbeato Local

      1 Reply Last reply Reply Quote 1
      • ObsolesceO
        Obsolesce @wirestyle22
        last edited by

        @wirestyle22 said in Skype for Business Autodiscovery Failing:

        Haven't played with Skype for Business very much as I'm trying to eliminate it, but here goes. We just recently switched e-mail domains. Everything is functioning as intended as far as e-mailing, but Skype for Business is losing chat history and some other issues. When I CTRL + Left click the Skype icon and click on Configuration Information on my local computer, both the EWS Internal URL and EWS External URL fields are completely empty. I read that this means it's likely that auto-discovery is failing.

        "The Lync/Skype for Business clients don't use Service Connection Point (SCP) to determine the autodiscover URL. Instead, they rely on DNS records. They base this action on the user’s domain suffix of the WindowsEmailAddress or Mail attribute in Active Directory."

        So skype account is logged in as [email protected] but my primary e-mail is [email protected]. Is this what is causing the issue? If so, how is that resolved? I don't seem to be able to manually enter the URL information.

        Do you have these set up on your DNS server?

        0_1540487568621_5b70b0db-d597-4b68-9552-6ec3f7fe91fb-image.png

        dbeatoD 1 Reply Last reply Reply Quote 0
        • dbeatoD
          dbeato @Obsolesce
          last edited by

          @Obsolesce said in Skype for Business Autodiscovery Failing:

          @wirestyle22 said in Skype for Business Autodiscovery Failing:

          Haven't played with Skype for Business very much as I'm trying to eliminate it, but here goes. We just recently switched e-mail domains. Everything is functioning as intended as far as e-mailing, but Skype for Business is losing chat history and some other issues. When I CTRL + Left click the Skype icon and click on Configuration Information on my local computer, both the EWS Internal URL and EWS External URL fields are completely empty. I read that this means it's likely that auto-discovery is failing.

          "The Lync/Skype for Business clients don't use Service Connection Point (SCP) to determine the autodiscover URL. Instead, they rely on DNS records. They base this action on the user’s domain suffix of the WindowsEmailAddress or Mail attribute in Active Directory."

          So skype account is logged in as [email protected] but my primary e-mail is [email protected]. Is this what is causing the issue? If so, how is that resolved? I don't seem to be able to manually enter the URL information.

          Do you have these set up on your DNS server?

          0_1540487568621_5b70b0db-d597-4b68-9552-6ec3f7fe91fb-image.png

          It is local not Office 365.

          ObsolesceO 1 Reply Last reply Reply Quote 0
          • ObsolesceO
            Obsolesce
            last edited by

            is the SIP proxyAddresses field in AD reflect the correct domain and user? What about the users' UPN suffix in AD?

            1 Reply Last reply Reply Quote 0
            • ObsolesceO
              Obsolesce @dbeato
              last edited by

              @dbeato said in Skype for Business Autodiscovery Failing:

              @Obsolesce said in Skype for Business Autodiscovery Failing:

              @wirestyle22 said in Skype for Business Autodiscovery Failing:

              Haven't played with Skype for Business very much as I'm trying to eliminate it, but here goes. We just recently switched e-mail domains. Everything is functioning as intended as far as e-mailing, but Skype for Business is losing chat history and some other issues. When I CTRL + Left click the Skype icon and click on Configuration Information on my local computer, both the EWS Internal URL and EWS External URL fields are completely empty. I read that this means it's likely that auto-discovery is failing.

              "The Lync/Skype for Business clients don't use Service Connection Point (SCP) to determine the autodiscover URL. Instead, they rely on DNS records. They base this action on the user’s domain suffix of the WindowsEmailAddress or Mail attribute in Active Directory."

              So skype account is logged in as [email protected] but my primary e-mail is [email protected]. Is this what is causing the issue? If so, how is that resolved? I don't seem to be able to manually enter the URL information.

              Do you have these set up on your DNS server?

              0_1540487568621_5b70b0db-d597-4b68-9552-6ec3f7fe91fb-image.png

              It is local not Office 365.

              What's local?

              dbeatoD 1 Reply Last reply Reply Quote 0
              • dbeatoD
                dbeato @Obsolesce
                last edited by

                @Obsolesce said in Skype for Business Autodiscovery Failing:

                @dbeato said in Skype for Business Autodiscovery Failing:

                @Obsolesce said in Skype for Business Autodiscovery Failing:

                @wirestyle22 said in Skype for Business Autodiscovery Failing:

                Haven't played with Skype for Business very much as I'm trying to eliminate it, but here goes. We just recently switched e-mail domains. Everything is functioning as intended as far as e-mailing, but Skype for Business is losing chat history and some other issues. When I CTRL + Left click the Skype icon and click on Configuration Information on my local computer, both the EWS Internal URL and EWS External URL fields are completely empty. I read that this means it's likely that auto-discovery is failing.

                "The Lync/Skype for Business clients don't use Service Connection Point (SCP) to determine the autodiscover URL. Instead, they rely on DNS records. They base this action on the user’s domain suffix of the WindowsEmailAddress or Mail attribute in Active Directory."

                So skype account is logged in as [email protected] but my primary e-mail is [email protected]. Is this what is causing the issue? If so, how is that resolved? I don't seem to be able to manually enter the URL information.

                Do you have these set up on your DNS server?

                0_1540487568621_5b70b0db-d597-4b68-9552-6ec3f7fe91fb-image.png

                It is local not Office 365.

                What's local?

                Skype for Business for @wirestyle22

                1 Reply Last reply Reply Quote 0
                • jt1001001J
                  jt1001001
                  last edited by

                  Still need the service records in DNS regardless of if its hosted or on premise. so the new email domain suffix has to match in DNS in order to find the service records. Think that is where your issue is as we ran into this as we have "split brain " DNS here (different internal and external domains). Also the certificates have to match the domain name as well.

                  wirestyle22W 1 Reply Last reply Reply Quote 2
                  • wirestyle22W
                    wirestyle22 @jt1001001
                    last edited by

                    @jt1001001 said in Skype for Business Autodiscovery Failing:

                    Still need the service records in DNS regardless of if its hosted or on premise. so the new email domain suffix has to match in DNS in order to find the service records. Think that is where your issue is as we ran into this as we have "split brain " DNS here (different internal and external domains). Also the certificates have to match the domain name as well.

                    Gonna have to figure out how to check all of this. I don't play with e-mail often

                    1 Reply Last reply Reply Quote 0
                    • dbeatoD
                      dbeato
                      last edited by

                      @wirestyle22 said in Skype for Business Autodiscovery Failing:

                      The Lync/Skype for Business clients don't use Service Connection Point (SCP) to determine the autodiscover URL. Instead, they rely on DNS records. They base this action on the user’s domain suffix of the WindowsEmailAddress or Mail attribute in Active Directory

                      I assume you have seen this already
                      https://support.microsoft.com/en-us/help/3120929/lync-skype-for-business-client-can-t-connect-with-exchange-in-office-3
                      Although it is for Office 365, those same DNS should be internal on your Exchange configured properly.

                      wirestyle22W 1 Reply Last reply Reply Quote 0
                      • wirestyle22W
                        wirestyle22 @dbeato
                        last edited by

                        @dbeato said in Skype for Business Autodiscovery Failing:

                        @wirestyle22 said in Skype for Business Autodiscovery Failing:

                        The Lync/Skype for Business clients don't use Service Connection Point (SCP) to determine the autodiscover URL. Instead, they rely on DNS records. They base this action on the user’s domain suffix of the WindowsEmailAddress or Mail attribute in Active Directory

                        I assume you have seen this already
                        https://support.microsoft.com/en-us/help/3120929/lync-skype-for-business-client-can-t-connect-with-exchange-in-office-3
                        Although it is for Office 365, those same DNS should be internal on your Exchange configured properly.

                        Yeah I saw that

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post