Quantcast
Channel: Exchange Server 2013 - Setup, Deployment, Updates, and Migration forum
Viewing all articles
Browse latest Browse all 7129

Issue when Creating a Federation Trust with MFG (Microsoft Federation Gateway)

$
0
0
I am trying to create a Federation Trust with MFG (Microsoft Federation Gateway).  However, I am running into a problem.  I see in the following that link (http://technet.microsoft.com/en-us/library/ff607475(v=exchg.141).aspx) that I have to run this command:

Set-ExchangeServer -Identity "MAIL01" -InternetWebProxy "<Webproxy URL>"

Please note that I have the following in our Exchange 2010 SP3 environment:

Two CAS/HT Servers (CAS Array between the two)
Two mailbox servers (DAG between the two)
One mailbox server (for stand-alone mailbox/archive databases)

We use windows load balancing and the internal/external VIP name is "mail.ourdomain.com"

I have successfully tested that we have properly published Autodiscover and Exchange Web Services via the Exchange Remote Connectivity Analyzer (http://exrca.com)

I have tried setting the InternetWebProxy to:

- http://mail.ourdomain.com:8080 (received the error below)
- http://servername.ourdomain.com (received the error below)
- http://proxy:8080 (received the error below)

Error:

Unable to access the Federation Metadata document from the federation partner. Detailed information: "Unable to connect to the remote server".
    + CategoryInfo          : MetadataError: (:) [New-FederationTrust], FederationMetadataException
    + FullyQualifiedErrorId : 27838E8C,Microsoft.Exchange.Management.SystemConfigurationTasks.NewFederationTrust

I restarted the Transport service on both CAS servers after each change too.

I have also followed the steps to "Use the Shell to create a federation trust" list here: http://technet.microsoft.com/en-us/library/dd335198.aspx

1. What do I put for the "Web Proxy URL"?
2. Do I have to run the Set-ExchangeServer -Identity "MAIL01" -InternetWebProxy "<Webproxy URL>" command on every server?
3. What do I need to do to resolve the "Unable to access the Federation Metadata document from the federation partner. Detailed information: "Unable to connect to the remote server" error?



Viewing all articles
Browse latest Browse all 7129

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>