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.



  • @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.

    Is this local hosted or Office 365?



  • @dbeato Local



  • @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



  • @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.



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



  • @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?



  • @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



  • 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.



  • @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



  • @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.



  • @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