Running into issues with Exchange 2010. Have done some initial trouble shooting but wanted to gain some insight from the community.
Looks like we have 2 internet send connectors:
Both with verify similar settings, except the Internet Outbound one has no source server and looks to be the remains of a migration before my time.
Now when I attempt to add a source server (in trouble shooting) it throws me “Source server “X” isn’t in the connector’s source routing group”.
Now several TechNet articles and Google searches later have lead me to digging around in ADSI edit under the Configuration Naming context. Which seems to include many signs of an old server in the Configuration > Services > Microsoft Exchange > Exchange Admin. Groups > Routing Group > Connections:
First off I would like to know if there is a way to verify that this is the cause of the error. Is there anyone to explicitly track what send connector a message is trying to send out with?
What’s weird is this only seems to be happening when trying to send out to one domain… at least that we have run into? Anyone have any guidance?
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.
Running into issues with Exchange 2010. Have done some initial trouble shooting but wanted to gain some insight from the community.
Looks like we have 2 internet send connectors:
Both with verify similar settings, except the Internet Outbound one has no source server and looks to be the remains of a migration before my time.
Now when I attempt to add a source server (in trouble shooting) it throws me “Source server “X” isn’t in the connector’s source routing group”.
Now several TechNet articles and Google searches later have lead me to digging around in ADSI edit under the Configuration Naming context. Which seems to include many signs of an old server in the Configuration > Services > Microsoft Exchange > Exchange Admin. Groups > Routing Group > Connections:
First off I would like to know if there is a way to verify that this is the cause of the error. Is there anyone to explicitly track what send connector a message is trying to send out with?
What’s weird is this only seems to be happening when trying to send out to one domain… at least that we have run into? Anyone have any guidance?
Share this post
Link to post
Share on other sites