asked on 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!
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!
ExchangeWindows Server 2003Windows Server 2008
Last Comment
sinister_kris
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
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.
ASKER
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.
As long as you got it resolved, that's all that matters.