Solved

Why would the FE Servers On-Prem in Lync 2013 try to reach All the DC's in Domain? How can we limit the connection to one of two DC's?

Posted on 2014-12-23
10
1,692 Views
Last Modified: 2014-12-25
I have been working on finding if there is way to limit the number of DCs to which Lync 2013 would like to connect to. This is an event that is frequently reported. All of the IPs belong to DC but I would like to know why the Lync Server needs to reach DCs on port 5061. Any thoughts?

12/11/2014 09:56:30 AM
LogName=Lync Server
SourceName=LS Protocol Stack
EventCode=14584
EventType=2
Type=Error
ComputerName=
TaskCategory=LS Protocol Stack
OpCode=None
RecordNumber=1122212
Keywords=Classic
Message=Connection attempt to at least one service in a pool failed.


Connection attempts to the following services have failed. Another attempt will be made for each service every 10 minutes.
Service Address: 10.4.8.103:5061; Pool FQDN: *.org; Down Time: 0:00

Cause: The specified service(s) are unavailable.

Resolution:
Check the servers in the pool(s) on which the service(s) are installed.
0
Comment
Question by:K Anthony O365
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
10 Comments
 
LVL 19

Assisted Solution

by:Adam Farage
Adam Farage earned 100 total points
ID: 40515273
Lync should be hitting domain controllers within there local AD site only. I believe there is a way to limit this to a particular domain controller (as you can do with Exchange) but I wouldn't recommend it. This is built in resiliency for the situation where a DC goes down, Lync can utilize another in-site domain controller to authenticate.

In the event that an in-site domain controller is not available it will then go to the closest site (depending on site link values) and utilize that domain controller.
0
 
LVL 58

Assisted Solution

by:Cliff Galiher
Cliff Galiher earned 400 total points
ID: 40515281
Looks like a DNS or maybe a topology issue. 5061 is SIP, and Lync has no reason to contact a DC via SIP. It is also reporting your pool FQDN as *.org, which means Lync will think every record in DNS is a part of the pool. So it isn't trying to contact a DC, it thinks it is trying to contact a pool member.
0
 

Author Comment

by:K Anthony O365
ID: 40515286
Cliff,

The actual Pool ID has been purposely omitted. So I don't think DNS is the issue. What protocol will Lync use to contact a DC? And is there a way to limit it to certain DC's in same site i.e. Exchange?
0
Backup Solution for AWS

Read about how CloudBerry Backup fully integrates your backups with Amazon S3 and Amazon Glacier to provide military-grade encryption and dramatically cut storage costs on any platform.

 
LVL 58

Accepted Solution

by:
Cliff Galiher earned 400 total points
ID: 40515294
LDAP, not SIP. That 5061 is still a sign of a misconfigurarion.  There is no way that I'm aware of to restrict Lync Server to specific DCs.
0
 

Author Comment

by:K Anthony O365
ID: 40515325
We have TMG in a DMZ and we're also using a Director role in our environment. Does that make a difference?
0
 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 40515326
Nope.
0
 

Author Comment

by:K Anthony O365
ID: 40515356
Thanks!
0
 

Author Comment

by:K Anthony O365
ID: 40515393
I constantly get these from SCOM...related to Lync 2013. Could this be related?

Alert: [LYNC] The number of requests currently in processing by application that have not yet been authenticated or are processed anonymously.
Source: Application Pool [LM_W3SVC_34577_ROOT_GroupExpansion]
Path: LyncServer.Domain.org
Last modified by: System
Last modified time: 12/22/2014 1:21:58 PM Alert description: Perf Object Name:
Perf Counter Name: WEB - Unauthenticated Requests In Processing Perf Counter Value: 4294967296 Error Threshold: 2499 Warning Threshold: 2000 Delta Window Size: 3 Dynamic Instance. Name: Application Pool DependencyId: ApplicationPool Symbol Prefix: WEBAUTH Category: LS:WEB - Throttling and Authentication Discover Interval: 14400 Excluded Instances:
Please see the 'Product Knowledge' and the 'Alert Context' tab on Alert Properties view for more information.
0
 
LVL 58

Expert Comment

by:Cliff Galiher
ID: 40515401
Possibly. Tough to tell for sure.
0
 

Author Closing Comment

by:K Anthony O365
ID: 40517766
Comments were very helpful! Still looking for a solution, but comments pointed me in right direction.
0

Featured Post

Salesforce Has Never Been Easier

Improve and reinforce salesforce training & adoption using WalkMe's digital adoption platform. Start saving on costly employee training by creating fast intuitive Walk-Thrus for Salesforce. Claim your Free Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Follow this checklist to learn more about the 15 things you should never include in an email signature from personal quotes, animated gifs and out-of-date marketing content.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question