?
Solved

New Exchange 2010 Server will not use correct send connector

Posted on 2012-09-22
11
Medium Priority
?
2,665 Views
Last Modified: 2012-10-04
I just installed a new Exchange 2010 SP2 server and migrated all of the mailboxes and traffic to the new machine.  This was just to split out services and give exchange its own dedicated box.

Everything has went great, except the new exchange server is only seeing the old exchange server as a legitimate send connector.  I added the new server to the send connector and ran it with both for a day no problems.  In the process of removing the old exchange 2010 server, i removed the old one from the send connector and it quits.  I have created a new send connector just for the new server and it has the same problem no outbound flow.

I have verified with the Queue manager that the mail is only queuing up on the old server.  I have done a few of these, even with this organization during an upgrade with no issues.

Any ideas so I get the mail to send via the new server?  I am sure it is something dumb.
0
Comment
Question by:jbmos2333
  • 7
  • 3
11 Comments
 
LVL 19

Expert Comment

by:R--R
ID: 38425183
delete all the send connector and create a send connector and add the source server as current hub transport server .
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38425854
Buddy is there any Firewall in between ..... if so you have to make changes on it to accept messages from the new server and route external and from external to send messages to the new E2k10 server.

SO changes on Firewall or router if you have any :)

If you dont then check Inbound and Outbound mail flow with www.exrca.com

- Rancy
0
 

Author Comment

by:jbmos2333
ID: 38427036
No firewalls in between the two servers.  I haven't deleted the old send connector but I disabled it and added a new send connector and that didn't work.

Hesitant to delete the current send connector completely without getting more info.

Already used:  https://www.testexchangeconnectivity.com/  and everything passes.

No problems receiving mail on the new server.  I've already cut off inbound access to the old server and re-routed DNS/MX records.

Definitely something internal.  Going to do some more digging.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 

Author Comment

by:jbmos2333
ID: 38427059
Creating a new send connector doesn't matter.  As soon as I add the old server to it, it works fine.  New server still nothing.

I thought it would be an issue with internal DNS, but I can't find anything wrong with the current setup.  Internal lookups are referencing the right server.
0
 

Author Comment

by:jbmos2333
ID: 38427087
The mail is queuing up completely on the old server.  Its not queuing up anything on the new server at all.

All functionality has been moved to the new server, mailboxes, everything.

Not sure why the old server is being treated as the only queue.
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38427832
Look the new server is a HUB server ?
As always the External email routes from the HUB Send Connector to External if there isnt any Firewall .... for Receiving from External you need to have the MX pointing to the new server and port 25 is open on the server to receive the email.

- Rancy
0
 

Author Comment

by:jbmos2333
ID: 38428597
Yes the new server is a hub server.  

There is not a firewall between the old server and the new server, but there is one external firewall managing all traffic.  And all of the records and firewall rules have been updated to reflect the new server.

In my experiment for sending mail.  When I create a new send connector and only have the new exchange server added, all outgoing still queues up on the old exchange server.  As soon as I add the old server to the new send connector of course it all sends out.  

I am creating the new send connector on the new exchange server and I have verified thru ADSIEDIT that the send connector was created properly and the homeMTA is showing the correct server.  

I have removed all receive connectors from the old exchange server and have removed all databases.  As far as I can tell, it is only functioning as an outbound queue for some reason.
0
 
LVL 52

Expert Comment

by:Manpreet SIngh Khatra
ID: 38431574
Get-Mailboxserver "ServerName" | FL and
Get-MailboxDatabase "DatabaseName" | FL

- Rancy
0
 

Author Comment

by:jbmos2333
ID: 38434647
Getting the mailbox and the database are all correct.  What I am going to do, but over the weekend is remove the HUB Transport and Mailbox roles off the old server.  Thus eliminating the old exchange 2010 server's ability to queue up.  Then re-create the send connector with only the new server as an option.

To describe the environment a little better, this was a single server SBS 2008 environment.  We did a swing migration as we exceeded the SBS limits.  So a new Standard 2008 R2 server was installed that became the single server in the network.  It was the DC, SharePoint and Exchange server.  The old SBS server was properly decommissioned and reloaded as the new Exchange server that we just turned on.  

So now the environment is comprised of two servers.  The first 2008 R2 is DC and SharePoint.  The second "new" server is Exchange 2010 SP2.  Thats it pretty simple environment.  

I think by properly removing the extra roles from the old exchange box, it will force AD to update and use the correct send connector.
0
 

Accepted Solution

by:
jbmos2333 earned 0 total points
ID: 38448064
Removing the HUB Transport role off of the old exchange server corrected the issue.  In my previous tests, i would remove the old exchange server from the send connector and reboot the transport service on both servers.  It would then send out properly for a minute or two before going out just the old server that was not part of the send group again.

But as soon as the Hub Transport role was uninstalled the new server immediately fired up working.
0
 

Author Closing Comment

by:jbmos2333
ID: 38462390
The HUB transport role on the old exchange server was causing the conflict and by removing it allowed the new server to take over as it should have from the start.
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Question has a verified solution.

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

On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
Suggested Courses

840 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