Solved

How to configure hub transport send / receive connectors on new exchange 2010 server when getting exchange 2007 and exchange 2010 to coexist?

Posted on 2016-09-22
14
25 Views
Last Modified: 2016-10-01
I currently have exchange 2007 on a windows 2003 server and have introduced a windows 2008 r2 server with exchange 2010.

Here is what I have done so far on the windows 2008 r2 (Exchange 2010 ONLY) server:

Installed the roles required by exchange 2010
Installed exchange 2010 application - it found the existing domain and populated EMC with current domain production data (domain, mailboxes and such)
Created new secondary drive for exchange DB file
Moved exchange DB file to new drive
renamed the exchange DB file
configured exchange 2010 OWA – its reachable with localhost
Installed Microsoft Filter Pack

I believe the next step is to configure hub transport send / receive connectors but I am confused on how to configure them. Do I just make them mirror exchange 2007 hub transport send / receive connectors ?

I have read this article on the subject and it really isn't clear on how to approach this for my particular setup....

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


*Please let me know if you need more information to make a suggestion and thanks in advance for your comments!
0
Comment
Question by:IT_Field_Technician
  • 10
  • 4
14 Comments
 
LVL 38

Expert Comment

by:Adam Brown
ID: 41811862
There's no need to create connectors for the two servers to communicate with one another. They will do so with RPC on the back end by default. The inter-server communication system didn't change between 2007 and 2010, and the two are are fully capable of communicating with one another out of the box.

That said, Send connectors are organizational objects, so all you have to do is modify the send connector you already have and change its configuration so the 2010 server is in the list of servers allowed to use it. Once you do that, users with mailboxes on the 2010 server will be able to send mail to the internet without it being relayed through the 2007 server.

Exchange 2010 has a couple of receive connectors on it when you install it. The Default receive connector is the one that will receive mail on port 25 from the Internet. The Client receive connector is meant for when users utilize IMAP/POP3 to connect to Exchange. It functions on port 587 and allows users to send Outgoing mail after authenticating with their username and password. It can also be used by applications and devices that need to send messages, as long as they support SMTP authentication, TLS, and allow you to change the port you connect to the mail server on. You don't have to make any changes to either of these connectors for things to function properly.

If you have applications or devices that either don't support SMTP authentication or allow you to change the mail server port, you can create an anonymous relay receive connector for them to use. I wrote an article a few years ago on how to do this: http://wp.me/pUCB5-b
0
 

Author Comment

by:IT_Field_Technician
ID: 41814820
Hi Adam, So what you are saying is that I do not have to create any default send or receive connectors on the newly introduced 2010 exchange server as explained in this video when trying to get exchange 2007 to coexist with exchange 2010?

https://www.youtube.com/watch?v=ZoijECnTa1o
0
 

Author Comment

by:IT_Field_Technician
ID: 41814832
When you say:

so all you have to do is modify the send connector you already have and change its configuration so the 2010 server is in the list of servers allowed to use it.

Do you mean I have to edit my exchange 2007 server current send connector under source server and add the new exchange 2010 server?

y
0
 

Author Comment

by:IT_Field_Technician
ID: 41814901
OK so I was able to delete the newly added default send connector I created on the new  exchange 2010 server and added the new exchange server as a source server on the existing 2007 exchange server send connector. Now outgoing email is working from a test mailbox that is on the new exchange 2010 server!

Now to figure out incoming email - Should incoming email be working at this point or is there something I need to configure on the existing exchange 2007 default receive connector?
0
 

Author Comment

by:IT_Field_Technician
ID: 41816341
I have migrated a test mailbox over to the new exchange 2010 server-


I am able to send and receive an email from test email account to test email account at same address

I am able to receive en email from an internal domain user email account but cannot send to an internal domain user email account

I am able to send to an external email address and can receive email from an external email address

Any ideas why I cant send to an internal email address
0
 
LVL 38

Expert Comment

