...its all about the certs and the SANs (in the certs) being used. Clients will only attempt to communicate with the FQDN associated with the CM service (e.g. MP/DP/SUP/CRL-DP/etc).
Have you confirmed that the IBCM client is attempting to communicate with the correct FQDN for the service? TMG needs to be configured to allow SSL-bridging or tunneling so that the IBCM clients can communicate. I've only ever configured "tunneling" ... IBCM can be intimidating...but it's really a teddy bear :) Troy L. Martin | Principal Consultant 1E | Empowering Efficient IT US Mobile: +1 678-898-6147 UK Mobile : +44 208 326 9141 [email protected]<mailto:[email protected]> | www.1e.com<http://www.1e.com/> Facebook<http://www.facebook.com/1eglobal> | Twitter<https://twitter.com/1e_global/> | YouTube<http://www.youtube.com/1enews> | Blogs<http://blogs.1e.com/> | RSS<http://blogs.1e.com/index.php/feed/> Please consider the environment before printing this e-mail From: [email protected] [mailto:[email protected]] On Behalf Of Lindenfeld, Ivan Sent: Monday, May 13, 2013 8:21 PM To: [email protected] Subject: [mssms] IBCM with F5 and TMG Anyone have time to talk to me about the above scenario? The biggest piece I still don't understand is how the F5 or TMG server knows to send traffic to the MP when relevant, the SUP when relevant, etc? These are separate servers in my environment. I had hoped ICBM would become less intimidating as I delved deeper but it has not. Thanks. Ivan Lindenfeld ________________________________ DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary user of this email address. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind 1E to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
