• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 741
  • Last Modified:

E2K3 unable to send email to E2K7 server during migration

We are at a point in an E2K3 to E2K7 migration where we are attempting verify email flow
between the two servers. I can send email out from the E2K7 server to anyone internally
or on the Internet, however I can not send an email from someone on the E2K3 server
to someone on the E2K7 server. Looking at the queue on the E2K3 server, they are held
up on the E2K3-E2K7 routing connector queue.

The Authentication tab on the Receive Connector on the Hub Transport are set for Basic,
Exchange Server authentication, and Integrated authentication, with the permission groups
set for Anonymous users, Exchange users, Exchange servers and Legacy Exchange Servers.

Am wondering what I am missing here in getting the two server to communicate fully?


0
j2luce
Asked:
j2luce
  • 3
  • 3
  • 2
1 Solution
 
AmitIT ArchitectCommented:
I assume this is a cross forest migration?
0
 
AmitIT ArchitectCommented:
If cross forest add Ex2k3 as accepted domain in Exchange 2007, Then test it
0
 
Glen KnightCommented:
Most likely cause is an SMTP Virtual Server misconfiguration.
Can you checfk your setup as per my article here: http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_3044-Exchange-Server-Mail-Flow.html
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
j2luceAuthor Commented:
This is not a cross forest migration, everything lives in the same forest/same domain.
0
 
Glen KnightCommented:
Yes exactly, have you checked the content of my article which refers to the configuration of the Default SMTP Virtual Server in Exchange 2003?

This is used to send/receive email between Exchange Servers within the same organisation so if you have made any changes to this it could be causing the problems.
0
 
j2luceAuthor Commented:
Demazter,

Reviewing your post, there is a smart host attached to the Default Virtual SMTP Server, so Irom the post you listed, I am assumming I should build a second virtual SMTP server directly for use with the smart host?
0
 
Glen KnightCommented:
No, you should use either an SMTP Connector to send to the Smarthost, or since you have now introduced an Exchange 2007 server and the Send Connectors are organisational based, create a send connector, configure this to send to the smart host then delete the smarthost entry from the Default SMTP Virtual Server.
0
 
j2luceAuthor Commented:
Thanks I got it. We already had a SMTP connector set up to use under 2003. The problem was an
old entry in the Default SMTP Virtual indicating that there was a smart host. It was there for a reason when we first installed Exchange 2003 (in fact Microsoft Tech Support put it there). But the purpose it served been dead a long time. I did not give it a thought since email worked coming in and going out through our normal channels. Appreciate the help and guidence!
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 3
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now