Hi greg, thanks for the input. I am not able to browse to http://ServerFQDN.domain.corp:8080/Autodiscover/AutodiscoverService.svc/root
.. i get the same error. The interesting thing is that internally the mobility is also not working now after i created a new topology.. Also, i went to the FE server's IIS and i dont see the "autodiscover" site in it. could
that be the issue?
here's the error for :http://ServerFQDN.domain.corp:8080/Autodiscover/AutodiscoverService.svc/root
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it
is spelled correctly.
Requested URL: /Autodiscover/AutodiscoverService.svc/root
---------------------------------------------------------------------------------------------------
Update! I re-published the topology and then ran the setup or remove components wizard and then the MCX and Autodiscover site showed up on the FE IIS.. then tried going to https://lyncdiscover.domain.org i
get a file download with the following message in it:
{"Root":{"Links":[{"href":"https:\/\/fqdn.domain.local\/Autodiscover\/AutodiscoverService.svc\/root?sipuri=","token":"Redirect"}]}}
After that i tried connecting internally and the mobile .. got prompted to install the cert and then the client just kept cycling trying to connect to the server a few times and then it said that the server was not found..
I went ahead and re-did the server webfarm on the reverse proxy because it was resolving my lyncdiscover site but not the webservice / webticket site .. instead of creating one webfarm for each site i created just one for all of them called
"lync" with all the same setting as shown in the article but with the following in the pattern section:
(*) instead of just *
under conditions pattern i entered:
(webservice.domain.org|lyncdiscover.domain.org|lync.domain.org/meet|lync.domain.org/dialin)
this pattern works for me because i published the dialin and meet as that, i assume that if had done the meet.domain.org i wouldve had to do the pattern differently.
Aside from that, i also noticed that my IISARR server was not resolving the sites to the DMZ ip's so i added them to the host file. ea:
192.168.1.10 lyncdiscover.domain.org and 192.168.1.20 webservice.domain.org
did a "iisreset" and then tested the webservice website and came back ok with the xml language. Tried logging in with a mobile device and ding ding ding!! im in business!!!
Thanks all of you for the help and your time. greg and andrew specially.
As for the connectivity test issue, my firewall was translating 443 to 4443 to the edge server.. obviously the edge server uses 4443 to replicate to the FE using the internal cert.. I removed the port translation and the connectivity test came back successful
with the right public cert.
-
Marked as answer by
Red Fury
Tuesday, August 19, 2014 10:32 PM
-
Edited by
Red Fury
Wednesday, August 20, 2014 8:01 PM
-
Unmarked as answer by
Red Fury
Friday, August 22, 2014 9:00 PM