Somebody please help me with this, once and for all.

First off, I just realized that I posted this in the wrong category. We are running Lync Server 2013, not 2010.

I am experiencing every imaginable issue with our Lync deployment possible. Being that I am so brand new to IT, I do not know a definitive answer to this seemingly elusive question.

We are running Lync Server 2013 Standard Edition single server pool with Mediation Server co-located.

The question is, is it a requirement to have the external access service FQDN as not only the CN, but as well the first SAN entry? I am finding conflicting information across the internet.

Our company wants to use only one single public cert, so I have spent much time on trying to make this single public cert work across our Lync deployment. I am wondering whether or not this could be the cause of my woes and frustrations.

Currently our one public certificate CN is our domain name; contoso.com.

I have consolidated the three edge services (web, access, A/V) into one FQDN and single IP and used three different port number assignments. That FQDN is not the CN of our public cert. It is not even the first SAN entry on this cert.

Please help me.

You are much appreciated.

• Edited by Donovan Dickinson 11 hours 1 minutes ago

I believe your _sip._tls.domain.net record is pointing to the wrong port. This port should be your Access port (5061?) and not your A/V port 443 when using a single IP on your edge.

Also Thomas Poett has a great blog about why you should probably stay away from deploying an Edge server with a single IP: http://lyncuc.blogspot.ca/2014/07/lync-edge-server-single-ip-address-how.html