Hello all,
I am very new to windows server in general but never the less I was tasked with setting up a Lync 2013 Server, which is running on a Windows Server 2008 r2 Server.
Now that is out of the way my question is in two parts, the first is relating to the topology set-up I have at the moment and the second is relating to the Mobility and Proxy side of things. The second problem may very well being caused because of the initial
set-up but I have no idea.
Complete Set-up: (I am aware the computer names are not the best, sorry).
Domain is: tlo-controller.local
- Server Type NameIP
- DNS:tlo-comp 192.168.1.11
- Lync Front End:tlo-comp2 192.168.1.12
- Edge Server:LyncEdge 192.168.1.18Not On the Domain
- Proxy Server: revproxy 192.168.1.19Not On the Domain
First Problem:
Currently the Topology Builder set-up for basic sip usage using a Edge Server can be seen in[Figure 1] below. You will notice that the A/V and Access Edge Services ports are not the default A/V:443 and Access:5061. The initial set-up was set using the default ports for both settings but when testing the set-up using
the Lync Connectivity Analyser we got errors with SSL, specifically saying that the server could not be contacted on port 443.
We then tested to see if the ports were indeed open externally using a port testing website calledYou Get Signal, this shown us that indeed port 5061 was open but 443 was closed. Trying our luck we changed A/V to port 5062 and Access to 443 and published the Topology, ran the Lync Connectivity
test again and it we got all green ticks! we tested external Lync Access on a computer and we were able to log in fine. We the left the set-up in this state simply as a temporary fix, we suspect this set-up may be causing problems with other systems such ass
meet and the Auto discover which is my second problem.
The TCP & TLS DNS Records set-up can be seen in [Figure 2] below. I understand that some of the records will be wrong or not needed but remember I am new to this stuff :)
[Figure 1] - Lync Edge A/V and Access Port Set-up
![]()
[Figure 2] - TCP & TLS DNS Record Configuration
![]()
Second Problem:
The Second problem relates to Mobility and the Reverse Proxy Server Set-up, we are having issues connection to Lync via mobile but we are able to internally resolve lyncdiscover.tlo-controller etc.. the command line test " Test-CsMcxP2PIM"
passes when run, with the following results.
Target Fqdn : lyncwebex.external.com
Target Uri : https://tlo-comp2.tlo-controller.local:443/mcx
Result : Success
Latency : 00:00:00
Error Message :
Diagnosis :
we are also able to navigate to lyncdiscover.external.com externally and receive the XML with the External web address and so on.
The Setup is:
- Internal web service: tlo-comp2.tlo-controller.local
- External web service: lyncwebex.external.com
- Web Service ports are at default settings
Also here is the results from running the mobile auto discover on my domain. (I could only upload two pictures)
Testing connectivity to the Lync Autodiscover Web Service server for a secure connection on port 443 to obtain the
root token.
Connectivity to the Lync Autodiscover Web Service test failed.
Test Steps
Attempting to test Autodiscover Web Service URL
https://lyncdiscover.external.com/Autodiscover/AutodiscoverService.svc/root.
Autodiscover Web Service URL can't be contacted due to failure of the following tests:
Test Steps
Attempting to resolve the host name lyncdiscover.tlo-ops.co.uk in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: External IP here
Testing TCP port 443 on host lyncdiscover.external.com to ensure it's listening and open.
The port was opened successfully.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server
lyncdiscover.external.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=sip.external.com, OU=Domain Control Validated, Issuer: SERIALNUMBER=07969287,
CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.",
L=Scottsdale, S=Arizona, C=US.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name lyncdiscover.external.com was found in the Certificate Subject Alternative Name entry.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 8/23/2013 8:06:09 AM, NotAfter = 8/22/2014 9:51:39 AM
Testing HTTP authentication methods for URL
https://lyncdiscover.external.com/Autodiscover/AutodiscoverService.svc/root/user.
HTTP authentication methods successful.
Additional Details
Web Ticket URL found as expected and confirmed anonymous access isn't allowed.
Testing HTTP content for URL https://lyncdiscover.external.com/Autodiscover/AutodiscoverService.svc/root/domain
has McxService.svc.
HTTP content isn't verified.
Tell me more about this issue and how to resolve it
Additional Details
HTTP 200 status received from server, but no McxService.svc.
Please done hesitate to ask about any details of my set-up I tried to provide the most reinvent info I could, as I said I am new to all this :D. Thanks in advanced people!
Beattie