Autodiscover URL returning error
-
Thursday, December 22, 2011 4:59 PM
I have the AutoDiscover rule created in TMG and and it tests fine within the TMG console.
However, when I hit the external URL lyncdiscover.domain.com I get this back:
Unable to download / from lyncdiscover.domain.com
Unable to open the Internet site. The requested site is either unavailable or cannot be found.
The rule is being hit if I filter the logging. There just seems to be some problem with it downloading the autodiscovery info.
Anyone else run into this?
- Edited by JayScovill Thursday, December 22, 2011 4:59 PM
All Replies
-
Thursday, December 22, 2011 8:13 PM
Make sure in your TMG rule that under the "Authentication Delegation" you have the following set:
No delegation, but client may authenticate directly.
This seems to be missing on some of the setup blogs found around the web. Also, this does not affect simple URLs.
Adam Curry -
Thursday, December 22, 2011 9:08 PM
Yep, that options checked.
I notice that when I try to go to the autodiscover link internally I get a 500 server error so not sure if there is something else going on there as well. Same result if I put in the full Autodiscover path to my Lync Web Services URL that is supposed to get returned by the lyndiscover.domain.com URL.
Either way I'm not getting prompted to download the autodiscover data.
What should be the contents of the Autodiscover and Mcx virtual directories? I'm starting to think maybe something is missing from there.- Edited by JayScovill Thursday, December 22, 2011 9:11 PM
- Edited by JayScovill Thursday, December 22, 2011 9:17 PM
-
Thursday, December 22, 2011 9:56 PM
The contents of the Autodiscover diretory for External should be:
Bin (folder)
-------> Microsoft.Rtc.Internal.Autodiscover.dll
Autodiscover.svc
Web.Config
Internally and Externally you should be able to go to https://lync.<domain>.com/Autodiscover/AutodiscoverService.svc/root and it should ask you for a fie download.
Also this link may be worth looking at as well: http://social.technet.microsoft.com/Forums/en-ZA/ocsmobility/thread/06eda9ed-53bc-4ec7-9d44-681725272fac
Adam Curry- Edited by Adam Curry Thursday, December 22, 2011 9:57 PM New Info
-
Friday, December 23, 2011 3:34 PM
I stumbled across that thread and my web.conf files appear to be ok.
I'm just wondering if there isn't something else not configured correctly. Here's what a get-csservice -webserver spits out:
Identity : WebServer:lync.domain.local
FileStore :
UserServer : UserServer:lync.domain.local
PrimaryHttpPort : 80
PrimaryHttpsPort : 443
ExternalHttpPort : 8080
ExternalHttpsPort : 4443
PublishedPrimaryHttpPort : 80
PublishedPrimaryHttpsPort : 443
PublishedExternalHttpPort : 80
PublishedExternalHttpsPort : 443
ReachPrimaryPsomServerPort : 8060
ReachExternalPsomServerPort : 8061
AppSharingPortStart : 49152
AppSharingPortCount : 16383
McxSipPrimaryListeningPort : 5086
McxSipExternalListeningPort : 5087
LIServiceInternalUri : https://lync.domain.local/locationinformation/liservice.svc
ABHandlerInternalUri : https://lync.domain.local/abs/handler
ABHandlerExternalUri : https://lyncwebservices.domain.com/abs/handler
DLExpansionInternalUri : https://lync.domain.local/groupexpansion/service.svc
DLExpansionExternalUri : https://lyncwebservices.domain.com/groupexpansion/service.svc
CAHandlerInternalUri : https://lync.domain.local/CertProv/CertProvisioningService.svc
CAHandlerInternalAnonUri : http://lync.domain.local/CertProv/CertProvisioningService.svc
CollabContentInternalUri : https://lync.domain.local/CollabContent
CollabContentExternalUri : https://lyncwebservices.domain.com/CollabContent
CAHandlerExternalUri : https://lyncwebservices.domain.com/CertPr ov/CertProvisioningService.svc
DeviceUpdateDownloadInternalUri : https://lync.domain.local/RequestHandler/ucdevice .upx
DeviceUpdateDownloadExternalUri : https://lyncwebservices.domain.com/RequestHandlerExt/ucdevice.upx
DeviceUpdateStoreInternalUri : http://lync.domain.local/RequestHandler/Files
DeviceUpdateStoreExternalUri : https://lyncwebservices.domain.com/RequestHandlerExt/Files
RgsAgentServiceInternalUri : https://lync.domain.local/RgsClients/AgentService.svc
RgsAgentServiceExternalUri : https://lyncwebservices.domain.com/RgsClients/AgentService.svc
MeetExternalUri : https://lyncwebservices.domain.com/Meet
DialinExternalUri : https://lyncwebservices.domain.com/Dialin
CscpInternalUri : https://lync.domain.local/Cscp
ReachExternalUri : https://lyncwebservices.domain.com/Reach
ReachInternalUri : https://lync.domain.local/Reach
WebTicketExternalUri : https://lyncwebservices.domain.com/WebTicket/WebTicketService.svc
WebTicketInternalUri : https://lync.domain.local/WebTicket/WebTicketService.svc
McxServiceExternalUri : https://lyncwebservices.domain.com/Mcx/McxService.svc
McxServiceInternalUri : https://lync.domain.local/Mcx/McxService.svc
AutodiscoverServiceExternalUri : https://lyncwebservices.domain.com/Autodiscover/AutodiscoverService.svc/root
AutodiscoverServiceInternalUri : https://lync.domain.local/Autodiscover/AutodiscoverService.svc/root
ExternalFqdn : lyncwebservices.domain.com
InternalFqdn :
DependentServiceList : {Registrar:lync.domain.local, ConferencingServer:lync.domain.local}
ServiceId : 1-WebServices-1
SiteId : Site:Company - Site
PoolFqdn : lync.domain.local
Version : 5
Role : WebServerSomething else: I should be able to test the connection to the AutoDiscover service from my TMG proxy by putting discovery URL in a web browswer, yes? E.g. https://lyncwebservice.domain.com:4443/Autdiscover Because that is just timing out.
Sorry for the formatting (or lack thereof). I can't get the PowerShell output to go into the post without losing most of the formatting.
- Edited by JayScovill Friday, December 23, 2011 3:35 PM
- Edited by JayScovill Friday, December 23, 2011 4:10 PM
-
Friday, December 23, 2011 6:40 PM
Here is my config that works. I have split brain DNS, FE, Edge, and TMG with a third party firewall and TMG as the backend firewall. I use an external web service name different than the internal pool.
Identity : WebServer:<pool>.<External-Domain.com>
FileStore : FileStore:<FESERVER>.<AD-DOMAIN.net>
UserServer : UserServer:<pool>.<External-Domain.com>
PrimaryHttpPort : 80
PrimaryHttpsPort : 443
ExternalHttpPort : 8080
ExternalHttpsPort : 4443
PublishedPrimaryHttpPort : 80
PublishedPrimaryHttpsPort : 443
PublishedExternalHttpPort : 80
PublishedExternalHttpsPort : 443
ReachPrimaryPsomServerPort : 8060
ReachExternalPsomServerPort : 8061
AppSharingPortStart : 49152
AppSharingPortCount : 16383
McxSipPrimaryListeningPort : 5086
McxSipExternalListeningPort : 5087
LIServiceInternalUri : https://<pool>.<External-Domain.com>/locationinformation/liservice.svc
ABHandlerInternalUri : https://<pool>.<External-Domain.com>/abs/handler
ABHandlerExternalUri : https://lyncweb.<External-Domain.com>/abs/handler
DLExpansionInternalUri : https://<pool>.<External-Domain.com>/groupexpansion/service.svc
DLExpansionExternalUri : https://lyncweb.<External-Domain.com>/groupexpansion/service.svc
CAHandlerInternalUri : https://<pool>.<External-Domain.com>/CertProv/CertProvisioningService.svc
CAHandlerInternalAnonUri : http://<pool>.<External-Domain.com>/CertProv/CertProvisioningService.svc
CollabContentInternalUri : https://<pool>.<External-Domain.com>/CollabContent
CollabContentExternalUri : https://lyncweb.<External-Domain.com>/CollabContent
CAHandlerExternalUri : https://lyncweb.<External-Domain.com>/CertProv/CertProvisioningService.svc
DeviceUpdateDownloadInternalUri : https://<pool>.<External-Domain.com>/RequestHandler/ucdevice.upx
DeviceUpdateDownloadExternalUri : https://lyncweb.<External-Domain.com>/RequestHandlerExt/ucdevice.upx
DeviceUpdateStoreInternalUri : http://<pool>.<External-Domain.com>/RequestHandler/Files
DeviceUpdateStoreExternalUri : https://lyncweb.<External-Domain.com>/RequestHandlerExt/Files
RgsAgentServiceInternalUri : https://<pool>.<External-Domain.com>/RgsClients/AgentService.svc
RgsAgentServiceExternalUri : https://lyncweb.<External-Domain.com>/RgsClients/AgentService.svc
MeetExternalUri : https://lyncweb.<External-Domain.com>/Meet
DialinExternalUri : https://lyncweb.<External-Domain.com>/Dialin
CscpInternalUri : https://<pool>.<External-Domain.com>/Cscp
ReachExternalUri : https://lyncweb.<External-Domain.com>/Reach
ReachInternalUri : https://<pool>.<External-Domain.com>/Reach
WebTicketExternalUri : https://lyncweb.<External-Domain.com>/WebTicket/WebTicketService.svc
WebTicketInternalUri : https://<pool>.<External-Domain.com>/WebTicket/WebTicketService.svc
McxServiceExternalUri : https://lyncweb.<External-Domain.com>/Mcx/McxService.svc
McxServiceInternalUri : https://<pool>.<External-Domain.com>/Mcx/McxService.svc
AutodiscoverServiceExternalUri : https://lyncweb.<External-Domain.com>/Autodiscover/AutodiscoverService.svc/root
AutodiscoverServiceInternalUri : https://<pool>.<External-Domain.com>/Autodiscover/AutodiscoverService.svc/root
ExternalFqdn : lyncweb.<External-Domain.com>
InternalFqdn :
DependentServiceList : {Registrar:<pool>.<External-Domain.com>, ConferencingServer:<pool>.<External-Domain.com>}
ServiceId : 1-WebServices-1
SiteId : Site:ABC
PoolFqdn : <pool>.<External-Domain.com>
Version : 5
Role : WebServer- Edited by mniccum Friday, December 23, 2011 6:40 PM
-
Monday, December 26, 2011 8:39 AMModerator
Hi,JayScovill,
It seems you didn't get the file store when you run Get-CsService,did you install Lync Mobility and AutoDiscover service on each Front End server or Diretor? This new services identifies the location of the user and enables mobile devices to locate resources, such as the internal and external URLs for Lync Server Web Services and the URL for the new Mobility Service, regardless of network location.When you install the Autodiscover Service, a new virtual directory (Autodiscover) is created under both the internal website and the external website on both Front End Servers and Directors.So please make sure you have set the ports and install MCX service and AutoDiscover service successfully.
Also please check the certification are set correctly.Here are some good article (A & B) for your reference,you can compare it with your installation steps.
Regards,
Sharon Shen
TechNet Community Support
******************************************************************************************************************************************************* Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community memb
- Edited by Sharon.ShenMicrosoft Contingent Staff, Moderator Tuesday, December 27, 2011 8:37 AM
-
Tuesday, January 03, 2012 8:38 PM
I've followed all the steps from the various articles (I've probably read every one of them) but I still can't even get to the point of being able to download autodiscover data. I think at this point I'm going to drop it as I'm not getting anywhere after a week or so of trying.
Thanks for the help!
-
Thursday, February 02, 2012 5:06 PM
I have the exact same problem.
Any luck yet?
-
Thursday, February 16, 2012 7:35 PM
Still no joy. The autodiscovery data seems to be downloading properly and redirecting to my web services URL but the client is still timing out.
Again, putting the web services URL in the client doesn't work either.
I just confirmed that everything is working on Android clients so it's definitely an iOS quirk.
If I try to browse directly to the web services autodiscovery URL I get a 500 Internal error but that seems to be normal going by the fact the Android clients are fine.
I read one post suggesting making sure the web services and autodiscovery URLs work for HTTP even if you are redirecting to HTTPS or that can cause problems with the iOS client. I haven't tried that yet.
-
Friday, February 17, 2012 9:02 PM
Are you testing from a pc browser? If so, I found it did not work until I used IE9.
Also, I've resolved many similar problems by removing all configurations that introduced load balancing. It is not a long term solution, but helped in resolving issues.
-
Monday, March 05, 2012 10:08 PM
[quote] If so, I found it did not work until I used IE9[/quote]
Thanks for the tip! I was getting the same message as the OP when trying to visit the autodiscover URL in IE8. Tried it in IE9 and was able to dl...
ianc
.png)
