Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 598
  • Last Modified:

Exchange 2010 transition problem with receive connector

I am performing a Exchange 2003 SP2 transition to Exchange 2010. Exchange 2003's OS is Server 03 with SP2 (32Bit). Exchange 2010's OS is on Server 08 R2. We have three DC's on the network (two Server 08 R2 servers and one Server 03 with SP2).  I have completed all the Active Directory prep for Exchange 2010, and have applied all the necessary hot fixes.
The Exchange 2010 SP1 environment has two servers. One holds the Hub Transport, CAS, Mailbox roles. The other holds the Edge Transport role. The transition seems to be working well.
 I can migrate a mailbox to the new server without any issues. I can see the global catalog and everything appears to be working. The problem I am having is I can send mail fine, but am unable to receive. It was my understanding through my research that I can run both in parallel. Is this correct?
If that is correct than my guess would be that I have improperly setup the receive connector on the edge server? I did configure the EdgeSync Service, and everything appears fine on the Hub Transport server.  Any help would be greatly appreciated.
Thanks!
0
ACSTechSrv
Asked:
ACSTechSrv
  • 2
  • 2
2 Solutions
 
sinister_krisCommented:
Hi ACSTechSrv,

It sure can run parallel.
Have you done a bidirectional connector for your routing group?
Check your permission on default <server> receive connector and verify that anonymous users is checked.

Kris
0
 
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
Can you send mail between exchange 2003 and 2010? Also do you have the IP address of the edge authorized on the hub receive connector? a good way to check this is to telnet 25 from the edge to the HUB. Also on the Edge do you have anonymous checked? and on the binding section do you have all IP's allowed (if receiving direclty from Internet)
0
 
ACSTechSrvAuthor Commented:
Sorry for the delay. It ended up being an old virtual SMTP connector on the 2003 server that caused our problem. Once it was removed, we where able to send again.
0
 
ACSTechSrvAuthor Commented:
Sorry for the delay. It ended up being an old virtual SMTP connector on the 2003 server that caused our problem. Once it was removed, we where able to send again. Thanks for helping.
0
 
sinister_krisCommented:
As long as you got it resolved, that's all that matters.
0

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

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