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

Similar Messages

  • [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 desktop sharing is giving Black screen when using virtual machine

    Hello,
    We have a user who is connecting our network through VPN and connecting to a virtual machine. He is able to login to lync but when he start desktop sharing or some one sharing the desktop to him, he is getting black screen. He is using windows 7 and Lync
    2013 client. Please advice

    Hi,
    Did he receive any error message?
    Please double check the ports for VPN traffic.
    Please also enable logging on Lync client for further troubleshooting.
    What’s more, when users connect to the corporate network using a VPN client, Lync media traffic is sent through the VPN tunnel. This configuration can create additional latency and jitter because media traffic must pass through an additional layer of encryption
    and decryption. The issue is compounded when the VPN concentrator is busy.
    You can configuration like this:
    Lync client connect to the Access Edge Server for all signaling connections when on the corporate VPN. However, Media sessions routed through the A/V Edge Server interface instead of establishing connectivity through the VPN tunnel.
    More details:
    http://blogs.technet.com/b/nexthop/archive/2011/11/15/enabling-lync-media-to-bypass-a-vpn-tunnel.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • 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

  • External Meetings using Lync Web App vs Lync 2013 Desktop client

    We have LYNC Server 2013 deployed on premise. Our clients are LYNC 2013. When someone external to our organization sends us a Lync meeting request we are able to connect with our Lync 2012 desktop client but only Audio is available. We cannot share
    the desktop. If however we connect to the external meeting using the Lync Web App (by specifying
    ?sl=1 at the end of the meeting url) we are able to use all the services like audio, desktop sharing etc.
    I've found the following articles that suggest that the desktop clients are not the preferred choice to connect to external meetings.
    http://blog.schertz.name/2011/11/forcing-lync-web-app/
    http://www.computer-talk.com/en/blog/item/attendees-cannot-join-your-lync-web-conference
    Can anyone advise as to why the desktop clients are restrictive and if there is a fix and if not how can we force users to use the Lync Web App to connect to external meetings?
    Our lync 2013 desktop clients use the following ports:
    PS C:\Users\am03744ad> Get-CsConferencingConfiguration
    Identity                           : Global
    MaxContentStorageMb                : 500
    MaxUploadFileSizeMb                : 500
    MaxBandwidthPerAppSharingServiceMb : 375
    ContentGracePeriod                 : 15.00:00:00
    ClientMediaPortRangeEnabled        : True
    ClientMediaPort                    : 5350
    ClientMediaPortRange               : 40
    ClientAudioPort                    : 50020
    ClientAudioPortRange               : 20
    ClientVideoPort                    : 58000
    ClientVideoPortRange               : 20
    ClientAppSharingPort               : 42000
    ClientAppSharingPortRange          : 20
    ClientFileTransferPort             : 42020
    ClientFileTransferPortRange        : 20
    ClientSipDynamicPort               : 7100
    ClientSipDynamicPortRange          : 3
    Organization                       :
    HelpdeskInternalUrl                :
    HelpdeskExternalUrl                :
    ConsoleDownloadInternalUrl         :
    ConsoleDownloadExternalUrl         :

    You should be fine using the full Lync client, it's not restricted by default.  If there's an issue, it's typically in the networking related to your edge, or the edge of the organization you're federating with.
    The reason the web client is preferred by many (not all, and that's not an official Microsoft stance), is simply that if everyone uses the web client, it's a consistent experience for the attendees and you don't have to worry about the status of attendee's Lync
    environment or federation.
    Can your external users share a desktop with internal users?  Can they do it externally in a conference hosted by you?  Can the remote organization share desktops with you when connected to your conferences?  And in these conferences,
    have the marked you as presenter so you can present your desktop?
    There's no good way to automatically force users to use the web app each time unfortunately.  The other organization would need to hardcode that ?sl=1 into each meeting invite sent.
    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".
    SWC Unified Communications

  • Lync 2013 desktop usesr and Lync Web users.

    When i send IM to users within my group using  Lync 2013 desktop client, the recipients on Lync Web app does not get my font color or font syle. Is there settings to get the font color and font style I use on the desktop client to appear in the Lync
    web app users windows as I send it over.

    Hi,
    I test in my Lync environment but didn’t find the issue. As Anthony said, there is no set except the setting “Change Font…” on Lync client Options. You can try to download the latest version for Lync client from Microsoft Website
    and then test again.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Differences & Similarities between Lync 2013 desktop & Lync 2013 mobile

    We've got Lync 2013 installed on our desktops.  We now want to introduce Lync 2013 for both iPhone's and Android's.
    Is there anywhere I can get a list of what functionality the desktop & mobile versions share, as well as what they don't.
    If this is in the wrong place, apologies.
    Duncan

    Sorry, just found the information.
    Guess I didn't look very well in the first place. :(

  • EWS not deployed anymore to Lync 2013 Desktop Clients, Mobile Clients still working fine

    Hello dear community,
    the subject of EWS in conjunction with Lync 2013 has been discussed a lot here .
    However, I could not find here any solution for my problem and I'm (almost) at my end.
    Following scenario - 1 x Lync 2013 BE server, 1 x Lync 2013 Edge server, 1 x reverse proxy (IIS ARR). This Lync 2013 deployment
    was installed about two months ago and integrated into existing IT landscape. Everything worked wonderfully - desktop and mobile clients were able to connect from inside and outside our organization, EMS was deployed to both desktop and mobile clients.
    After that there are no any configuration changes made on Lync server, and yesterday, shortly before an important presentation
    I've found, that EWS is not deployed anymore on all desktop clients. Mobile clients, however, continue to function smoothly.
    I have tried the following: restart Lync and reverse proxy servers - without success, Lync Connectivity Analyzer shows all
    green (internal and external), all relevant tests with Microsoft Remote Connectivity Analyzer were passed, also analysis using Wireshark brought nothing.
    I must to say that a week ago I installed SP3 for Exchange 2010 - can it may be because? Also appears more
    times a day the following error message in Event Viewer on the back-end server (language of operation system is German):
    Protokollname: Lync Server
    Quelle:        LS Storage Service
    Datum:         05.12.2013 19:23:14
    Ereignis-ID:   32054
    Aufgabenkategorie:(4006)
    Ebene:         Fehler
    Schlüsselwörter:Klassisch
    Benutzer:      Nicht zutreffend
    Computer:      SERVER-11.Speedpoint.local
    Beschreibung:
    EWS-AutoErmittlungsfehler im Speicherdienst.
    ExchangeAutodiscoverException: code=ErrorEwsAutodiscover, reason=GetUserSettings
    failed, smtpAddress = xxx, Autodiscover Uri=https://autodiscover.xxx.de/autodiscover/autodiscover.svc, Autodiscover WebProxy=<NULL> ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed.
    Das Stammelement ist nicht vorhanden. ---> System.Xml.XmlException: Das Stammelement ist nicht vorhanden.
       bei System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
       bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
       bei System.Xml.XmlCharCheckingReader.Read()
       bei Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read()
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
       --- Ende der internen Ausnahmestapelüberwachung ---
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetUserSettings(List`1 smtpAddresses, List`1 settings, Nullable`1 requestedVersion, Uri& autodiscoverUrl)
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetSettings[TGetSettingsResponseCollection,TSettingName](List`1 identities, List`1 settings, Nullable`1 requestedVersion, GetSettingsMethod`2 getSettingsMethod, Func`1 getDomainMethod)
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(List`1 smtpAddresses, List`1 settings)
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetSoapUserSettings(String smtpAddress, List`1 requestedSettings)
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(String userSmtpAddress, UserSettingName[] userSettingNames)
       bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
       --- End of inner exception stack trace ---
       bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
       bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.GetUserEwsSettings(StoreContext ctx, String smtpAddress, CacheMode cacheMode)
    Ursache: Der AutoErmittlungs-URI war nicht richtig konfiguriert oder nicht erreichbar. Eventuell besteht ein Problem mit dem Proxy, oder andere Fehler liegen
    vor.
    Lösung:
    Überprüfen Sie die Ereignisdetails. Überprüfen Sie, ob der URI des AutoErmittlungsdiensts ordnungsgemäß konfiguriert und erreichbar ist. Prüfen Sie, ob die Proxyeinstellungen ordnungsgemäß konfiguriert sind und der Proxy erreichbar ist. Prüfen Sie die Konfiguration
    der AutoErmittlung zwischen Lync und Exchange Autodiscovery anhand des Handbuchs zur Problembehandlung. Wenn das Problem weiterhin besteht, wenden Sie sich mit den Ereignisdetails an das Supportteam Ihrer Organisation.
    Ereignis-XML:
    < Event xmlns="">
      <System>
        <Provider Name="LS Storage Service" />
        <EventID Qualifiers="53158">32054</EventID>
        <Level>2</Level>
        <Task>4006</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-12-05T18:23:14.000000000Z" />
        <EventRecordID>19949</EventRecordID>
        <Channel>Lync Server</Channel>
        <Computer>SERVER-11.Speedpoint.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>ExchangeAutodiscoverException: code=ErrorEwsAutodiscover, reason=GetUserSettings failed, smtpAddress=xxx, Autodiscover Uri=https://autodiscover.xxx.de/autodiscover/autodiscover.svc, Autodiscover WebProxy=&lt;NULL&gt; ---&gt;
    Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed.
    Das Stammelement ist nicht vorhanden. ---&gt; System.Xml.XmlException: Das Stammelement ist nicht vorhanden.
       bei System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
       bei System.Xml.XmlTextReaderImpl.ParseDocumentContent()
       bei System.Xml.XmlCharCheckingReader.Read()
       bei Microsoft.Exchange.WebServices.Data.EwsXmlReader.Read()
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
       --- Ende der internen Ausnahmestapelüberwachung ---
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverRequest.InternalExecute()
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetUserSettings(List`1 smtpAddresses, List`1 settings, Nullable`1 requestedVersion, Uri&amp; autodiscoverUrl)
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetSettings[TGetSettingsResponseCollection,TSettingName](List`1 identities, List`1 settings, Nullable`1 requestedVersion, GetSettingsMethod`2 getSettingsMethod, Func`1 getDomainMethod)
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(List`1 smtpAddresses, List`1 settings)
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.InternalGetSoapUserSettings(String smtpAddress, List`1 requestedSettings)
       bei Microsoft.Exchange.WebServices.Autodiscover.AutodiscoverService.GetUserSettings(String userSmtpAddress, UserSettingName[] userSettingNames)
       bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
       --- End of inner exception stack trace ---
       bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.SendGetUserSettingsRequest(StoreContext ctx, String smtpAddress)
       bei Microsoft.Rtc.Internal.Storage.Exchange.ExchangeContext.GetUserEwsSettings(StoreContext ctx, String smtpAddress, CacheMode cacheMode)
    < /Data>
      </EventData>
    < /Event>
    However Event ID
    32054
    was actually
    always there
    – even
    when everything
    worked fine -
    but with
    some another content.
    That's why I
    don't know
    if I
    should take it seriously.
    Thanks a lot in advance for your help!

    Hi MiF,
    The issue may cause by the Network Service account that the Lync Storage Service uses does not have access to the private key in used by the oAuth certificate. Please do with the following steps:
    Open MMC and add the “Certificates” Snap-in (Local Computer)
    Open Personal | Certificates and find the the Certificate being used for OAuth (use the Lync “Get-CsCertificate -Type OAuthTokenIssuer” cmdlet to find the serial number of the OAuth certificate).
    Right-click | “All Tasks” | “Manage Private Keys”
    Add Permissions for “Network Service” account (the defaults Full control and Read).
    Please also check registry key on client computer.
    If the HKCU\Software\Microsoft\ Office\15.0\Lync \[User SMTP Address]\Autodiscovery registry key does not exist on the user’s workstation, then it likely means that one of the following failures
    have occurred:
    Lync was unable to locate a valid DNS A record or SRV record for the Autodiscover site
    Certificate assigned to Autodiscover site is not trusted by the Lync workstation
    More details:
    http://www.microsoft.com/en-in/download/confirmation.aspx?id=15668
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • 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

  • How can I manually verify autodiscovery configuration for on premise environment from Lync 2013 desktop client?

    I have very limited access to an environment (basically just user access). I am documenting the Lync 2013 cilent for this environment. I was provisioned a limited SIP enabled account for testing. Autodiscovery from the Lync 2010 client works, but not from
    the 2013 client. I can connect (with some issues) from either 2010 client (autodiscovery) and 2013 client (manually configuring the server). So I want to verify if the Autodiscover is configured correctly to work with the 2013 client or not and if the reason
    it fails for me is due to something wrong with my account or if this will happen with other users?
    I have checked the lyncdiscoverinternal.domain.com and it resolves and is reachable. I can navigate to https :// lyncdiscoverinternal.domain.com/Autodiscover/AutodiscoverService.svc/root/domain and it returns the information I would think it should
    including hrefs to Internal/Autodiscover, Internal/AuthBroker, External/Autodiscover, External/AuthBroker, Internal/Mcx & External/Mcx as well as fqdns for SipClientExternalAccess, SipClientInternalAccess, SipServerExternalAccess & SipServerInternalAccess.
    The AuthBrokers urls return what I believe is the expected RemoteService Service pages. The Mcx urls return what I believe is the expected McxService2 Service pages. The SipClientInternalAccess & SipServerInternalAccess fqdns are both resolvable and
    reachable. The Autodiscover urls return hrefs for Domain and User. Those Domain urls return the same information as the initial root/domain url and the user url (which I believe is the one that is actually opened by lync during the autodiscover process) returns
    what I believe is an expected 401 - Unauthorized: Access is denied due to invalid credentials page.
    If I explicitly configure the Lync 2013 client to use the fqdn listed for SipClientInternalAccess, the client will log me in. However on Automatic configuration, it fails to log me in.
    One other note is that when I watch with Wireshark, I observed that it is getting another internal server fqdn from somewhere. We'll just say that the SipClientInternalAccess fqdn is lyncABC.domain.internal. When looking at Wireshark and the DNS requests,
    I'm also seeing a lync2013ABC.domain.internal that does resolve and is reachable and can also be used as the explicitly listed server in the Lync 2013 client and it will log in. However, that fqdn is not listed in any of the root or domain url replies. So
    I'm not sure where it is coming from or how to check that.
    Is there any additional information anywhere that can tell me exactly what the behavior of the 2013 client is when trying to find the server to authenticate to and how I can reproduce any missing steps manually to determine what it is identifying as the
    login server (if any) since it is obviously not the trying the one listed as SipClientInternalAccess?
    Thanks,
    Richard

    Hi Richard,
    To narrow down the issue, you could refer to the following steps first.
    1. Delete the Lync client 2013 user profile and registry key.
    User profile:
    %userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]
    Registry Key:
    HKCU\Software\Microsoft\Office\15.0\Lync\[email protected]
    Certificate:
    a. Open Windows Certificate Manager. To do this, press Windows + R, type certmgr.msc, and then click OK.
    b. Expand Personal, and then expand Certificates.
    c. Look for a certificate that's issued by Communications Server and delete it.
    2. Upgrade Lync client to the latest update.
    3. Check the DNS records(A records and SRV records) again.
    Best regards,
    Eric

  • Lync 2013 Desktop Recording

    When I recorded my Lync meeting, it indicated that I was not doing any desktop presentations, but I was sharing my desktops as I was talking - doesn't it record my desktop as I'm sharing during the meeting?

    I'd make sure that the PC that is recording the meeting is dialed into the meeting using Lync audio/video instead of dialing in PSTN.  Paul is correct - when you record a meeting, the entire experience is included in the MP4 file (in 2013).  We
    use it all the time and it works well.
    I'd be interested in the details of the scenario in which these results are experienced. 
    -G
    if my post is helpful - please click on the green arrow. (please excuse, in advance, any perceived sarcasm/humor - as I often forget it does not translate through text) :)

  • Cannot share desktop - Lync 2013 server and Windows 8 (64-bit) client

    Currently my new Lync server cannot share a desktop through a Lync 2013 client installed on a Windows 8 workstation. The client is patched up with the latest MS patches (much beyond the patch issues noted about a year ago, the patches in question do not
    even show up as installed).
    I get the same "An error occurred during the screen presentation" message. I do have a NVIDIA video cards on the workstations, but they too are patched up. The same systems have no issues sharing desktop screens in the Lync 2013 client on Windows
    8 systems when they are connected to a Lync 2010 server.
    I have no idea where to go from here. Any suggestions or help is greatly appreciated.

    Did this issue happen to other Lync 2013 client?
    As you mentioned that you can used the same Lync 2013 to sharing desktop screen when it connects Lync Server 2010 while you couldn’t share desktop screen when it connects to Lync Server 2013,
    I think it is related with Lync Server.
    Please check if you can find any errors on Lync Front End Server.
    Check all Lync server services are all started.
    Lisa Zheng
    TechNet Community Support

  • Lync Application and Desktop Sharing - Restrict remote access/Telnet

    I have a customer and they are paranoid about using Lync application/desktop sharing which could potentially enable remote users from getting into their internal IT systems.  They are asking if we could restrict application/desktop sharing specifically
    for appls with remote access capabilities (e.g. Telnet, etc.)? Anyone could share any information relating to this? Thanks!

    We can’t do this with Lync Server natively. Maybe you want to vote idea at
    http://lync.ideascale.com/a/dtd/Limit-AppSharing-for-specific-applications/467874-16285
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found
    there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    Lisa Zheng
    TechNet Community Support

  • Lync 2013 stops responding when making audio calls

    Lync 2013 desktop client in Windows 8.1 connected to Lync Server 2010
    From my office workstation (Windows 7, Lync 2010 client, completely different hardware), from inside the firewall, I don't have any problems (IM, audio, conference, video, desktop sharing all work 100%).  At home, I haven't been able to make PC calls. 
    I can see the status of my contacts in Lync, and contact them through IM, but as soon as I try to make an audio call, Lync stops responding.  I can, on occasion, connect and can receive audio, but I cannot be heard on the other end.
    To place audio calls, I connect to my office workstation through remote desktop - the audio quality is terrible but it works.
    I'm testing various configurations using the "Check Call Quality" function under Tools > Audio Device Settings.  I can hear a couple of beeps, or even a ring tone, once, but then it crashes again.  Waiting 10 to 15 minutes, it still
    does not respond.
    I am using Lync 2013 because 2010 wasn't available through MS Office HUP.  I checked the compatibility list, and I didn't think there would be a conflict between the two versions.
    Would downgrading Lync to 2010 help?
    I am not exactly a Lync expert, so I may have some of the setup wrong.  I'm hoping it's as simple as a server/connection setting that I've missed.  I'm using Automatic Configuration under Advanced Connection Settings.
    Hardware specs:
    DELL XPS 8500
    Windows 8.1 64-bit
    Realtek High-Definition ALC887 Audio
    Creative Labs Sound Blaster Recon3D PCIe Audio Card
    NVidia GeForce GTX 660 Graphics Card
    According to Windows, all drivers are up to date.
    I had a Logitech webcam installed.  I disconnected it and restarted the computer, to make sure it wasn't affecting Lync.

    Hi,
    Did the issue happen only for you or for multiple users?
    Did the issue happen when one endpoint is internal and the other is remote or also happen when two endpoint external the company?
    If it possible, please try to use another computer login on Lync client 2013 at home.
    Please double check if you have configured DNS entry for Lync server Edge A/V service.
    Here is a similar case may help you:
    http://social.technet.microsoft.com/Forums/lync/en-US/522e7f53-d0d4-4b08-9917-45b80a292963/lync-2010-external-voice-calls-do-not-complete-call-failed-to-establish-due-to-a-media?forum=ocsedge
    Please also double check the Edge external A/V port UDP 3478, TCP 50,000-59,999 and UDP 50,000-59,999 and make sure they are opened.
    What’s more, you can troubleshooting Edge server with the help of the link below:
    http://blogs.technet.com/b/nexthop/archive/2011/12/07/useful-tips-for-testing-your-lync-edge-server.aspx
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Lync 2013 internal video stuck at connecting

    Hi,
    I have built a simple Lync 2013 deployment with two FE enterprise servers a F5 load balancer and a single edge server. The problem I have is that video or desktop sharing won't work internally. The status within the client is 'Connecting...' if I perform
    a network monitoring capture, when I start my video and get the 'connecting..' notice, I see packets from my PC to the Lync edge server.
    This is confusing as I expected video to be peer-to-peer.
    Is there something wrong with my topology to explain this behaviour?

    Hi, Thanks for replying! The workload poster is very useful. Spent all of yesterday looking at snooper, network monitor, firewall logs, but couldn't resolve issue. Overnight had the thought of a fresh install of the Lync client on test PC's, this worked!
    yah!
    I had customised the installation of the lync client, I removed the Office 2013 tools, including the lync recording manager, office 2013 language prefrences and office 2013 upload center (we use office 2010). As I didn't think these were necessary for basic
    lync, seems I was wrong.
    Will work on the cutomised install again to include these options, and wil test lync video / desktop sharing.

Maybe you are looking for