• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1380
  • Last Modified:

Cannot Publish Exchange 2010 with Forefront TMG

Hello,

I am trying to publish Exhcnage 2010 OWA using Forefront TMG. I have a Godaddy UCC cert in place and believe it is working as expected.

It seems that the rule I created in TMG is not being tested. If I go to Logs & Reports and start a query, I see Denied Connection from Rule: "Default rule". I do not see any logging before that. I assume I should see my rule "Exch-2010" in the real-time log? I have my rule positioned at the top (#1). I am not sure that this is the issue. It's just the only thing I'm noticing.

I believe I have everything else related to Exchange 2010 configured correctly. I can hit OWA from the inside. I am using basic authentication on the Exchange server and basic authentication on the Authentication Delegation tab in TMG.

Please let me know what additional information you need.

Thanks -Mark

0
mkueffner
Asked:
mkueffner
  • 4
1 Solution
 
NagarajbCommented:
Hope all the things are followed , may be cross check/compare with the steps from below link.

http://www.isaserver.org/tutorials/Publishing-Outlook-Web-Access-Microsoft-Forefront-TMG.html
0
 
mkueffnerAuthor Commented:
I stepped through the article and have verified that all steps have been followed with one exception: I imported the SSL certificate from the Exchange server. However, TMG shows the certificate as valid and the CN name matches my external DNS entry.
0
 
mkueffnerAuthor Commented:
I ran BPA Tool. I am pasting the Publishing Failure error that seems to be the issue:

9/24/2010 9:45:11 AM - The Web publishing rule Exch-2010 failed because the Web listener selected for the rule is not valid. Verify that the Web listener specifies a valid IP address on this computer. I have two NICs: 10.1.10.14 and 192.168.1.154.

After seeing that error, I decided to add 10.1.10.14 to the listener even though I only have on IP addressed assigned on the NIC. When I added the IP address, I got a warning "The specified IP address does not belong to this netowrk. Do you still want to add this IP address he list of IP addresses specifed for this listener?"

I'm wondering if the External Network could somehow be tied to the wrong NIC?
0
 
mkueffnerAuthor Commented:
The problem was I had the listener bound to the built in External Network. Binding the listener to the Perimeter network fixed the issue.
Thanks.
0
 
mkueffnerAuthor Commented:
I found that the listner was bound to the wrong network
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now