SOLVED
Home

Lync 2013 - No connectivity with any of Web Conferencing Edge Servers

%3CLINGO-SUB%20id%3D%22lingo-sub-72180%22%20slang%3D%22en-US%22%3ELync%202013%20-%20No%20connectivity%20with%20any%20of%20Web%20Conferencing%20Edge%20Servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72180%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3E%26nbsp%3B%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EAfter%20patching%20Lync%202013%20front%20end%20servers%20with%20March%202017%20CU%2C%20I%20get%20loads%20of%20event%20id%2041025%2C%2041026%20on%20FE%20servers.%20Any%20one%20else%20seen%20this%20and%20got%20some%20tips%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConnection%20to%20the%20Web%20Conferencing%20Edge%20Server%20has%20succeeded%3C%2FP%3E%3CP%3EEdge%20Server%20Machine%20FQDN%3A%20edge.acme.com%2C%20Port%3A8057%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20connectivity%20with%20any%20of%20Web%20Conferencing%20Edge%20Servers.%20External%20Lync%20clients%20cannot%20use%20Web%20Conferencing%20modality.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20tested%3A%3C%2FP%3E%3CUL%3E%3CLI%3ERestarted%20servers%3C%2FLI%3E%3CLI%3EDisabled%20IPv6%20in%20registry%20on%20FE%3C%2FLI%3E%3CLI%3EEDGE%20responds%20to%20telnet%3C%2FLI%3E%3CLI%3ENo%20ports%20blocked%20by%20firewall%3C%2FLI%3E%3CLI%3ECertificates%20verified%20(goDaddy%20public%20cert%20on%20EDGE%20external%2C%20internal%20cert%20on%20EDGE%20internal%20and%20FE).%20Internal%20certs%20from%20same%20CA%2C%20root%20cert%20is%20ok%3C%2FLI%3E%3CLI%3ETime%20out%20values%20in%20the%20Palo%20Alto%20firewall%20has%20not%20been%20verified..%20in%20progress%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-72180%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EInstallation%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72621%22%20slang%3D%22en-US%22%3ERe%3A%20Lync%202013%20-%20No%20connectivity%20with%20any%20of%20Web%20Conferencing%20Edge%20Servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72621%22%20slang%3D%22en-US%22%3E%3CP%3ENice%2C%20thanks%20for%20the%20update.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72605%22%20slang%3D%22en-US%22%3ERe%3A%20Lync%202013%20-%20No%20connectivity%20with%20any%20of%20Web%20Conferencing%20Edge%20Servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72605%22%20slang%3D%22en-US%22%3E%3CP%3EHey%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20a%20new%20Technet%20Blog%26nbsp%3Barticle%20about%20these%20Issue%20(with%20workarounds)%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fuclobby%2F2017%2F05%2F24%2Flyncsfb-server-event-41026-ls-data-mcu-after-may-2017-net-framework-update%2F%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fuclobby%2F2017%2F05%2F24%2Flyncsfb-server-event-41026-ls-data-mcu-after-may-2017-net-framework-update%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72511%22%20slang%3D%22en-US%22%3ERe%3A%20Lync%202013%20-%20No%20connectivity%20with%20any%20of%20Web%20Conferencing%20Edge%20Servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72511%22%20slang%3D%22en-US%22%3EWorked%20right%20off%20the%20bat!%20Great%20work!%20Thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72206%22%20slang%3D%22en-US%22%3ERe%3A%20Lync%202013%20-%20No%20connectivity%20with%20any%20of%20Web%20Conferencing%20Edge%20Servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72206%22%20slang%3D%22en-US%22%3EIt%20helped.%20Thanks%20a%20lot.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72204%22%20slang%3D%22en-US%22%3ERe%3A%20Lync%202013%20-%20No%20connectivity%20with%20any%20of%20Web%20Conferencing%20Edge%20Servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72204%22%20slang%3D%22en-US%22%3E%3CP%3EI%20found%20the%20following%20solution.%3CBR%20%2F%3EThe%20.Net%20Framework%204.6%20and%204.6.1%26nbsp%3Brollup%20was%20also%20installed%20at%20the%20same%20time.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4014510%2Fdescription-of-the-security-and-quality-rollup-for-the-net-framework-4%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4014510%2Fdescription-of-the-security-and-quality-rollup-for-the-net-framework-4%3C%2FA%3E%20%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHad%20to%20add%20the%20following%20registry%20key%20and%20restart%20the%20web%20conferencing%20service.%3C%2FP%3E%3CP%3E%5BHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft.NETFramework%5Cv4.0.30319%5D%3C%2FP%3E%3CP%3E%22RequireCertificateEKUs%22%3Ddword%3A00000000%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72197%22%20slang%3D%22en-US%22%3ERe%3A%20Lync%202013%20-%20No%20connectivity%20with%20any%20of%20Web%20Conferencing%20Edge%20Servers%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72197%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20the%20same%20problem%20for%20Skype%20for%20Business%20Server%202015%20with%20recent%20updates%3C%2FP%3E%3C%2FLINGO-BODY%3E
Ivar Økseter
New Contributor

 

After patching Lync 2013 front end servers with March 2017 CU, I get loads of event id 41025, 41026 on FE servers. Any one else seen this and got some tips?

 

Connection to the Web Conferencing Edge Server has succeeded

Edge Server Machine FQDN: edge.acme.com, Port:8057

 

No connectivity with any of Web Conferencing Edge Servers. External Lync clients cannot use Web Conferencing modality.

I have tested:

  • Restarted servers
  • Disabled IPv6 in registry on FE
  • EDGE responds to telnet
  • No ports blocked by firewall
  • Certificates verified (goDaddy public cert on EDGE external, internal cert on EDGE internal and FE). Internal certs from same CA, root cert is ok
  • Time out values in the Palo Alto firewall has not been verified.. in progress
6 Replies

Have the same problem for Skype for Business Server 2015 with recent updates

I found the following solution.
The .Net Framework 4.6 and 4.6.1 rollup was also installed at the same time.

 

https://support.microsoft.com/en-us/help/4014510/description-of-the-security-and-quality-rollup-for-...   

 

Had to add the following registry key and restart the web conferencing service.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319]

"RequireCertificateEKUs"=dword:00000000

Worked right off the bat! Great work! Thanks!

Nice, thanks for the update.