Exchange server help

[Sir Asvald]

I have 2 Exchange servers for 2 separate domains. The Exchange server on domain 1 is being port forwarded to the ASA. What I'm trying to achieve is I want the emails for domain 2 come from The exchange server in domain 1 into the Exchange server of domain 2. I've set up send connectors and and receive connectors. But I'm unable to receive, I can't only send.

 

Network diagram :

 

[Radium_Angel]

What error messages (if any) are you getting?

Sounds like you either have the firewall, or ports mis-configured

[Sir Asvald]

5 minutes ago, Radium_Angel said:

What error messages (if any) are you getting?

Sounds like you either have the firewall, or ports mis-configured

No errors at all

I've even tested my email with http://testconnectivity.microsoft.com and others, all test say it is working.

 

 

 

 

[Nerdtality]

Could it be a Exchange mail rule?

[Nerdtality]

Also, check your logs

[Nerdtality]

Also, make sure this is checked...

[leadeater]

Have you allowed the Exchange server itself to receive and route emails for the other domain? It would actually be easier to setup a front end mail relay using the Windows Server role and just straight forward emails based on domain to the appropriate Exchange servers.

 

Quote

Relay domains

Typically, most Internet-facing messaging servers are configured to not allow for other domains to be relayed through them. However, there are scenarios where you may want to let partners or subsidiaries relay email through your Exchange servers. In Exchange 2013, you can configure accepted domains as relay domains. Your organization receives the email messages and then relays the messages to another email server.

You can configure a relay domain as an internal relay domain or as an external relay domain. These two relay domain types are described in the following sections.

Internal relay domain

When you configure an internal relay domain, some or all of the recipients in this domain don't have mailboxes in this Exchange organization. Mail from the Internet is relayed for this domain through Transport servers in this Exchange organization. This configuration is used in the scenarios that are described in this section.

An organization may have to share the same SMTP address space between two or more different messaging systems. For example, you may have to share the SMTP address space between Exchange and a third-party messaging system, or between Exchange environments that are configured in different Active Directory forests. In these scenarios, users in each email system have the same domain suffix as part of their email addresses.

To support these scenarios, you need to create an accepted domain that's configured as an internal relay domain. You also need to add a Send connector that's sourced on a Mailbox server and configured to send email to the shared address space. If an accepted domain is configured as authoritative and a recipient isn't found in Active Directory, a non-delivery report (NDR) is returned to the sender. The accepted domain that's configured as an internal relay domain first tries to deliver to a recipient in the Exchange organization. If the recipient isn't found, the message is routed to the Send connector that has the closest address space match.

If an organization contains more than one forest and has configured global address list (GAL) synchronization, the SMTP domain for one forest may be configured as an internal relay domain in a second forest. Messages from the Internet that are addressed to recipients in internal relay domains are relayed to the Mailbox servers in the same organization. The receiving Mailbox servers then route the messages to the Mailbox servers in the recipient forest. You configure the SMTP domain as an internal relay domain to make sure that email that's addressed to that domain is accepted by the Exchange organization. The connector configuration of your organization determines how messages are routed.

To learn more, see Configure an accepted domain for a business unit with mailboxes outside your Exchange organization.

External relay domain

When you configure an external relay domain, messages are relayed to an email server that's outside your Exchange organization and outside the organization's network perimeter.

For more information, see Configure an accepted domain for an independent business unit.

https://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx

 

Edit:

Send/Receive connectors alone isn't enough.

[Sir Asvald]

6 minutes ago, leadeater said:

Have you allowed the Exchange server itself to receive and route emails for the other domain? It would actually be easier to setup a front end mail relay using the Windows Server role and just straight forward emails based on domain to the appropriate Exchange servers.

 

https://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx

 

Edit:

Send/Receive connectors alone isn't enough.

I've done all that. Only problem any email that it to domain 2 will be sent into my primary inbox of domain 1. For example, any email sent to that email with be send to domain1.com email box. Not dmain2.com email box.

 

 

[leadeater]

4 minutes ago, Abdul201588 said:

I've done all that. Only problem any email that it to domain 2 will be sent into my primary inbox of domain 1. For example, any email sent to that email with be send to domain1.com email box. Not dmain2.com email box.

Not if you follow the external relay configuration instructions.

[leadeater]

Oh and for the external relay to work you'll need internal MX records to let Exchange 1 know the internal Exchange 2 address otherwise it won't know where to send the emails.

 

Still I'd put a non Exchange relay in front of both of them and relay that way, much simpler and no dependency on either Exchange environments.

[Sir Asvald]

5 minutes ago, leadeater said:

Oh and for the external relay to work you'll need internal MX records to let Exchange 1 know the internal Exchange 2 address otherwise it won't know where to send the emails.

 

Still I'd put a non Exchange relay in front of both of them and relay that way, much simpler and no dependency on either Exchange environments.

I can send emails which is fine. It's the receiving that is not working.  As for the Non-Exchange Relay, is there any free ones? 

[Sir Asvald]

10 minutes ago, leadeater said:

Not if you follow the external relay configuration instructions.

That KB is for Exchange 2013, would it work for Exchange 2010

[leadeater]

38 minutes ago, Abdul201588 said:

I can send emails which is fine. It's the receiving that is not working.  As for the Non-Exchange Relay, is there any free ones? 

https://technet.microsoft.com/en-us/library/bb124423(v=exchg.141).aspx

 

Do remember that for Exchange 1 anything to Exchange 2 is sending so of you know mail is getting to Exchange 1, which I'm sure is, then it's a sending issue on Exchange 1.

 

On Exchange 1 open up nslookup and do an MX record looking for the Exchange 2 domain, make sure internally you are getting the internal IP address for Exchange 2 and not your external one. If Exchange 1 sends it back out to the public IP the forwarding rules on your routers will just send it right back to Exchange 1 and it'll never get to Exchange 2.

 

You can also start a wireshark trace and send an email destined for Exchange 2 and you should see SMTP traffic outbound from Exchange 1 to Exchange 2, check the destination IP address.

[leadeater]

50 minutes ago, Abdul201588 said:

As for the Non-Exchange Relay, is there any free ones? 

http://blog.powerbiz.net.au/exchange/how-to-set-up-an-internal-smtp-service-for-windows-server-2012-essentials/

 

Or any Linux server and Postfix.

https://www.akadia.com/services/sendmail_relay.html

 

Edit:

Finding a decent guide is a bit annoying for postifx.

[Sir Asvald]

1 hour ago, leadeater said:

On Exchange 1 open up nslookup and do an MX record looking for the Exchange 2 domain, make sure internally you are getting the internal IP address for Exchange 2 and not your external one. If Exchange 1 sends it back out to the public IP the forwarding rules on your routers will just send it right back to Exchange 1 and it'll never get to Exchange 2.

 

This is what i got:

Spoiler

 

 

[leadeater]

29 minutes ago, Abdul201588 said:

This is what i got:

 

Does the primary name server resolve to an internal IP or your public one?

[Sir Asvald]

15 minutes ago, leadeater said:

Does the primary name server resolve to an internal IP or your public one?

Internal IP address.

[Sir Asvald]

@leadeater Still not working.