locked
Lync Mobility RRS feed

  • Question

  • Hi All,

    I'm having trouble with lync mobility service. when i type the lyncdiscover.domain.com the redirection file can be downloaded. but it contain internal address of the lync server. Is there any way to configure it to external address?

    Monday, March 26, 2012 1:14 PM

Answers

  • Hi,

    It looks like you just download internal lyncdiscover file.

    Where do you download the lyncdiscover file, internal or internet?

    You can have a test in internal network with htttps:// lyncdiscoverinternal.domain.com:4443 to check you can get the external lyncdiscover file. If not, maybe something with your mobility service configuration. Please check it.

    If internet, please make sure you configure your reverse proxy correctly. You need to redirect the external requests from 443 to internal 4443 port.


    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.

    • Marked as answer by Sean_Xiao Thursday, April 5, 2012 3:03 AM
    Wednesday, March 28, 2012 1:21 AM
  • OK.

    Let's just look at your IIS logs.  On your front end servers go to this folder

    %SystemDrive%\inetpub\logs\LogFiles

    There should be a couple log files in there.  Look for the one that has events on port 4443.  Thats your external listener web log.  You should see events like below.  In my case the request is from the TMG (192.168.176.130 is the TMG server proxying the external web request (443 external --> 4443 internal). 

    012-03-27 00:05:49 10.xxx.xxx.28 GET /mcx/mcxasyncdatachannel.ashx sid=08664d69-f926-8801-5d62-a624470c9552&ackid=680&timeout=300000&ua=true 4443 - 192.168.xxx.130 Lync%202010/1.1+CFNetwork/548.1.4+Darwin/11.0.0 200 0 0 3

    My assumption is you wont see the requests from your external phones on the external listener, but instead you will see them on your internal listener because you are not forwarding 443 to 4443 internally.


    BBB

    • Proposed as answer by Sean_Xiao Saturday, March 31, 2012 2:13 AM
    • Marked as answer by Sean_Xiao Thursday, April 5, 2012 3:03 AM
    Wednesday, March 28, 2012 12:29 AM

All replies

  • Hi,

    I suppose you set internal option as exposed URL for mobility service. Try to execute Get-CsMcxConfiguration in Lync Server Management Shell. If it returns "ExposedWebURL: Internal", execute "Set-CsMcxConfiguration -ExposedWebURL External".

    Regards,


    Yutaka

    Monday, March 26, 2012 1:34 PM
  • Hi Yutuka,

    I already typed this command called "Get-CsMcxConfiguration" and checked the status. It has "ExposedWebURL : External". But still I'm receiving the internal file. Further, I do not have any reverse proxy in my scenario.

    Monday, March 26, 2012 4:08 PM
  • Thisaru,

    Can you test 2 urls for me.  My assumption is that your external people are hitting the internal url (80 or 443) instead of the external (8080 4443). 80 and 443 should give you internal info. 8080 and 4443 should provide external.

    http://lyncdiscover.domain.com:8080/autodiscover.aspx/root/sipuri=user@domain.com

    http://lyncdiscover.domain.com:80/autodiscover.aspx/root/sipuri=user@domain.com

    or

    https://lyncdiscover.domain.com:4443/autodiscover.aspx/root/sipuri=user@domain.com

    https://lyncdiscover.domain.com:443/autodiscover.aspx/root/sipuri=user@domain.com


    BBB

    Monday, March 26, 2012 6:06 PM
  • Still I'm receiving the same file when I typed lyncdiscover.domain.com which looks like this -

    {"AccessLocation":"Internal","Root":{"Links":[{"href":"https:\/\/lyncserver.domain.local\/Autodiscover\/AutodiscoverService.svc\/root\/domain","token":"Domain"},{"href":"https:\/\/lyncserver.domain.local\/Autodiscover\/AutodiscoverService.svc\/root\/user","token":"User"}]}}

    it should be "External" is it?
    Monday, March 26, 2012 7:32 PM
  • on 443 from inside you should get internal.
    4443 from inside you should get external. 

    443 outside must be proxied or natted or different assigned ip to the 4443 server on the FE.  It sounds like your external 443 is going to the internal 443 which is not correct.


    BBB

    Monday, March 26, 2012 8:59 PM
  • Yes correct you should get external URL instead of internal.

    here are my suggestions and questions:

    are you able to use lync mobility internally have you tried lyncdiscoverinternal.domain.com open the file what is it giving you it should be external.

    are you using microsoft lync standard edition or FE

    can you go to topology builder and see the property of external url what is mentioned there internal one or external one

    where exacty you have defined lyncserver.domain.local in topology builder

    what is your primary sip domain is it domain.local or have you defined additional sip domains in topology builder


    If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync

    Monday, March 26, 2012 9:00 PM
  • I'm using Lync standard edition and I have only one sip domain no adiitional sip domain is configured. (only domain.com is available. and it is set to default).

    When i can get the file from lyncdiscoverinternal.domain.com but it contain internal fqdn.

    i'm using standerd edition.

    in topology builder i have defined the external FQDN as lync.domail.com 

    Tuesday, March 27, 2012 6:24 AM
  • Thisaru, can you post the internal results from the four ports listed above? and then from outside .. we can probably tell you exactly whats wrong with that info.

    BBB

    Tuesday, March 27, 2012 3:27 PM
  • Hi indubious,

    When I type http://lyncdiscover.domain.com:8080/autodiscover.aspx/root/sipuri=user@domain.com it doesn't download anything. But when I type http://lyncdiscover.domain.com:80/autodiscover.aspx/root/sipuri=user@domain.com I receive a file which includes following

    {"Root":{"Links":[{"href":"https:\/\/lync.domain.int\/Autodiscover\/AutodiscoverService.svc\/root?sipuri=","token":"Redirect"}]}}

    When I type https://lyncdiscover.domain.com:4443/autodiscover.aspx/root/sipuri=user@domain.com still there’s no any download. But when I type https://lyncdiscover.domain.com:443/autodiscover.aspx/root/sipuri=user@domain.com I receive a file which includes following

    {"AccessLocation":"Internal","Root":{"Links":[{"href":"https:\/\/ lync.domain.int \/Autodiscover\/AutodiscoverService.svc\/root\/domain","token":"Domain"},{"href":"https:\/\/ lync.domain.int \/Autodiscover\/AutodiscoverService.svc\/root\/user","token":"User"}]}}


    Tuesday, March 27, 2012 5:57 PM
  • OK.

    Let's just look at your IIS logs.  On your front end servers go to this folder

    %SystemDrive%\inetpub\logs\LogFiles

    There should be a couple log files in there.  Look for the one that has events on port 4443.  Thats your external listener web log.  You should see events like below.  In my case the request is from the TMG (192.168.176.130 is the TMG server proxying the external web request (443 external --> 4443 internal). 

    012-03-27 00:05:49 10.xxx.xxx.28 GET /mcx/mcxasyncdatachannel.ashx sid=08664d69-f926-8801-5d62-a624470c9552&ackid=680&timeout=300000&ua=true 4443 - 192.168.xxx.130 Lync%202010/1.1+CFNetwork/548.1.4+Darwin/11.0.0 200 0 0 3

    My assumption is you wont see the requests from your external phones on the external listener, but instead you will see them on your internal listener because you are not forwarding 443 to 4443 internally.


    BBB

    • Proposed as answer by Sean_Xiao Saturday, March 31, 2012 2:13 AM
    • Marked as answer by Sean_Xiao Thursday, April 5, 2012 3:03 AM
    Wednesday, March 28, 2012 12:29 AM
  • Hi,

    It looks like you just download internal lyncdiscover file.

    Where do you download the lyncdiscover file, internal or internet?

    You can have a test in internal network with htttps:// lyncdiscoverinternal.domain.com:4443 to check you can get the external lyncdiscover file. If not, maybe something with your mobility service configuration. Please check it.

    If internet, please make sure you configure your reverse proxy correctly. You need to redirect the external requests from 443 to internal 4443 port.


    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.

    • Marked as answer by Sean_Xiao Thursday, April 5, 2012 3:03 AM
    Wednesday, March 28, 2012 1:21 AM