Sign in
 
HomeOnline20132010Interop ProgramsLibraryForumsGalleryLync Blogs
TechCenter >
> 
> 
AutodiscoverService.svc returning internal address externally

Odpovědět AutodiscoverService.svc returning internal address externally

  • Friday, February 17, 2012 10:28 PM
     
     
    Sign In to Vote
    0

    When, from the outside of our network, I browse to https://lyncdiscover.<domain>.com/Autodiscover/AutodiscoverService.svc/ IE lets me open the file. The file, however, is returning the internal domain information:

    {"AccessLocation":"Internal","Root":{"Links":[{"href":"https:\/\/<internal server and domain>\/Autodiscover\/AutodiscoverService.svc\/root\/domain","token":"Domain"},{"href":"https:\/\/<internal server and domain>\/Autodiscover\/AutodiscoverService.svc\/root\/user","token":"User"}]}}

    Is there a particular reason this is happening. It's obviously preventing our external phones form connecting. Phone work fine when connecting via wi-fi inside the network.

    Thanks

     

All Replies

  • Friday, February 17, 2012 11:19 PM
     
     
    Sign In to Vote
    1
    Check you Lyncautodiscover records in the public DNS? are pointing to the Public IP of the Reverse Proxy ? Try an Nslookup as well.

    Abhay Kamath (MSFT)- Global Partner Services

     
  • Sunday, February 19, 2012 2:41 PM
    Moderator
     
     Proposed Answer
    Sign In to Vote
    2

    First validate what your configured internal and external URIs are:

    Get-CsService -PoolFqdn lyncpool.contoso.com -WebServer | Select-Object McxService* | fl

    If both the McxServiceExternalUri and McxServiceInternalUri values are set to the same internal FQDN then run the following command to expose the proper URLs for the internal+external access scenario:

    Set-CsMcxConfiguration –ExposedWebUrl External

    Jeff Schertz | Microsoft Solutions Architect - Polycom | Lync MVP




     
  • Tuesday, February 21, 2012 8:25 PM
     
     
    Sign In to Vote
    0

    Thanks for the reply (and your great blog). 

    Get-CsService gives these results:

    McxServiceExternalUri : https://lync.domain.com/Mcx/McxService.svc
    McxServiceInternalUri : https://server.internaldomain.pvt/Mcx/McxService.svc

    From outside, using IE9, all of the discovery seems to work as expected. However, when I put in https://lync.exdomain.com/Mcx/McxService.svc the value returned at the top is "svcutil.exe https://server.internaldomain.pvt:4443/Mcx/McxService.svc/mex?wsdl"

    That's confusing because simply going to lyncdiscover.domain.com gives me the correct results (extneral info).

    ------------------------------------------------------------------

    Here is the log from my phone (WP7 - which does work on internal wifi)

    2012-02-21 12:37:56.353-6 : Verbose : 420741382 : ConfigurationResolver : Value for internal MCX is https://server.internaldomain.pvt/Mcx/McxService.svc.
    2012-02-21 12:37:56.353-6 : Verbose : 420741382 : ConfigurationResolver : Value for external MCX is https://server.internaldomain.pvt/Mcx/McxService.svc.
    2012-02-21 12:37:56.354-6 : Verbose : 420741382 : ConfigurationResolver : Value for internal auto-discover is https://server.internaldomain.pvt/Autodiscover/AutodiscoverService.svc/root.
    2012-02-21 12:37:56.354-6 : Verbose : 420741382 : ConfigurationResolver : Value for external auto-discover is https://lync.exdomain.com/Autodiscover/AutodiscoverService.svc/root.
    2012-02-21 12:37:56.354-6 : Info : 420741382 : ConfigurationResolver : Discovery complete for user@domain.com. Internal MCX: https://server.internaldomain.pvt/Mcx/McxService.svc. External MCX: https://server.internaldomain.pvt/Mcx/McxService.svc. Is internal? False.
    2012-02-21 12:37:56.371-6 : Info : 420741382 : InternalExternalSelector : Setting mode to EXTERNAL
    2012-02-21 12:37:56.372-6 : Info : 420741382 : InternalExternalSelector : Configuring Transport to use EXTERNAL URLs
    2012-02-21 12:37:56.372-6 : Info : 420741382 : LogonSession : Server discovery complete. Beginning sign-in.
    2012-02-21 12:37:56.377-6 : Info : 420741382 : Mcx14Session : InitSession request: Culture 'en-US', UA 'WPLync/4.0.7878.0 (Microsoft Windows CE 7.10.7720; SAMSUNG SGH-i937 2103.11.10.1)'.
    2012-02-21 12:37:56.377-6 : Verbose : 420741382 : HttpRequestPump : Request InitSess to https://server.internaldomain.pvt/Mcx/McxService.svc requires metadata.
    2012-02-21 12:37:56.377-6 : Verbose : 420741382 : MetadataManager : Got a resolve request for https://server.internaldomain.pvt/Mcx/McxService.svc.
    2012-02-21 12:37:56.378-6 : Info : 420741382 : LogonSession : New LogonSession internal state = SigningIn
    2012-02-21 12:37:57.383-6 : Warning : 459997402 : HttpRequestPump : Got a WebException while reading the response for MEXhttps://server.internaldomain.pvt/Mcx/McxService.svc.


    • Edited by rtbarnes001 Tuesday, February 21, 2012 8:40 PM
    •  
     
  • Wednesday, February 22, 2012 10:00 PM
     
     
    Sign In to Vote
    0
    Could you let us know which Reverse proxy are you using and are you using HTTP - HTTPS redirection to the front end server or do you have the autodiscover entries defined in the Reverse proxy cert.

    Abhay Kamath (MSFT)- Global Partner Services

     
  • Wednesday, February 22, 2012 10:03 PM
     
     
    Sign In to Vote
    0
    I'm using all HTTPS on an unauthenticated UAG SP1 trunk. We are using a wildcard cert for our external certificate but everything is under the same domain.
     
  • Thursday, February 23, 2012 12:14 AM
     
     Answered
    Sign In to Vote
    0

    @rtbarnes001

    TMG is the recommended Reverse proxy solution for Publishing Lync mobility. Though UAG SP1 is now supported for publishing Lync web services, I doubt if there are many UAG/Mobility configurations working fine. UAG is known to cause issues for lync mobility.

    Abhay Kamath (MSFT)- Global Partner Services