Solved

How to forward emails from Exchange1 to another Exchange2 without creating mailboxes in Exchnage1 ?

Posted on 2016-08-18
9
41 Views
Last Modified: 2016-08-22
We have a newly acquired company with one Exchange 2010 called Exchange2 and the domain say domain2.com. We want their emails coming to our HQ Exchange server firstly and then got forwarded to Exchange2 without creating their user mailbox in HQ Exchange server. Is it possible? How?
0
Comment
Question by:Castlewood
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
9 Comments
 
LVL 26

Expert Comment

by:-MAS
ID: 41761282
This expert suggested creating a Gigs project.
Hi Please do as below.

On exchange1 -> EMC -> org config -> Hub transport-> Create a send connector and make it use the IP of Exchange2 as smart host relay.
https://technet.microsoft.com/en-us/library/jj839710(v=exchg.141).aspx

On exchange2 -> EMC -> server config -> hub tranposrt -> create a new receive connector make it accept connections from the IP of Exchange1 and allow relaying on it.

Create Receive connector https://technet.microsoft.com/en-us/library/bb125159(v=exchg.141).aspx

Use this to allow relay.
https://www.experts-exchange.com/articles/2666/Allow-relaying-on-Exchange-2007-Exchange-2010-in-4-easy-steps.html

Thanks
MAS
0
 

Author Comment

by:Castlewood
ID: 41761347
I need to put the newly aqcuired company's domain name (domain2.com) into the Accepted Domain on HQ Exchange, correct?
0
 
LVL 26

Accepted Solution

by:
-MAS earned 500 total points
ID: 41761413
I apologize for that missed part.

On exchange1 -> EMC -> org config -> Hub transport-> Send connectors --> Create a send connector and make it use the IP of Exchange2 as smart host relay.
https://technet.microsoft.com/en-us/library/jj839710(v=exchg.141).aspx

On exchange1 -> EMC -> org config -> Hub transport-> Accepted domains-->Create a domain as internal relay.
New-AcceptedDomain -Name "Domain2" -DomainName domain2.com -DomainType InternalRelay

Open in new window



On exchange2 -> EMC -> server config -> hub tranposrt -> create a new receive connector make it accept connections from the IP of Exchange1 and allow relaying on it.

Create Receive connector https://technet.microsoft.com/en-us/library/bb125159(v=exchg.141).aspx

Run this command to allow relaying on the connector created above
Get-ReceiveConnector <NEWCONNECTORNAME> | Add-ADPermission -User "NT AUTHORITY\ANONYMOUS LOGON" -ExtendedRights "ms-Exch-SMTP-Accept-Any-Recipient"

Open in new window

Use this to allow relay.
https://www.experts-exchange.com/articles/2666/Allow-relaying-on-Exchange-2007-Exchange-2010-in-4-easy-steps.html

Thanks
MAS
0
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 

Author Comment

by:Castlewood
ID: 41761443
A side question....
In HQ Exchange I've had an existing Send Connector (#1) which is with '*' in Address Space where the '*' I believe means ALL. You now want me to add one more Send Connector (#2) with the Address Space = *.domain2.com. It seems the two address spaces have an overlapping area. So my concern is, would an email intended to domain2.com be handled by the #1 Send Connector instead of the #2 ? In another word, how does an Exchange server determine which Send Connector to go to if the Address Spaces overlap?
0
 
LVL 26

Expert Comment

by:-MAS
ID: 41761466
You will have 2 send connectors in your HQ exchange server.
1 with address space "*" and with cost 2
2 with address space "*.domain2.com" and with cost 1

Thanks
MAS
0
 

Author Comment

by:Castlewood
ID: 41761472
I got your idea. The different cost makes it work, just as the "metric" plays in IP routing -- the lower value the higher priority. Currently both connectors are with cost = 1. I'm gonna change it.  
Thanks for help.
0
 

Author Comment

by:Castlewood
ID: 41761636
Hi MAS,

Want to verify the necessity of creating a Receive Connector on Exchange2 since
1. Exchange2 is the final destination with Mail boxes so don't need relay. Conversely besides the Send Connector, shall we need to create a new Receive Connector on HQ Exchange to receive and relay domain2.com emails to Exchange1 ?
2. the existing Receive Connector already covers ALL ip addresses (received from a filtering smart host)

What you think?
0
 
LVL 26

Expert Comment

by:-MAS
ID: 41761646
1. Exchange2 is the final destination with Mail boxes so don't need relay. Conversely besides the Send Connector, shall we need to create a new Receive Connector on HQ Exchange to receive and relay domain2.com emails to Exchange1 ?

No need. You can send email directly out from Exchange2 if you have internet on Exchange2.
If you dont have internet you can do the same process vice-versa to send email out through HQ server.

2. the existing Receive Connector already covers ALL ip addresses (received from a filtering smart host).
If both the exchange servers are from different forest you have to create a receive connector to allow relay.

Thanks
MAS
0
 

Author Comment

by:Castlewood
ID: 41761663
Sorry I got a typo. The previous question should be:

Shall we need to create a new Receive Connector on HQ Exchange to receive (from a filtering smart host) and then relay the domain2.com emails to Exchange2 via the new Send Connector?

The reason I'm confused is, look, it is the HQ Exchange who relays the inbound mails to Exchange2. Doesn't it need a separate Receive Connector with relay on HQ Exchange ?
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…

691 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question