Avatar of geke
geke
 asked on

route to new backend server not found

We have added a new Exchange 2003 SP2 backend server to an existing Exchange organisation. The existing organisation contains only 1 admin and routing group, containing 1 FE and 1 BE server.
I was able to move a mailbox from the old BE server to the new one. I'm able to send mails from the new server to the old one and outside the organisation as well. I'm able to do an smtp telnet session from the old BE to the new one.
BUT I'm not able to receive anything. The connector is still assigned to the old BE server. All mails remain stuck in the queue pointing to the new one. The old BE knows the mailbox resides on the new one, AD replication seems to work perfectly well.
In message tracking, the last stage is "message routed and queued for remote delivery". After a while the message is re-submitted to the smtp gateway and returns in the queue for remote delivery.
Exchange

Avatar of undefined
Last Comment
geke

8/22/2022 - Mon
ASKER CERTIFIED SOLUTION
rakeshmiglani

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.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
geke

ASKER
You're ABSOLUTELY correct. Shame on me, I've overlooked this  (obvious) setting.
Many thanks for the very quick answer.
This is the best money I have ever spent. I cannot not tell you how many times these folks have saved my bacon. I learn so much from the contributors.
rwheeler23