Lync 2013 Desktop SHaring Not working from Internet

Hi,
I am facing one issue, my Desktop Sharing is not working for Internet Clients, error message comes is "we could not connect to the presentation because of network issues" Internally it is working fine even I from Edge Server.
I am using single Public IP Configuration on Edge Server with Port 5061,444,443,3478.
Any suggestions, on I can check are welcome.
Best Regards, Ranjit Singh

Hello Ranjit, 
Application Sharing/Desktop Sharing happens  through SRTP  through the A/V edge Server hence checking the Port Range is very important
Following Port reachability to be checked first
Public --> Edge server:
TCP/443
UDP/3478
TCP/50,000-59,999 (Outbound only)
From the Front End pool to the internal Edge:
TCP/5062
TCP/443
UDP/3478
From the internal Edge to the Front End Pool:
TCP/5065
TCP/49152-65335 (Inbound/Outbound)
More Detailed info can be seen here
http://blogs.technet.com/b/nexthop/archive/2012/11/05/lyncmd-troubleshooting-lync-server-2010-application-sharing-internal-and-remote-scenarios.aspx

Similar Messages

  • Lync 2013 Desktop Shareing

    Hi all
    this is Lync 2013.
    When desktop sharing between 2 external users( Connecting from Internet) will it be P2P or will it go via FE servers ?
    When desktop sharing between 1 internal user and 1 External user, will it be via FE server ?
    regards

    Sorry about that, I guessed this was common knowledge.
    NAT means "Network Address Translation" which is a difficult term for saying that someone is for example sitting at home behind a Router connected to an ISP with one public IP Address and shares the internet access with other devices connected to that user
    (essentially enabling all those devices connections to internet without the need of having multiple public IP Adresses)
    The process works by hiding the device real IP and replacing with the router Public IP address when it crosses the router and ther router keeps track of Ports and sessions that the different devices have so it knows how to send traffic back to the devices.
    A side effect of this is that there is no way of someone on the internet connection can see your IP or contact you directly.  Lync does have a process to try to enable direct communication between clients behind a NAT but that does not guarantee
    this will always work, there are cases where it will work and cases where it will never work.  In case it does not work Lync will bridge the connection at the Lync EDGE server.
    I hope this explains it better
    - Belgian Unified Communications Community : http://www.pro-lync.be - MCM/MVP/MCT

  • Lync 2013 A/V not working federated partner

    Hi,
    I have an interesting problem. I cant make video calls / desktop sharing via only federated
    domain. But IM working properly. There is a problem only A/V call.
    in my lync organization :
    1 front-end
    1 edge
    1 reverse proxy
    From
    To
    Type
    Result
    My Lync User ( Inside )
    My Lync User ( Outside )
    IM & A/V & Desktop Sharing
    Success
    My Lync User ( Inside or Outside ) from PC
    Federated Lync domain
    IM
    Success
    My Lync User ( Inside or Outside ) from PC
    Federated Lync domain
    A/V & Desktop Sharing
    Fail due network isses
    My Lync User ( Inside or Outside ) from Lync Mobile  to Federated Lync domain, type: Audio / Video call. result:
    success
    If you sign in from Lync mobile client and start video call to federated domain worked successfully. But if you sign in from PC Lync 2013 client and start video call, to federated domain,
    fail. Video invitation is reached federated domain and connection established but after a few seconds, A/V failed due network issues or audio video device not configured.
    During issue, i collected log using OcsLogger on the Edge Server. I examined the collected log but I could not find a error line.
    please help
    thanks

    Hi,
    From your description above, there is something wrong during the deployment of Edge Server.
    To avoid routing issues, make sure there are at least two network adapters in your Edge Servers and that the default gateway is set only on the network adapter associated with the external interface.
    You can configure two network adapters in your Edge Server as follows:
    Network adapter 1 (Internal Interface)
    For example: Internal interface with 172.25.33.10 assigned.
    No default gateway is defined.
    Ensure that there is a route from the network containing the Edge internal interface to any networks that contain servers running Lync Server 2013 or Lync Server 2013 clients.
    Network adapter 2 (External Interface)
    Three private IP addresses are assigned to this network adapter, for example 10.45.16.10 for Access Edge, 10.45.16.20 for Web Conferencing Edge, 10.45.16.30 for AV Edge.
    More details:
    http://technet.microsoft.com/en-us/library/gg412787.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Lync 2013 External Mobility Not Working

    Hello,
    The issue I seem to be having is in regards to the external mobility access. 
    So far everything else in our environment seems to be functioning properly. 
    The Lync desktop client works both internally as well as externally. 
    The Lync internal mobility also works.  The only issue seems to be with the external mobility part.
    I tried going to the external autodiscover address for our system, https://lyncdiscover.mydomain.com but it doesn’t return anything either. 
    I think the issue lies somewhere with DNS or my reverse proxy, however I’m having a hard time being able to just start changing settings seeing as how I don’t want to break everything that is currently working for our users.
    I’ve been through a lot of the post here but I still can’t seem to find the settings to fix the issue I’m having.
    Here is a breakdown of my settings I feel are in question:
    1 – Lync 2013 FE Server (LYNC01)
    1 – Lync Edge Server (EDGE01)
    1 – Reverse Proxy Server (RPROXY01)
    Public DNS:
    A Records
    SIP.mydomain.com                          
    205.XXX.XXX.91 (Access Service on EDGE01)
    AccessEdge.mydomain.com              
    205.XXX.XXX.91 (Access Service on EDGE01)
    WebConfEdge.mydomain.com            205.XXX.XXX.92 (WebConf Service on EDGE01)
    AVEdge.mydomain.com                    
    205.XXX.XXX.93 (A/VEdge Service on EDGE01)
    meet.mydomain.com                        
    205.XXX.XXX.94 (Reverse Proxy Server)
    dialin.mydomain.com                        
    205.XXX.XXX.94 (Reverse Proxy Server)
    lync.mydomain.com                          
    205.XXX.XXX.94 (Reverse Proxy Server)
    lyncdiscover.mydomain.com               205.XXX.XXX.94 (Reverse Proxy
    Server)
    SRV
    _sip._tls.mydomain.com:443                                     
    AccessEdge.mydomain.com
    _sipfederationtls._tcp.mydomain.com:5061             
    AccessEdge.mydomain.com
    _xmpp-server._tcp.mydomain.com                          
    AccessEdge.mydomain.com
    Private DNS:
    A Records
    LYNC01                                            
    172.XXX.XXX.65 (LYNC01 FE Server)
    Admin                                              
    172.XXX.XXX.65 (LYNC01 FE Server)
    Dialin                                               
    172.XXX.XXX.65 (LYNC01 FE Server)
    LyncDiscoverInternal                         
    172.XXX.XXX.65 (LYNC01 FE Server)
    Meet                                                
    172.XXX.XXX.65 (LYNC01 FE Server)
    Sip                                                  
    172.XXX.XXX.65 (LYNC01 FE Server)
    EDGE01                                            
    172.XXX.XXX.66 (EDGE01 Server)
    RPROXY01                                        
    172.XXX.XXX.70 (Reverse Proxy Server)
    Lync                                                 
    205.XXX.XXX.94 (Reverse Proxy Server)
    LyncDiscover  
    (CNAME)                    
    lync.gmsd.k12.pa.us
    SRV
    _xmpp-server._tcp.mydomain.com                          
    Sip.mydomain.com
    _sipinternaltls._tcp.mydomain.com:5061                 
    LYNC01.mydomain.com
    Lync Server Services Addresses
    Lync FE Server:                      \\
    LYNC01.mydomain.com (172.XXX.XXX.65)
    File Store:                              \\
    LYNC01.mydomain.com\Share
    Office Web Apps Server:
             \\lyncowa.mydomain.com
    External Web Services:
               \\lync.mydomain.com
    Edge Server Services Addresses
    Edge Server:                  
    \\ EDGE01.mydomain.com (172.XXX.XXX.66)
    Access Edge Service:       
    \\AccessEdge.mydomain.com (172.XXX.XXX.67, 205.XXX.XXX.91)
    Web Conference Service:  \\WebConfEdge.mydomain.com (172.XXX.XXX.68, 205.XXX.XXX.92)
    A/V Edge Service:            \\WebConfEdge.mydomain.com
    (172.XXX.XXX.69, 205.XXX.XXX.93)
    Reverse Proxy Server Addresses
    Reverse Proxy Server:            
    RPROXY01.mydomain.com (172.XXX.XXX.70, 205.XXX.XXX.94)
    Server Farms:
    Dialin.mydomain.com:
    Dialin.mydomain.com (LYNC01)
    Meet.mydomain.com:
    Meet.mydomain.com (LYNC01)
    LyncDiscover.mydomain.com:
               LYNC01.mydomain.com (LYNC01)
    Lync.mydomain.com:                       
    LYNC01.mydomain.com (LYNC01)
    Edge External Cert
    AccessEdge.mydomain.com
    Sip.mydomain.com
    WebConfEdge.mydomain.com
    Reverse Proxy Cert
    lync.mydomain.com
    meet.mydomain.com
    dialin.mydomain.com
    lyncdiscover.mydomain.com
    lyncowa.mydomain.com
    With everything else working as it should, this external mobility part is just not really making sense to me.  I have also verified that the correct ports are being using on the reverse proxy as well for the server farms,
    8080 and 4443.  Any help would be greatly appreciated.  Thank you.

    I'm also attaching the log file from running Lync Connectivity Analyzer if it helps.
    [6/10/2014 7:30:18 AM] [DEBUG] Logging test parameters:
    [6/10/2014 7:30:18 AM] [DEBUG] SIP Uri: [email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] User Name:
    [6/10/2014 7:30:18 AM] [DEBUG] Discovery Type: Automatic Discovery
    [6/10/2014 7:30:18 AM] [DEBUG] Network access: NetworkAccessExternal
    [6/10/2014 7:30:18 AM] [DEBUG] Selected client: ApplicationLyncMobile2010
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting Lync server autodiscovery
    [6/10/2014 7:30:18 AM] [INFO] Please wait; this test may take several minutes to complete...
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting automatic discovery for secure (HTTPS) internal channel
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lyncdiscoverinternal.mydomain.com/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      Pragma: no-cache
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 670
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL https://lyncdiscoverinternal.mydomain.com/[email protected].  Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="Internal"><Root><Link token="Domain" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/domain" /><Link token="User" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user"
    /><Link token="OAuth" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/oauth/user" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /></Root></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover URL https://lyncdiscoverinternal.mydomain.com/[email protected] redirected to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 401, ReasonPhrase: 'Unauthorized', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      X-MS-WebTicketURL: https://lync01.mydomain.com/WebTicket/WebTicketService.svc
      X-MS-WebTicketSupported: cwt,saml
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-Powered-By: ASP.NET
      Content-Length: 1293
      Content-Type: text/html
    [6/10/2014 7:30:18 AM] [DEBUG] Authorization required for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Obtaining WebTicket from https://lync01.mydomain.com/WebTicket/WebTicketService.svc
    [6/10/2014 7:30:18 AM] [DEBUG] On-premises WebTicket server: https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] AcquireTicketAsync succeeded for https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] WebTicket: <saml:Assertion MajorVersion="1" MinorVersion="1" AssertionID="SamlSecurityToken-4e51bf2a-2849-4779-a595-a5040c22ff1b" Issuer="https://lync01.mydomain.com/63b16135-930c-5e0b-998c-7ed6bc68b6f8" IssueInstant="2014-06-10T11:30:18.173Z"
    xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"><saml:Conditions NotBefore="2014-06-10T11:30:18.173Z" NotOnOrAfter="2014-06-10T19:23:01.173Z"><saml:AudienceRestrictionCondition><saml:Audience>https://lync01.mydomain.com/</saml:Audience></saml:AudienceRestrictionCondition></saml:Conditions><saml:AuthenticationStatement
    AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:unspecified" AuthenticationInstant="2014-06-10T11:30:18.173Z"><saml:Subject><saml:NameIdentifier Format="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/uri">sip:[email protected]</saml:NameIdentifier><saml:SubjectConfirmation><saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:holder-of-key</saml:ConfirmationMethod><KeyInfo
    xmlns="http://www.w3.org/2000/09/xmldsig#"><e:EncryptedKey xmlns:e="http://www.w3.org/2001/04/xmlenc#"><e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#kw-aes256"></e:EncryptionMethod><KeyInfo><KeyName>63b16135-930c-5e0b-998c-7ed6bc68b6f8:8d152b04ce7ddbf</KeyName></KeyInfo><e:CipherData><e:CipherValue>7M3R6naVg1ifGvuQKTMS+4EjHlJrdZeQqsqobNZUhMxHE9y7klUmXw==</e:CipherValue></e:CipherData></e:EncryptedKey></KeyInfo></saml:SubjectConfirmation></saml:Subject></saml:AuthenticationStatement><Signature
    xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></CanonicalizationMethod><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></SignatureMethod><Reference
    URI="#SamlSecurityToken-4e51bf2a-2849-4779-a595-a5040c22ff1b"><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"></Transform><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></Transform></Transforms><DigestMethod
    Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"></DigestMethod><DigestValue>otvulmCO6kY0HQdwfqQXUZT/pdmKSdVZJTU0f/MS0N8=</DigestValue></Reference></SignedInfo><SignatureValue>WUGQOtUzu6RtuSKdHHCQZWxiOFVf8HT181U6tS8IVifyyAzA046lm0SBKbFpLzwMEAXsf3ZmkHQkzK/AfS6WJ92WkAz3LLEsqSqGBGQoxe5WPXMlfA9J4+1lnT6Zsfq7fb9aLqZch2oSga3yj0CeQgsbcmppQhQO86zJ468YskVyAk4Y/oIOyThKg/+Ce8V4tFw575+zYatuSzKvUtgHq+DKJRO7T2M8r0aoCx65ZgfCxJpA+bqalDz3BesqOzMKfWTn33fwArVh8JMF1ohNkliwOegTeEEq4aH2Sg04N7ZfLrhoFlWeXuZWn1AzWppyl+FBfwlbLOVbQgP6/3NdMQ==</SignatureValue><KeyInfo><o:SecurityTokenReference
    xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1">/YVCIdf+YFyKopRflv61uWov2vs=</o:KeyIdentifier></o:SecurityTokenReference></KeyInfo></Signature></saml:Assertion>
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      Pragma: no-cache
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 1646
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected].  Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="Internal"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess
    fqdn="AccessEdge.mydomain.com" port="5061" /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker"
    href="https://lync01.mydomain.com/Reach/sip.svc" /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root"
    /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc" /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications"
    /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [INFO] Server discovery has completed for https://lyncdiscoverinternal.mydomain.com/.
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover full response for URL https://lyncdiscoverinternal.mydomain.com/ is <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    AccessLocation="Internal"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess fqdn="AccessEdge.mydomain.com" port="5061"
    /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker" href="https://lync01.mydomain.com/Reach/sip.svc"
    /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc"
    /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications" /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications"
    /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] SendRequest failed for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [INFO] Automatic discovery results for https://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [INFO] Access Location                          : Internal
    [6/10/2014 7:30:18 AM] [INFO] SIP Server Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Server External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] Internal Auth broker service             : https://lync01.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] External Auth broker service             : https://lync.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal Auto discover service           : https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] External Auto discover service           : https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] Internal MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] External MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal UCWA service                    : https://lync01.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] External UCWA service                    : https://lync.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] Internal Webscheduler service            : https://lync01.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] External Webscheduler service            : https://lync.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] Total server discovery time: 0.1 seconds
    [6/10/2014 7:30:18 AM] [SUMMARY_SUCCESS] Server discovery succeeded for secure (HTTPS) internal channel against URL https://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting automatic discovery for unsecure (HTTP) internal channel
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to http://lyncdiscoverinternal.mydomain.com/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      Pragma: no-cache
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 670
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL http://lyncdiscoverinternal.mydomain.com/[email protected].  Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="Internal"><Root><Link token="Domain" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/domain" /><Link token="User" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user"
    /><Link token="OAuth" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/oauth/user" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /></Root></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover URL http://lyncdiscoverinternal.mydomain.com/[email protected] redirected to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 401, ReasonPhrase: 'Unauthorized', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      X-MS-WebTicketURL: https://lync01.mydomain.com/WebTicket/WebTicketService.svc
      X-MS-WebTicketSupported: cwt,saml
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-Powered-By: ASP.NET
      Content-Length: 1293
      Content-Type: text/html
    [6/10/2014 7:30:18 AM] [DEBUG] Authorization required for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Obtaining WebTicket from https://lync01.mydomain.com/WebTicket/WebTicketService.svc
    [6/10/2014 7:30:18 AM] [DEBUG] On-premises WebTicket server: https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] AcquireTicketAsync succeeded for https://lync01.mydomain.com/WebTicket/WebTicketService.svc/Auth
    [6/10/2014 7:30:18 AM] [DEBUG] WebTicket: <saml:Assertion MajorVersion="1" MinorVersion="1" AssertionID="SamlSecurityToken-1b6331e1-4be5-4749-869a-21feb4b7198a" Issuer="https://lync01.mydomain.com/63b16135-930c-5e0b-998c-7ed6bc68b6f8" IssueInstant="2014-06-10T11:30:18.238Z"
    xmlns:saml="urn:oasis:names:tc:SAML:1.0:assertion"><saml:Conditions NotBefore="2014-06-10T11:30:18.238Z" NotOnOrAfter="2014-06-10T19:20:24.238Z"><saml:AudienceRestrictionCondition><saml:Audience>https://lync01.mydomain.com/</saml:Audience></saml:AudienceRestrictionCondition></saml:Conditions><saml:AuthenticationStatement
    AuthenticationMethod="urn:oasis:names:tc:SAML:1.0:am:unspecified" AuthenticationInstant="2014-06-10T11:30:18.238Z"><saml:Subject><saml:NameIdentifier Format="http://schemas.xmlsoap.org/ws/2005/05/identity/claims/uri">sip:[email protected]</saml:NameIdentifier><saml:SubjectConfirmation><saml:ConfirmationMethod>urn:oasis:names:tc:SAML:1.0:cm:holder-of-key</saml:ConfirmationMethod><KeyInfo
    xmlns="http://www.w3.org/2000/09/xmldsig#"><e:EncryptedKey xmlns:e="http://www.w3.org/2001/04/xmlenc#"><e:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#kw-aes256"></e:EncryptionMethod><KeyInfo><KeyName>63b16135-930c-5e0b-998c-7ed6bc68b6f8:8d152b04ce7ddbf</KeyName></KeyInfo><e:CipherData><e:CipherValue>NrQOUA0JAXMmR/4ACrZ8LyVN79jUZbR6Fz+sGlbAdWXgQF/u24DLlw==</e:CipherValue></e:CipherData></e:EncryptedKey></KeyInfo></saml:SubjectConfirmation></saml:Subject></saml:AuthenticationStatement><Signature
    xmlns="http://www.w3.org/2000/09/xmldsig#"><SignedInfo><CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></CanonicalizationMethod><SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></SignatureMethod><Reference
    URI="#SamlSecurityToken-1b6331e1-4be5-4749-869a-21feb4b7198a"><Transforms><Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"></Transform><Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></Transform></Transforms><DigestMethod
    Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"></DigestMethod><DigestValue>WnZZN/Vbfrget92urYd1+HmyXX/vYQ6CjHN4lLEXxK0=</DigestValue></Reference></SignedInfo><SignatureValue>BiFjeIuG7TW/DqIdklMNdaqRJLgbenphBcb51HGGH4WCdThgj2Oizkvfa6NRAwsE74qmyVLcfJIO2TK+if1yelHzUEde8ZvLwcruIFYWecK3OXDSDiGpYa3WdPwNUZrSRySSiCyb+fyYgz8BvZq3JjQRulOXnFhz4X3wXzoS6xMovmmVsOrdVTMjvT7l7ydEo1ucnEl5zjEnKih7WjCoElYENwEeG2HGf4Xqi43piaWXa9k7GY9k1idyrfJ7too+u7O7fhnhJ9OR0GR1KydbAPdSi5hmpZcziLn6xKCVW64w2bGCsT4N2vr+f5AhknSmjDa+9Wnyiar2uuLk+7eLmQ==</SignatureValue><KeyInfo><o:SecurityTokenReference
    xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><o:KeyIdentifier ValueType="http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA1">/YVCIdf+YFyKopRflv61uWov2vs=</o:KeyIdentifier></o:SecurityTokenReference></KeyInfo></Signature></saml:Assertion>
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [DEBUG] Cookie  found in autodiscover response: StatusCode: 200, ReasonPhrase: 'OK', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:
      Pragma: no-cache
      X-MS-Server-Fqdn: LYNC01.mydomain.com
      X-Content-Type-Options: nosniff
      Cache-Control: no-cache
      Date: Tue, 10 Jun 2014 11:30:18 GMT
      Server: Microsoft-IIS/7.5
      X-AspNet-Version: 4.0.30319
      X-Powered-By: ASP.NET
      Content-Length: 1646
      Content-Type: application/vnd.microsoft.rtc.autodiscover+xml; v=1
      Expires: -1
    [6/10/2014 7:30:18 AM] [DEBUG] Parsing the response for URL https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected].  Full response: <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" AccessLocation="Internal"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess
    fqdn="AccessEdge.mydomain.com" port="5061" /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker"
    href="https://lync01.mydomain.com/Reach/sip.svc" /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root"
    /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc" /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications"
    /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [INFO] Server discovery has completed for http://lyncdiscoverinternal.mydomain.com/.
    [6/10/2014 7:30:18 AM] [DEBUG] Autodiscover full response for URL http://lyncdiscoverinternal.mydomain.com/ is <?xml version="1.0" encoding="utf-8"?><AutodiscoverResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    AccessLocation="Internal"><User><SipServerInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipClientInternalAccess fqdn="LYNC01.mydomain.com" port="5061" /><SipServerExternalAccess fqdn="AccessEdge.mydomain.com" port="5061"
    /><SipClientExternalAccess fqdn="AccessEdge.mydomain.com" port="443" /><Link token="Internal/Autodiscover" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="Internal/AuthBroker" href="https://lync01.mydomain.com/Reach/sip.svc"
    /><Link token="Internal/WebScheduler" href="https://lync01.mydomain.com/Scheduler" /><Link token="External/Autodiscover" href="https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root" /><Link token="External/AuthBroker" href="https://lync.mydomain.com/Reach/sip.svc"
    /><Link token="External/WebScheduler" href="https://lync.mydomain.com/Scheduler" /><Link token="Internal/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc" /><Link token="External/Mcx" href="https://lync01.mydomain.com/Mcx/McxService.svc"
    /><Link token="Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications" /><Link token="Internal/Ucwa" href="https://lync01.mydomain.com/ucwa/v0/applications" /><Link token="External/Ucwa" href="https://lync.mydomain.com/ucwa/v0/applications"
    /><Link token="Self" href="https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/user" /></User></AutodiscoverResponse>
    [6/10/2014 7:30:18 AM] [DEBUG] SendRequest failed for https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root/[email protected]
    [6/10/2014 7:30:18 AM] [INFO] Automatic discovery results for http://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [INFO] Access Location                          : Internal
    [6/10/2014 7:30:18 AM] [INFO] SIP Server Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Server External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] SIP Client External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:30:18 AM] [INFO] Internal Auth broker service             : https://lync01.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] External Auth broker service             : https://lync.mydomain.com/Reach/sip.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal Auto discover service           : https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] External Auto discover service           : https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:30:18 AM] [INFO] Internal MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] External MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:30:18 AM] [INFO] Internal UCWA service                    : https://lync01.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] External UCWA service                    : https://lync.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:30:18 AM] [INFO] Internal Webscheduler service            : https://lync01.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] External Webscheduler service            : https://lync.mydomain.com/Scheduler
    [6/10/2014 7:30:18 AM] [INFO] Total server discovery time: 0.1 seconds
    [6/10/2014 7:30:18 AM] [SUMMARY_SUCCESS] Server discovery succeeded for unsecure (HTTP) internal channel against URL http://lyncdiscoverinternal.mydomain.com/
    [6/10/2014 7:30:18 AM] [SUBHEADING] Starting automatic discovery for secure (HTTPS) external channel
    [6/10/2014 7:30:18 AM] [DEBUG] Sending HTTP request to https://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:30:39 AM] [DEBUG] Exception encountered while sending an HTTP request to https://lyncdiscover.mydomain.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException:
    An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period
    of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    [6/10/2014 7:30:39 AM] [ERROR] An error occurred while sending the request.
    Unable to connect to the remote server
    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:443
    [6/10/2014 7:30:39 AM] [INFO] For troubleshooting, try using a browser to open the server discovery URL https://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:30:39 AM] [DEBUG] System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed
    because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:443
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
    [6/10/2014 7:30:39 AM] [SUMMARY_ERROR] Server discovery failed for secured external channel against https://lyncdiscover.mydomain.com/
    [6/10/2014 7:30:39 AM] [SUBHEADING] Starting automatic discovery for unsecure (HTTP) external channel
    [6/10/2014 7:30:39 AM] [DEBUG] Sending HTTP request to http://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:31:00 AM] [DEBUG] Exception encountered while sending an HTTP request to http://lyncdiscover.mydomain.com/[email protected]: An error occurred while sending the request.. Complete Exception: \r\nSystem.Net.Http.HttpRequestException:
    An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period
    of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:80
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    [6/10/2014 7:31:00 AM] [ERROR] An error occurred while sending the request.
    Unable to connect to the remote server
    A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:80
    [6/10/2014 7:31:00 AM] [INFO] For troubleshooting, try using a browser to open the server discovery URL http://lyncdiscover.mydomain.com/[email protected]
    [6/10/2014 7:31:00 AM] [DEBUG] System.Net.Http.HttpRequestException: An error occurred while sending the request. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed
    because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 205.XXX.XXX.94:80
       at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
       at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
       --- End of inner exception stack trace ---
       at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
       at System.Net.Http.HttpClientHandler.GetResponseCallback(IAsyncResult ar)
       --- End of inner exception stack trace ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendHttpRequest>d__9.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<SendRequest>d__d.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<TryNextUrl>d__3.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at Microsoft.LyncServer.WebServices.AutoDiscoverManager.<StartDiscoveryJourney>d__0.MoveNext()
    --- End of stack trace from previous location where exception was thrown ---
       at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
       at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
       at LyncConnectivityAnalyzerCore.Utilities.<RetrieveUserLocation>d__3e.MoveNext()
    [6/10/2014 7:31:00 AM] [SUMMARY_ERROR] Server discovery failed for unsecured external channel against http://lyncdiscover.mydomain.com/
    [6/10/2014 7:31:00 AM] [DEBUG] None, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST, MobilityMCXInternalLMXCheckGET,
    MobilityMCXInternalLMXCheckPOST, MobilityMCXExternalLMXCheckGET, MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
    [6/10/2014 7:31:00 AM] [SUMMARY]
    [6/10/2014 7:31:00 AM] [SUMMARY_ERROR] Automatic discovery meant for external network access failed. Please verify the server requirements at http://go.microsoft.com/fwlink/?LinkId=278998 .
    [6/10/2014 7:31:00 AM] [SUMMARY] Automatic discovery meant for internal network access succeeded from an external network which could be a potential security concern.
    [6/10/2014 7:31:00 AM] [MAINHEADING] Starting the requirement tests for Lync Mobile 2010 App
    [6/10/2014 7:31:00 AM] [INFO] Please wait; this test may take several minutes to complete...
    [6/10/2014 7:31:00 AM] [INFO] Testing the app requirements using the following discovery response:
    [6/10/2014 7:31:00 AM] [INFO] Access Location                          : Internal
    [6/10/2014 7:31:00 AM] [INFO] SIP Server Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] SIP Server External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] SIP Client Internal Access               : LYNC01.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] SIP Client External Access               : AccessEdge.mydomain.com
    [6/10/2014 7:31:00 AM] [INFO] Internal Auth broker service             : https://lync01.mydomain.com/Reach/sip.svc
    [6/10/2014 7:31:00 AM] [INFO] External Auth broker service             : https://lync.mydomain.com/Reach/sip.svc
    [6/10/2014 7:31:00 AM] [INFO] Internal Auto discover service           : https://lync01.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:31:00 AM] [INFO] External Auto discover service           : https://lync.mydomain.com/Autodiscover/AutodiscoverService.svc/root
    [6/10/2014 7:31:00 AM] [INFO] Internal MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] External MCX service                     : https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] Internal UCWA service                    : https://lync01.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:31:00 AM] [INFO] External UCWA service                    : https://lync.mydomain.com/ucwa/v0/applications
    [6/10/2014 7:31:00 AM] [INFO] Internal Webscheduler service            : https://lync01.mydomain.com/Scheduler
    [6/10/2014 7:31:00 AM] [INFO] External Webscheduler service            : https://lync.mydomain.com/Scheduler
    [6/10/2014 7:31:00 AM] [SUBHEADING] Starting tests for Mobility (MCX) service
    [6/10/2014 7:31:00 AM] [INFO] Verifying internal Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] Successfully obtained the WS-Metadata Exchange (MEX) document using GET. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [INFO] Verifying external Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [INFO] Successfully obtained the WS-Metadata Exchange (MEX) document using GET. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [INFO] Verifying internal Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [WARNING] Failed to obtain the WS-Metadata Exchange (MEX) document using POST for https://lync01.mydomain.com/Mcx/McxService.svc/mex. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [INFO] Verifying external Mobility (MCX) service: https://lync01.mydomain.com/Mcx/McxService.svc
    [6/10/2014 7:31:00 AM] [WARNING] Failed to obtain the WS-Metadata Exchange (MEX) document using POST for https://lync01.mydomain.com/Mcx/McxService.svc/mex. The service did not require authorization.
    [6/10/2014 7:31:00 AM] [SUMMARY] Completed tests for Mobility (MCX) service
    [6/10/2014 7:31:00 AM] [DEBUG] None, AutoExternalSecureD, AutoExternalUnsecureD, ManualDNSFail, ManualSecureD, ManualUnsecureD, AuthBrokerInternalLMXCheckGET, AuthBrokerInternalLMXCheckPOST, AuthBrokerExternalLMXCheckGET, AuthBrokerExternalLMXCheckPOST, MobilityMCXInternalLMXCheckPOST,
    MobilityMCXExternalLMXCheckPOST, LMXSIPServerInternalDNS, LMXSIPServerExternalDNS, MobilityUCWAInternalCheckPOST, MobilityUCWAExternalCheckPOST
    [6/10/2014 7:31:00 AM] [SUMMARY]
    [6/10/2014 7:31:00 AM] [SUMMARY_SUCCESS]
    Your deployment meets the minimum requirements for Lync Mobile 2010 App.

  • Lync 2013 /w Edge not working properly (internal/external same domain name and all "external" users"

    Hi,
    I've got some issues with a Lync 2013 setup.
    The config consists of 2 lync servers. One FE and one Edge. All seems to work except audio in meetings and Sip.
    The setup is like this (fake ip's used):
    Front End:
    Internal IP: 172.16.0.10
    External IP: x.x.185.10
    All ports open in Cisco ASA
    internal AD DNS: dialin/lync/meet/lyncdiscover to Front end internal ip. edge/lsedge/sip points to edge internal ip
    EDGE:
    Interal IP: 172.16.0.11 (no gateway configured)
    External IPS: x.x.185.11, x.x.185.12, x.x.185.13
    All external IP's are direct internet facing, no NAT (a firewall is in place).
    All external interfaces are using a wildcard certificate.
    All server are running in a remote data center, so basically no internal users. We all connect to the external interfaces. The Windows domain name (AD) is the same as our External DNS (companyname.com).
    Autodiscover works, we can logon, chat but there is no audio. The audio test failes. Also SIP is not working with a sip trunk.
    External DNS: sip/webconf/av are pointing to their external ip's. sipexternal is a cname to sip. lyncdiscover/lync/dialin/meet all point to the Frond end External ip.
    _sip._tls/_sipfederationtls.tcp/_xmpp-server.tcp all point to the sip.companyname.com ip.
    I just can't figure out what is wrong.

    @PSingh123 I'll try the logs in a minute and get back with the results.
    @PaulB_NZ Thanks for the input. In my opinion the FE does need an external IP. How else will you be able to connect if you are a remote worker?
    The Edge is (asfar as i know) needed for Enterprise voice and Federation with other (external) sip domains. It's not needed for basic (chat/video/whiteboard etc) Lync functionality for both internal and external (remote) users.
    The Edge is to communicate with services/users outside the origanisation.
    I do still think that the basic topology (FE with internal IP and Nat'ed external ip working with an Edge with internal IP and 1 external IP nat'ed to 3 DMZ ip's) is correct in this case.
    I can be wrong and in that case would like to be pointed to the correct configuration.
    75           
    Points
    Top 15
    PSingh123        
    Partner        
    Joined  Jun 2007        
    9
    PSingh123's threads
    Show activity

  • [Lync 2013] - Desktop Sharing and taking control

    Hello,
    In Lync 2013 when someone shares his/her screen and I'm taking control of the shared screen I have the following problem:
    Everything works fine when I'm in control with other person's desktop, however when the Lync IM/Sharing window looses focus and then the focus is regained by clicking on the shared desktop, all the input is frozen in the Lync IM window.
    for example:
    I take control of shared screen, do something on the shared desktop, then I open something on my own PC (the Lync window is loosing focus at this moment), then when I click on the shared screen inside Lync IM window to continue controlling the remote desktop
    any input to the Lync window is "frozen".
    There is some error sound comming everytime I click in the Lync IM window during this time - just as there was some invisible popup that is blocking interaction with parent window
    to solve this I have to once again loose focus of Lync IM window and then regain it again.
    This is on many machines (Windows 7 64bit / Windows 8.1 Preview 64bit) using Lync 2013 32bit with and without updates
    I'm using multiple monitors, but it's the same on a single display - just open Lync IM/Sharing window in one half of the screen and open notepad on other half (don't minimize windows, just switch between them during sharing)
    Best Regards

    Hi Bartek,
    Did the issue happen on Windows 7/8 32 bit using Lync 2013 32 bit?
    Try Clean Boot to disable all non-Microsoft services and start Lync again:
    How to Clean Boot:
    http://support.microsoft.com/kb/929135
    Since the OS is 64 bit, please remove Lync 2013 32 bit and install Lync 2013 client 64 bit and apply the latest update then test the issue again.
    Best Regards,
    Eason Huang
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Lync 2013 Photos will not update from AD

    I recently joined a company who has Lync 2013, Exchange 2010 and AD is at a 2003 functional level. We are experiencing issues where Lync photos are not updating from AD correctly. I have checked the pre-reqs;  Replicate this attribute to the Global
    Catalog is set for the ThumbnailPhoto attribute. We are also forcing photos from AD only (or no photo) by setting the following:
    "Set-CsClientPolicy -Identity PhotosControl -DisplayPhoto PhotosFromADOnly"  
    and finally we are setting the photo in ad using:
    "Import-RecipientDataProperty -Identity "Test User" -Picture -FileData ([Byte[]]$(Get-Content -Path "C:\pictures\testuser.jpg" -Encoding Byte -ReadCount 0))"
    The pictures being uploaded are under 10KB and update within Outlook but never updates on Lync. I have also manually tried running the "Update-CsAddressBook" command from Lync and waiting 24hours + but the photo will not update in Lync. I have
    also tried a 3rd party utility that grabs the attribute directly from each DC individually and each node is displaying the correct photo. Any Ideas?
    EDIT: I did some more testing and can say with quite a bit of certainty there is something not quite right on the Lync side of things. I started with the company over a month ago and although users can see my original photo that was added to AD, I myself
    do not even see it loaded in my client yet. I've completly dumped my local Lync cache but no change. Is there a specific Lync Server service that handles retrieving/pushing photos to the Lync clients?

    Thank you so much for your reply, it was very helpful in understanding how the service is suppose to work however I have still not been able to correct the issue.
    What I have found by using your article may have narrowed down the scope of the problem. I was able to find that on our Lync file store, the cached contacts/photos are being updated daily (as expected) and actually contain the correct photos. I confirmed
    this be using abserver.exe on the .lsabs file and then locating the contactID for a few users I know are not updating properly. Once I have their contact ID I simply look for their .photo file in the cached files, copy it out to a different location and change
    it to a .jpeg. To my surprise the photos are actually the correctly updated ones, so why are these no getting to the users/clients? I have gone through and deleted my local cache folder as well as the registry key HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Lync
    but unfortunately no change on my Client. I still see these users original photos.
    Another piece of the puzzle; We are also working on letting mobile devices connect to our Lync infrasructure as well. This is not fully functional yet however during my testing I did get Lync client for android running for a little while and low and behold
    the pictures are actually correct on my mobile device!! Surely this must give some kind of clue?
    We are planning to upgrade Exchange from 2010 to 2013 and I hoping that leveraging the HiDef photo capabilities for Lync 2013 with Exchange 2013 may fix this issue. What do you guys think?
    More info on the environment:
    4 main sites + remote users
    ~7DC's - 2003 DFL (1 at each site + a few at HQ)
    3 Lync Front end servers (2013) (All located at central HQ)
    2 Lync edge server (2013) (All located at central HQ)
    1 - 2010 Exchange server (Located at central HQ)
    2013 Lync Client version 15.0.4675.1000 MSO 15.0.4675.1002 64bit
    About 100 HP 4110 Lync Edition Desk phones
    Users's workstations are either Windows 7 Enterprise or Windows 8.1 Enterprise

  • Lync 2013 PSTN calling not working with Sonus SBC 1000 over TLS and SRTP

    Dear All,
    We have recently installed Lync 2013 Enterprise Edition with a Pool of 3 FE Servers (MEDIATION COLLOCATED).
    We need to implement TLS and SRTP with Sonus SBC 1000. However calls are not routing b/w SBC and Lync.
    We are using wild card certificate with multiple SIP Domains as SAN(s), for internal FE servers as well SBC.
    Also i would like to mentioned here that inbound and outbound calls are routing properly when we tested it over TCP.
    When I move to TLS Only calls from Lync to SBC (outgoing) are working without encryption.
    Here are the OCS Logger traces for incoming calls which are not landing on lync:
    TL_INFO(TF_PROTOCOL) [1]2C5C.0D30::04/30/2014-14:35:18.020.00026518.020.00026518.020.00026518.020.00026518.020.00026518.020.00026518.020.00026518.020.000265d2
    (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[3491463749]
    >>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_AE0419>], 10.10.0.11:5067->10.10.7.50:25678
    SIP/2.0 400 Bad Request
    FROM: "3158222726"<sip:[email protected]>;tag=ac3201ce-4d7
    TO: <sip:[email protected]:5067>;epid=D2091CF753;tag=f373543c
    CSEQ: 2 INVITE
    CALL-ID: [email protected]
    VIA: SIP/2.0/TLS 10.10.7.50:5067;branch=z9hG4bK-UX-ac32-01ce-0b14
    CONTENT-LENGTH: 0
    SERVER: RTCC/5.0.0.0 MediationServer
    ------------EndOfOutgoing SipMessage
    TL_INFO(TF_PROTOCOL) [1]2C5C.0D30::04/30/2014-14:35:18.027.00026518.027.00026518.027.00026518.027.00026518.027.00026518.027.00026518.027.00026518.027.000265d7
    (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[2666394843]
    >>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_370F030>], 10.10.0.11:58059->10.10.0.13:5061
    SERVICE sip:2138797082;[email protected];user=phone SIP/2.0
    FROM: <sip:2138797082;[email protected];user=phone>;epid=DCFDB95F4C;tag=17d286a93
    TO: <sip:2138797082;[email protected];user=phone>
    CSEQ: 3 SERVICE
    CALL-ID: de750f98bdd94e908be5f2f975228ff7
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TLS 10.10.0.11:58059;branch=z9hG4bKd47f1d3c
    CONTACT: <sip:[email protected];gruu;opaque=srvr:MediationServer:CiGdW3iH5FiI3Qvr3PIKGQAA>
    CONTENT-LENGTH: 630
    SUPPORTED: gruu-10
    USER-AGENT: RTCC/5.0.0.0 MediationServer
    CONTENT-TYPE: application/msrtc-reporterror+xml
    <?xml version="1.0" encoding="us-ascii"?>
    <reportError xmlns="http://schemas.microsoft.com/2006/09/sip/error-reporting">
    <error callId="[email protected]" fromUri="sip:3158222726;[email protected];user=phone" toUri="sip:2138797082;[email protected];user=phone" fromTag="ac3201ce-4d7"
    toTag="" requestType="INVITE" contentType="application/sdp;call-type=audio" responseCode="400"><diagHeader>10013;reason="Gateway peer in inbound call is not found in topology document or does not depend
    on this Mediation Server"</diagHeader><progressReports /></error></reportError>------------EndOfOutgoing SipMessage
    Call
    Send SMS
    Add to Skype
    You'll need Skype CreditFree via Skype

    @Paul, Thanks for you response.
    All ports / IP Add / DNS are defined properly. Telenet on listening port is working.
    We are using Public Certificate for 3 Domains (wild card) and same is loaded and verified in SBC
    I've not reviewed the OCS logs properly posted above.
    What i've found or seems to me is that in a TLS Calls:
    After receiving SIP Invite from SBC, mediation server started TLS Negotiation Process b/w Lync 2013 Server Pool and it fails.
    SIP Domains:
    contoso.com (default)
    fabrikam.com
    Lync FE Pool (lync.contoso.com
    Here are the some more logs.
    TL_INFO(TF_PROTOCOL) [0]2DF8.2930::05/01/2014-11:50:31.612.00025e49 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[2716989131]
    <<<<<<<<<<<<Incoming SipMessage c=[<SipTlsConnection_103DFE0>], 10.10.0.11:5067<-10.10.7.50:24591
    INVITE sip:[email protected]:5067 SIP/2.0
    FROM: "3158222726" <sip:[email protected]>;tag=ac3201ce-ae
    TO: <sip:[email protected]:5067>
    CSEQ: 2 INVITE
    CALL-ID: [email protected]
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TLS 10.10.7.50:5067;branch=z9hG4bK-UX-ac32-01ce-010c
    CONTACT: <sip:[email protected]:5067;transport=TLS>
    CONTENT-LENGTH: 406
    SUPPORTED: replaces,update,100rel
    USER-AGENT: SONUS SBC1000 3.1.2v293 Sonus SBC
    CONTENT-TYPE: application/sdp
    ALLOW: INVITE, ACK, CANCEL, BYE, NOTIFY, OPTIONS, REFER, REGISTER, UPDATE, PRACK
    P-ASSERTED-IDENTITY: "3158222726" <sip:[email protected]>
    v=0
    o=SBC 9 1001 IN IP4 10.10.7.50
    s=VoipCall
    c=IN IP4 10.10.7.50
    t=0 0
    m=audio 16418 RTP/AVP 8 0 101 13
    c=IN IP4 10.10.7.50
    a=rtpmap:8 PCMA/8000/1
    a=rtpmap:0 PCMU/8000/1
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-15
    a=rtpmap:13 CN/8000
    a=ptime:20
    a=tcap:1 RTP/SAVP
    a=pcfg:1 t=1
    a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:pqL6Tke8pVmXPuplJ1G3+Sr9jM97H8R7iBagWzzh|2^31|1:1
    a=sendrecv
    ------------EndOfIncoming SipMessage
    TL_INFO(TF_PROTOCOL) [1]2DF8.0E04::05/01/2014-11:50:31.665.00025e8e (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[2716989131]
    >>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_103DFE0>], 10.10.0.11:5067->10.10.7.50:24591
    SIP/2.0 100 Trying
    FROM: "3158222726"<sip:[email protected]>;tag=ac3201ce-ae
    TO: <sip:[email protected]:5067>
    CSEQ: 2 INVITE
    CALL-ID: [email protected]
    VIA: SIP/2.0/TLS 10.10.7.50:5067;branch=z9hG4bK-UX-ac32-01ce-010c
    CONTENT-LENGTH: 0
    ------------EndOfOutgoing SipMessage
    TL_INFO(TF_CONNECTION) [1]184C.0EFC::05/01/2014-11:50:32.652.00025f32 (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(454))[946832530] $$begin_record
    Severity: information
    Text: TLS negotiation started
    Local-IP: 10.10.0.11:5061
    Peer-IP: 10.10.0.11:52529
    Connection-ID: 0x10BE00
    Transport: TLS
    $$end_record
    TL_INFO(TF_PROTOCOL) [1]184C.0EFC::05/01/2014-11:50:32.669.00026236 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[1853494582] $$begin_record
    Trace-Correlation-Id: 1853494582
    Instance-Id: 425D
    Direction: incoming
    Peer: 10.10.0.11:52529
    Message-Type: request
    Start-Line: NEGOTIATE sip:127.0.0.1:5061 SIP/2.0
    FROM: <sip:contoso.com>;ms-fe=LYNCFE1.fabrikam.com
    TO: <sip:contoso.com>
    CALL-ID: aa53739ef9b34b93ba9c97d3ee56cb99
    CSEQ: 1 NEGOTIATE
    VIA: SIP/2.0/TLS 10.10.0.11:52529
    MAX-FORWARDS: 0
    CONTENT-LENGTH: 0
    SUPPORTED: NewNegotiate
    SUPPORTED: ECC
    REQUIRE: ms-feature-info
    SERVER: RTC/5.0
    $$end_record
    TL_INFO(TF_CONNECTION) [1]184C.0EFC::05/01/2014-11:50:32.669.0002636e (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(383))[946832530] $$begin_record
    Severity: information
    Text: Connection established
    Peer-IP: 10.10.0.11:52529
    Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
    Peer-Cert: contoso.com(LYNCFE1.fabrikam.com)
    Transport: M-TLS
    Data: alertable="yes"
    $$end_record
    TL_WARN(TF_CONNECTION) [1]184C.0EFC::05/01/2014-11:50:32.669.00026387 (SIPStack,SIPAdminLog::WriteConnectionEvent:SIPAdminLog.cpp(386))[946832530] $$begin_record
    Severity: warning
    Text: The pool FQDN provided by the peer in its NEGOTIATE feature information does not match the pool configured in CMS for the server FQDN that it provided
    Peer-IP: 10.10.0.11:52529
    Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
    Peer-Cert: contoso.com(LYNCFE1.fabrikam.com)
    Transport: M-TLS
    Data: fqdn="LYNCFE1.fabrikam.com";pool="contoso.com";expected-fqdn="lync.contoso.com";info="Possible server configuration issue"
    $$end_record
    TL_INFO(TF_DIAG) [1]184C.0EFC::05/01/2014-11:50:32.670.000265be (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(802))[1853494582] $$begin_record
    Severity: information
    Text: Routed a locally generated response
    SIP-Start-Line: SIP/2.0 200 OK
    SIP-Call-ID: aa53739ef9b34b93ba9c97d3ee56cb99
    SIP-CSeq: 1 NEGOTIATE
    Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
    $$end_record
    TL_INFO(TF_PROTOCOL) [1]184C.0EFC::05/01/2014-11:50:32.670.00026615 (SIPStack,SIPAdminLog::ProtocolRecord::Flush:ProtocolRecord.cpp(265))[1853494582] $$begin_record
    Trace-Correlation-Id: 1853494582
    Instance-Id: 425E
    Direction: outgoing;source="local"
    Peer: lync.contoso.com:52529;ms-fe=LYNCFE1.fabrikam.com
    Message-Type: response
    Start-Line: SIP/2.0 200 OK
    FROM: <sip:contoso.com>;ms-fe=LYNCFE1.fabrikam.com
    To: <sip:contoso.com>;tag=C3A751556F332F7265E9BA2517C878D4
    CALL-ID: aa53739ef9b34b93ba9c97d3ee56cb99
    CSEQ: 1 NEGOTIATE
    Via: SIP/2.0/TLS 10.10.0.11:52529;ms-received-port=52529;ms-received-cid=10BE00
    Content-Length: 0
    Require: ms-feature-info
    Supported: NewNegotiate,OCSNative,ECC,IPv6,TlsRecordSplit
    Server: RTC/5.0
    $$end_record
    TL_INFO(TF_PROTOCOL) [1]2DF8.1078::05/01/2014-11:50:32.671.000266da (S4,SipMessage.DataLoggingHelper:sipmessage.cs(774))[720988281]
    >>>>>>>>>>>>Outgoing SipMessage c=[<SipTlsConnection_F8A09B>], 10.10.0.11:52529->10.10.0.11:5061
    SERVICE sip:2138797082;[email protected];user=phone SIP/2.0
    FROM: <sip:2138797082;[email protected];user=phone>;epid=16FEE4A02E;tag=22fd877f3a
    TO: <sip:2138797082;[email protected];user=phone>
    CSEQ: 3 SERVICE
    CALL-ID: ac0f7bc4cdc94c1dbd0bb51c7c02c890
    MAX-FORWARDS: 70
    VIA: SIP/2.0/TLS 10.10.0.11:52529;branch=z9hG4bK67a4c9d1
    CONTACT: <sip:[email protected];gruu;opaque=srvr:MediationServer:CiGdW3iH5FiI3Qvr3PIKGQAA>
    CONTENT-LENGTH: 628
    SUPPORTED: gruu-10
    USER-AGENT: RTCC/5.0.0.0 MediationServer
    CONTENT-TYPE: application/msrtc-reporterror+xml
    - <reportError xmlns="http://schemas.microsoft.com/2006/09/sip/error-reporting">
    - <error callId="[email protected]"
    fromUri="sip:3158222726;[email protected];user=phone"
    toUri="sip:2138797082;[email protected];user=phone"
    fromTag="ac3201ce-ae"
    toTag=""
    requestType="INVITE"
    contentType="application/sdp;call-type=audio"
    responseCode="400">
    <diagHeader>10013;reason="Gateway peer in inbound call is not found in topology document or does not depend on this Mediation Server"</diagHeader>
    <progressReports/>
    - </error>
    ------------EndOfOutgoing SipMessage

  • Lync 2013 Edge replication not working

    hi, I have a Lync 2013 Edge replication issue - it is simply not working.
    UpToDate           : False
    ReplicaFqdn        : LyncEdge.contoso.com
    I have already checked the following:
    1) telnet from FEP servers to the Edge sever on port 4443 is working
    2) Certificates are installed correctly - Lync Federation, Voice/Video to Skype, Lync Mobile is all working fine.
    3) Replication traffic checking showing the following error in XDS logs:
    (000000000126DB35)[FileTransferTask(11, 9/03/2015 2:44:24 PM): {TASK_NOT_STARTED, fromReplica, [lyncedge.contoso.com, HttpsWebService, 4443], 0}] Failed to copy files from replica. Exception: [System.ServiceModel.Security.MessageSecurityException: The HTTP
    request was forbidden with client authentication scheme 'Anonymous'. ---> System.Net.WebException: The remote server returned an error: (403) Forbidden.
       at System.Net.HttpWebRequest.GetResponse()
       at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       --- End of inner exception stack trace ---
    Server stack trace:
       at System.ServiceModel.Channels.HttpChannelUtilities.ValidateAuthentication(HttpWebRequest request, HttpWebResponse response, WebException responseException, HttpChannelFactory factory)
       at System.ServiceModel.Channels.HttpChannelUtilities.ValidateRequestReplyResponse(HttpWebRequest request, HttpWebResponse response, HttpChannelFactory factory, WebException responseException, ChannelBinding channelBinding)
       at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.Rtc.Xds.Replication.Common.IReplicationWebService.DownloadFiles(String senderFqdn, String sourceDirPath, String tempDirPath)
       at Microsoft.Rtc.Xds.Replication.FileTransfer.FileTransferTask.CopyFilesFromReplicaUsingWcf(String fromDir, String tmpDir, String toDir)]
    I have checked certificate stores: there are only 34 certificates in the Root folder and the SendTrustedIssuerList reg. key has been configured, which did not solve the issue.
    Any idea how to troubleshoot this or possible root causes?

    Try Test-CsComputer on the Frontend Servers and the Edge Servers. This should check Windows Firewall exceptions are correct. Then check permissions on your Lync fileshare. You can also try to reinstall CMS Database with the following command (user must be
    memeber of CsAdministrator group and sysadmin group of SQL Server)
    Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn CMS.FQDN 
    -SqlInstanceName DBInstance -Verbose

  • Lync 2013 Group Chat not working

    We have a 2010 server and when I move people over to 2013 group chat does not work. I can select the people I want to talk to, but they don't see any of the conversations. When I move the back to the 2010 it works again.
    We are running office 2013, lync 2013 and exchange 2010. 
    Any suggestions?

    Have you installed Persistent Chat in Lync 2013? You'll need to migrate the group chat data to the Persistent Chat pool and setup a Persistent Chat Endpoint for the legacy 2010 group chat clients, see: http://technet.microsoft.com/en-us/library/jj204901.aspx
    Please mark posts as answers/helpful if it answers your question.
    Blog
    Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

  • Lync 2013 Desktop does not start on WIndows 8.1

    My Office 365 version of Lync 2013 64bit crashes every time I start it.  There is no error message just the "Microsoft Lync has stopped working" message with Close option.  In further looking for a solution, I found the suggestion to
    uninstall the Intel Bluetooth drivers but my system uses Realtek Filter drivers.  I have looked  in the event logs and found:
    Log Name:      Application
    Source:        Windows Error Reporting
    Date:          2014-09-11 1:47:20 PM
    Event ID:      1001
    Task Category: None
    Level:         Information
    Keywords:      Classic
    User:          N/A
    Computer:      --------Win8
    Description:
    Fault bucket 85949488684, type 4
    Event Name: APPCRASH
    Response: Not available
    Cab Id: 0
    Problem signature:
    P1: lync.exe
    P2: 15.0.4641.1000
    P3: 53c5ce3c
    P4: KERNELBASE.dll
    P5: 6.3.9600.17055
    P6: 532954fb
    P7: e06d7363
    P8: 0000000000005bf8
    P9:
    P10:
    Attached files:
    C:\Users\Yves\AppData\Local\Temp\WERCA6B.tmp.WERInternalMetadata.xml
    These files may be available here:
    C:\Users\Yves\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_lync.exe_1f7a49ef615ca788e016ddaf8db0d1fb92c4a8e9_00000000_256fdc4d
    Analysis symbol:
    Rechecking for solution: 0
    Report Id: aa908032-39db-11e4-8280-48d224dc5142
    Report Status: 0
    Hashed bucket: 61000269e077a9a343a6fe9bbb7efc54
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Windows Error Reporting" />
        <EventID Qualifiers="0">1001</EventID>
        <Level>4</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-09-11T17:47:20.000000000Z" />
        <EventRecordID>143379</EventRecordID>
        <Channel>Application</Channel>
        <Computer>Fedmet-YL-Win8</Computer>
        <Security />
      </System>
      <EventData>
        <Data>85949488684</Data>
        <Data>4</Data>
        <Data>APPCRASH</Data>
        <Data>Not available</Data>
        <Data>0</Data>
        <Data>lync.exe</Data>
        <Data>15.0.4641.1000</Data>
        <Data>53c5ce3c</Data>
        <Data>KERNELBASE.dll</Data>
        <Data>6.3.9600.17055</Data>
        <Data>532954fb</Data>
        <Data>e06d7363</Data>
        <Data>0000000000005bf8</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>
    C:\Users\Yves\AppData\Local\Temp\WERCA6B.tmp.WERInternalMetadata.xml</Data>
        <Data>C:\Users\Yves\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_lync.exe_1f7a49ef615ca788e016ddaf8db0d1fb92c4a8e9_00000000_256fdc4d</Data>
        <Data>
        </Data>
        <Data>0</Data>
        <Data>aa908032-39db-11e4-8280-48d224dc5142</Data>
        <Data>0</Data>
        <Data>61000269e077a9a343a6fe9bbb7efc54</Data>
      </EventData>
    </Event>
    A lot of sites suggest to uninstall Intel Bluetooth drive but I does not have Intel Bluetooth.

    Go to your computer manufacturer’s website and update all driver packages for your computer, especially:
    Audio drivers
    Bluetooth drivers
    System chipset drivers
    webcam drivers
    Important Note:
    If you use office 64 bit, Lync 2013 must be 64 bit also. {And vice versa, If you use office 32 bit, Lync 2013 must be 32 bit}
    Also check answer of Eric to fix this issue
    http://social.technet.microsoft.com/Forums/en-US/e8268935-e97c-4033-9a2e-02734b4390bf/lync-2013-client-on-windows-81-stuck-at-starting?forum=ocsclients
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • Lync 2013 domain discovery not working, but Lync 2010 works flawlessly

    We are using Lync 2013 and Lync 2010 in our company. Upon installation Lync 2010 can connect absolutely fine with for example [email protected], but when we use Lync 2013 we receive a DNS error saying it cannot resolve the domain when using the same
    method. I have to manually enter the internal and external servers on each deployment of Lync 2013 to sipdir.online.lync.com:443 in order for successfully login to Lync 2013. We are upgrading all users to Lync 2013 and I want to avoid having to do this
    on every deployment. This has always been an issue and not something that recently became an issue.
    I have double checked my CNAME and SRV from my host provider and everything is as it should be. Contacting MS support they made me change my preferred DNS to 8.8.8.8 on the network adapter for the PC, but that breaks everything you connect to internally and
    is not a solution to this issue.
    Any ideas?

    Hi,
    The forum you posted is for Lync Server On Premise only. The issue is more related to Lync online, you can also post a question on Office365 forum for assistance. Thank you for your understanding.
    http://community.office365.com/en-us/f/166.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Webdynpro ABAP not working from internet

    Hello,
    I´m new at webdynpro and portal...
    We have a ess portal with webdynpro abap and java. Our employees may access it from intranet and all works fine, and from internet when they are in the outside.
    From internet the webdynpro abap gives the message that the server cannot be reached. The server is our production backend and is not open to the exterior.
    Is there a way to make this work, from inside and outside?
    Teresa

    Yes sure,
      so you have to set the parameter wdisp/add_clientprotocol_header = 1 in the web dispatcher profile.
      Good references are:
    [http://help.sap.com/saphelp_nw04s/helpdata/en/de/89023c59698908e10000000a11402f/frameset.htm|http://help.sap.com/saphelp_nw04s/helpdata/en/de/89023c59698908e10000000a11402f/frameset.htm]
    [http://wiki.sdn.sap.com/wiki/display/BSP/HandlingBinaryData|http://wiki.sdn.sap.com/wiki/display/BSP/HandlingBinaryData]
    and this
    [http://help.sap.com/saphelp_nw04s/helpdata/en/9a/53a2a4a45e244aa189c2b7065a0b78/frameset.htm|http://help.sap.com/saphelp_nw04s/helpdata/en/9a/53a2a4a45e244aa189c2b7065a0b78/frameset.htm]
    Sergio

  • Library sharing not working from all accounts

    I am using iTunes Library sharing from my iMac to enable access to mucis & movies on ios devices on my local network.  From my login on the iMac this works fine and the shared library appears on the "more" menu in the music app on my ipad whenever itunes is open on the iMac.
    I have made the same set up on my daughters login on the same iMac but her shared library will not show up on any devices on the network.  Her shared library is however visible in iTunes when I log into my account on the same iMac via fast user switching.  Other functionality of itunes from her login seems fine & it can airplay to my ATV without problem.
    There is no difference in the set up of iTunes between her login and mine:  neither have home sharing enabled, and both have 'share my library on my local network/entire library' selected in itunes prefence.
    I have tried with home sharing enabled and this made no difference.
    I can only guess that there is a preference pane or similar in her login that is corrupted.  Any ideas welcome.
    Thanks
    JW
    itunes 10.6.3
    osx 10.7.4
    imac mid 24" mid 2007
    ipad latest model 3g/wifi
    ios 5.1.1

    Once again updating and hoping (praying) somebody will get this:
    I still cannot get Library Sharing to work, and I think it is a bug with Windows7 64 Bit Version:
    1) Uninstall
    I have uninstalled everything as per Knowledge Base http://support.apple.com/kb/HT1923
    I even removed all regstry-entries pointing to Apple software (mainly under HKLM and HKLU). I removed all "Apple Computers" Folders in USER\AppData
    2) Re-Install
    Reboot & Clean reinstall
    New empty itunes library (Removed old itunes Folder in MyMusic)
    Imported one CD
    3) Sharing
    Turned on sharing in the settings.
    Started up another PC: nothing:
    Started up Apple Remote (2.0.1 - 229) on iPad (iOs 4.2.1): Entered correct four digit code in Itunes
    A greyed-out Itunes symbol without a name appears (normally reading "BlaBlas Library")
    4) Sharing Part 2
    Using the other Computer (Notebook W32bit)
    using sharing feature in the other direction (Notebook -> Windows 7 64Bit PC) works
    Apple Remote to this PC also works.
    5) Sharing Part 3
    Created an entire Blank new User with a new empty Itunes Library. Imported one CD: Same Problem.
    Conclusion: Bonjour or some other component of ITunes sharing is broken. What should I do. Can I leave a bug report somewhere?
    Please help me!

  • Screen Sharing not working from maverick macair to 10.6 mac mini

    I'm not able to connect to mac mini (10.6.8) from mac book ait running Maverick.
    Mac mini set-up is the following:
    Screen Sharing enabled
    Firewall disabled
    Connection to the mac mini working from windows pc (VNC connection)
    VNC connection enabled with password
    Mac Book air situation is:
    Sreen Sharing (client) 1.3.1
    os 10.9.1
    What happens:
    from air it starts the connection
    ther the air stais waiting: "Receiving first screen ..." messsage with no response from mini
    if I check the console messages in mini there is a message about CGContextSetInterpolationQuality from AppleVNCServer that receives and invalid context
    Can anybody help?

    Hi, try this...
    https://discussions.apple.com/thread/5468647?tstart=0
    By Mad9000...
    This is what worked for me:
    1. Go to System Preferences > Sharing and uncheck Screen Sharing and File Sharing
    2. Restart Mac
    3. System Preferences > Sharing and recheck Screen Sharing and File Sharing
    4. Problem solved (for me anyway)

Maybe you are looking for