Just for the moment, take the Edge server out of the equation.

Can the internal HT send email directly to the Internet?

If so, I'd blame this on your subscription. How did you set that up?

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com


-----Original Message-----
From: Joseph Heaton [mailto:jhea...@dfg.ca.gov] 
Sent: Wednesday, September 22, 2010 5:44 PM
To: MS-Exchange Admin Issues
Subject: RE: Edge Transport Server - Exchange 2010

Ok, so here's where I stand.  Hopefully, you can help me figure this out, 
because I'm a noob to 2010.

Lab environment:

2 MB servers, in a DAG.
2 HT/CS servers, with WNLB for the CS role.
1 TMG in the DMZ, to handle client access security
1 Edge server in the DMZ, to handle mail flow

Internal e-mail works flawlessly.  At the moment, incoming e-mail from the 
outside world works fine.  Outgoing to the internet is not working.  I'm 
getting a "#550 5.7.1 Unable to relay ##".  So the message is going from my 
internal HT server to the edge server, then it's getting kicked back with that 
error.

Looking at my Send connector (EdgeSync - Default-First-Site-Name to Internet) I 
see the following settings:

Address Space Tab:  smtp  *  1   (Type - Address - Cost)

Network Tab:  Route mail through the following smart hosts:  IP of the Edge 
Server
                       Smart host authentication - None

Source Server:  Name of edge server


My initial thought was the Smart host authentication, but changing that to 
Exchange Server authentication didn't change the error message I'm getting.

Any tips/advice/push in the right direction would be immensely appreciated.

>>> "Michael B. Smith" <mich...@smithcons.com> 9/22/2010 1:13 PM >>>
Exchange, except when clustering, prefers a single path/route. That being said, 
as long as you only have one default gateway, it's not a big deal regardless.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com 


-----Original Message-----
From: Joseph Heaton [mailto:jhea...@dfg.ca.gov] 
Sent: Wednesday, September 22, 2010 1:41 PM
To: MS-Exchange Admin Issues
Subject: Edge Transport Server - Exchange 2010

We're working on setting up an Edge box in our lab environment.  We have a DMZ 
setup, we have the Edge box installed in this zone.  Currently, it has one NIC, 
with a public IP on it.  My question:

Is the box supposed to actually sit completely in the DMZ, or is it supposed to 
have a second NIC, with an internal IP, therefore "straddling" the 
firewall/DMZ?  I have not been able to find any info on this issue.

Any pointers to further/better info would be appreciated also.  I've already 
looked at TechNet, and there doesn't seem to be any reference to actual network 
configuration.



---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/ 
or send an email to listmana...@lyris.sunbeltsoftware.com 
with the body: unsubscribe exchangelist


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/ 
or send an email to listmana...@lyris.sunbeltsoftware.com 
with the body: unsubscribe exchangelist





---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist


---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe exchangelist

Reply via email to