by:Adam Brown
ID: 41816487
Is there a firewall (Software or hardware) between the two servers? If so, make sure it is configured to allow all ports between the two Exchange servers (This is a requirement. MS won't support Exchange servers that have port limitations between them).

Do you get an NDR (Bounce message) when sending to the internal domain user from Exchange 2010? If so, could you please post the content of it?
0
 

Author Comment

by:IT_Field_Technician
ID: 41816519
We only have a firewall blocking external ports all internal ports are open accept for port 25.

And no there is no NDR (Bounce message) it will just never show up for the expecting recipient (whose mailbox is on the old exchange 2007 server still).
0
Too many email signature updates to deal with?

Do you feel like you are taking up all of your time constantly visiting users’ desks to make changes to email signatures? Wish you could manage all signatures from one central location, easily design them and deploy them quickly to users? Well, there is an easy way!

 

Author Comment

by:IT_Field_Technician
ID: 41816522
I have ensured both exchange servers ip addresses are excluded in the port 25 blocking rule in our firewall before hand.
0
 
LVL 38

Expert Comment

by:Adam Brown
ID: 41816533
Exchange doesn't use port 25 to communicate with other Exchange servers (usually). It utilizes RPC, which runs over a random port between 40000 and 65000 (Or there abouts). But you should make sure you aren't blocking port 25 between the Exchange servers as well, as it can be used as a backup.

You'll want to check the event log and queues on the 2010 server to see if there is something causing the messages from the server to disappear. Also make sure the Mail Submission and Transport services are running on both servers.
0
 

Author Comment

by:IT_Field_Technician
ID: 41816955
It looks like the emails are delayed - I just got this:


 
Content Area Delivery delayed:RE: rer  
Microsoft Outlook  
 
Sent:  Monday, September 26, 2016 4:30 PM  
To:  user
Attachments:  
 
 
 
Delivery is delayed to these recipients or groups:

Administrator (Administrator@domain.com)

Subject: RE: rer

This message hasn't been delivered yet. Delivery will continue to be attempted.

The server will keep trying to deliver this message for the next 1 days, 19 hours and 53 minutes. You'll be notified if the message can't be delivered by that time.
0
 
LVL 38

Assisted Solution

by:Adam Brown
Adam Brown earned 500 total points
ID: 41816993
Open the mail queues in the Exchange toolbox on the 2010 server. That should help you better identify the cause of delivery failures.
0
 

Assisted Solution

by:IT_Field_Technician
IT_Field_Technician earned 0 total points
ID: 41817127
OK here is what I see in the mail queue under error for all the stuck (delayed) Messages:

451 4.4.0 Primary target IP address responded with: “451 5.7.3 Cannot achieve Exchange Server authentication.” Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.

I am looking at this article to resolve but I am not understanding what its telling me to do:

https://blogs.technet.microsoft.com/tkern/2011/03/30/451-4-4-0-primary-target-ip-address-responded-with-451-5-7-3-cannot-achieve-exchange-server-authentication/

I do have a 3rd custom receive connector for an application on my domain as the article describes but I believe the setting are configure properly according to the article....
0
 

Accepted Solution

by:
IT_Field_Technician earned 0 total points
ID: 41817150
I resolved my issue and mail is now flowing in all directions for all email accounts on both exchange servers - Thanks you so much for helping me figure this out - now only tame the rest of this monster!!!!!

I was able to go into the receive connector for my app and enable exchange server authentication under the authentication tab. I also had to enable exchange servers under permission groups tab.
0
 

Author Closing Comment

by:IT_Field_Technician
ID: 41824644
Thanks!
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Suggested Solutions

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
Learn to move / copy / export exchange contacts to iPhone without using any software. Also see the issues in configuration of exchange with iPhone to migrate contacts.
This tutorial will show how to configure a single USB drive with a separate folder for each day of the week. This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten. The USB drive must be s…
The viewer will learn how to successfully create a multiboot device using the SARDU utility on Windows 7. Start the SARDU utility: Change the image directory to wherever you store your ISOs, this will prevent you from having 2 copies of an ISO wit…

743 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

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now