• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1405
  • Last Modified:

Lync 2013 Deployment - External Connection Error's

Hey Experts,

We are currently upgrading our MS Lync 2010 environment to MS Lync 2013 and are having some challenges with it.

The setup is:
AD Domain: domain.local
Web/Email: domain.net

Old 2010 Server (com01.domain.local) - Server 2008R2

CA Server (dc01.domain.local) - Server 2008R2

New 2013 Front End Pool (lync01.domain.local) - Server 2012R2
New 2013 Edge Server (lync02.domain.local) - Server 2012R2

Internal Certs set (lync01.domain.local / lync02.domain.local)
External UCC SSL Cert (access.domain.net, av.domain.net, webconf.domain.net)

DNS/CNAME/SRV Records Applied / All Correct Ports Open - everything is talking to everything (tested extensively).

So everything works but when I run the MS Connectivity Tester on port 5061 I get this error on the Front End Pool Server:

"The certificate received from the remote server does not contain the expected name. It is therefore not possible to determine whether we are connecting to the correct server. The server name we were expecting is lync02.domain.local. The SSL connection request has failed. The attached data contains the server certificate."

I don't get the same error when running it on Port 443?

It seems like the Front End Pool doesn't recognize the Edge Server or the CNAME/Alias from access.domain.net to lync02.domain.local - these are all set and working?

Any help would be great, thank you! Alex.
  • 3
  • 2
1 Solution
Jakob DigranesSenior ConsultantCommented:
could you please post the EDGE server part from topology builder?
alexballAuthor Commented:
So the Edge Server part is;

Internal server FQDN: lync02.domain.local
Internal IPv4 address:
Federation (port 5061): Enabled
XMPP federation (port 5269): Disabled
Internal Configuration Replication Port (HTTPS): 4443

Net hop selection
Next hop pool: lync01.domain.local (Business)

External settings

Access Edge service
FQDN: access.domain.net
IPv4 address:
Port: 443
Protocol: TLS

Web Conferencing Edge service
FQDN: webconf.domain.net
IPv4 address:
Port: 443
Protocol: TLS

A/V Edge service
FQDN: av.domain.net
NAT: Disabled
IPv4 address:
Port: 443
Protocol: TCP
Jakob DigranesSenior ConsultantCommented:
it the Internal interface for Edge on the same Subnet as the Edge interfaces? network
alexballAuthor Commented:
Hi Jakob_di,

Sorry for the delay, yes it is on the same subnet. Is that a problem?

Thanks, Alex.
Jakob DigranesSenior ConsultantCommented:
yes - it needs to network cards, in different zones)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now