Forefront TMG SMTP Published Rule - "Request appear....."

Hello Everyone,

I am installing a Forefront TMG server to become the Edge server for a new Exchange 2010 server.

I am almost ready to bring it online but have run into a snag and need some advice if I should just change this setting or figure out what could be causing it.

My question is, on the default Exchange Mail Publish Rule SMTP Server if I leave the rule with the default setting of "Request appear to come from the original client" when inbound messages come in I look at the log and see the message "A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond" and obviously mail is not delivered to the Exchange server. Now if I change the setting to "Requests appear to come from the Forefront TMG Computer" the mail will come in and get routed to the Exchange server. Now I am basically wondering if this is something that I should not do or how can I fix this?

Thank you,
-Mike

LVL 5
BAYCCSAsked:
Who is Participating?
 
khuphucCommented:
how you config your lan setting, you tmg is route o nat,

it's is nat, you have to accept that condition, instead if you use route, the firewall been transparent and the exchange receive the mail with the correct ip source, this condition have some thing to considerate, tmg has to become the gateway of your exchange server.

how you config tmg on your lan, you have a little schema? to understand better the issue
0
 
BAYCCSAuthor Commented:
I don't have a schema per say but I can describe the setup...

Current Exchange 07 server with CAS/HUB/MB roles on one box behind ASA with an internal IP natted to an External on ASA.

New Setup will be Exchange2010 CAS/HUB/MB role with internal IP of 10.25.50.11. TMG server has Exchange edge transport Role installed. The Edge has 2 nics behind ASA. One on ASA DMZ with IP of 10.2.2.2 and one Internal with IP 10.25.50.2

I added a second IP to the External interface of the Edge server with IP 10.2.2.3 and using NAT in the ASA to use External IP from mail.domain.com to 10.2.2.3. I also had to create a NAT rule on the Edge to so request from 10.25.50.11 (new server) use the specific ip of 10.2.2.3 for reverse DNS reasons. After writing this out I am wondering if I should get rid of that rule on the edge?

-Mike
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.