tag:blogger.com,1999:blog-3920347219421157797.post2675255904698479294..comments2024-03-17T13:44:24.499-07:00Comments on Clint Boessen's Blog: Federation information could not be received from the external organization.Clint Boessenhttp://www.blogger.com/profile/11156487394562821934noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-3920347219421157797.post-46662795617267395502012-05-16T16:13:36.088-07:002012-05-16T16:13:36.088-07:00Were you able to find a resolution to this issue?Were you able to find a resolution to this issue?JChttps://www.blogger.com/profile/01044195494004113774noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-9214669317542632432012-04-28T05:25:18.220-07:002012-04-28T05:25:18.220-07:00I have same issue. That does it mean, a post above...I have same issue. That does it mean, a post above? We should wait untill rollup 2, or?..Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-37129311866594587902012-04-12T14:20:13.070-07:002012-04-12T14:20:13.070-07:00Update to April 11, 2012 post: The MS engineer th...Update to April 11, 2012 post: The MS engineer thinks he's found the problem with our SP2, Rollup 1 installation and can reproduce it. The problem lies somewhere with IIS and autodiscover. If you browse directly to autodiscover.svc, it fails. But if you go to the autodiscover.xml and authenticate first, and then you go to autodiscover.svc, it redirects to WSSecurity and succeeds. The problem is, when O365 "reaches in," it does not first go to the .xml.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-9663604029636102912012-04-11T13:09:34.401-07:002012-04-11T13:09:34.401-07:00We're seeing it too, and are working with a se...We're seeing it too, and are working with a senior support escalation engineer at Microsoft to attempt to determine the cause and solution. We have split DNS, and the internal DNS record for autodiscover is a CName pointing to an "A" record representing the Hybrid server (though not the NetBIOS name). We tried a host file entry and still no go. The SAN cert's subjects contain "autodiscover" and the name in the "A" record. Still no go. Same error.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-51071547249921189212012-03-06T21:53:26.513-08:002012-03-06T21:53:26.513-08:00I am getting this error too, RU1 did not fix it fo...I am getting this error too, RU1 did not fix it for me, did it work for you?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-90043373664428742852012-03-04T11:58:31.808-08:002012-03-04T11:58:31.808-08:00Install Exchange 2010 SP2 Update Rollup 1. This s...Install Exchange 2010 SP2 Update Rollup 1. This should contain the fix.Clint Boessenhttps://www.blogger.com/profile/11156487394562821934noreply@blogger.comtag:blogger.com,1999:blog-3920347219421157797.post-64320707441432557152012-03-01T07:53:34.905-08:002012-03-01T07:53:34.905-08:00any issues with using a wildcard certificate inste...any issues with using a wildcard certificate instead of a SAN certificate? i'm getting the exact errors shown here, but all dns resolution appears to be functional.Anonymousnoreply@blogger.com