Message looping between Exchange 2003 & Exchange 2010 after domain type changed to internal relay

Hi
We have a coexistence environment where we are currently migrating from Exchange 2003 to 2010 and have 80% of the users already on the Exchange 2010 platform. This is all within the same AD forest, let's call it FOREST1.AD.
The problem I'm seeking help about is a message routing problem we had this morning where messages bound for the Exchange 2003 users started looping between Exchange 2003 and Exchange 2010. The problem started as a result of changing the accepted domain
type to 'internal relay domain' for the purposes of establishing SMTP namespace sharing with an external Exchange environment (different forest, let's call it FOREST2.AD). The expectation was that after changing the domain type from authoritative to 'internal
relay domain', Exchange 2010 would route messages for unknown recipients to the external environment and that would be the only effect of the change. The message routing to the external environment worked completely OK. However, later we noticed that Exchange
2003 stopped delivering messages to its local users and started routing them to Exchange 2010 which would route the messages back to Exchange 2003 as that's where the recipients existed, only to have Exchange 2003 send them back to Exchange 2010 again.
The Send connector to route the messages, for the shared namespace, to the external environment used the Exchange 2010 server as the source server. It makes sense and is expected that Exchange 2003 would send messages for any unknown recipients to Exchange
2010 for onward delivery via the Send connector. But it is not expected for Exchange 2003 to not deliver messages to its own users using the store driver and instead routing them on to Exchange 2010.
We fixed the problem by reversing the change and not only changed the domain type back to authoritative but also removed the Send connector for the specified shared namespace. However, we do need to understand why this problem happened and how to stop it
from happening.
We did test the shared SMTP namespace configuration using a test domain before applying the change to the domain that is used for production email traffic. Test users on Exchange 2003 with email addresses on the test domain did not experience this looping
problem. This has been tested again after the production domain experienced the problem and there is no looping for the test domain. The only difference I noticed between the configuration for the test domain and the production domain is that while both domains
existed as accepted domains of type 'internal relay domain' in Exchange 2010, there was a difference in configuration in Exchange 2003 where the test domain was not present on the recipient policy at all and the production domain was present there.
This also makes me wonder if Exchange 2003 and Exchange 2010 in the same organization keep a separate configuration to determine which domain they are authoritative for. When you install Exchange 2010, it does add all the domains on the recipient policies
to the accepted domains configuration but any new domains you add in accepted domains in Exchange 2010 are not added to the legacy recipient policy object.
Can someone please help clarify these grey areas and explain why the message looping was created and how to avoid it. I'm happy to provide any further information.
Thanks
Nauman.

Hello,
Why do you want to use the 'internal relay domain' authentication?
Thanks,
Simon Wu
TechNet Community Support

Similar Messages

Mail is Slow between Exchange 2010 and 2013 During Co-Existance Transition

Hello,
I recently migrated from a single Exchange 2003 server to a single Exchange 2010 server
I am now trying to Migrate from Exchange 2010 to Exchange 2013.
I have a test user on Exchange 2013, and Internet Mail works fine and quickly both inbound and outbound.
However, when I try and send between a 2010 user to my 2013 user, delivery takes around 10 minutes.
On the 2013 server I see health check messages, and my 2010 user's message stuck in retry status. The messages eventually clear and the mail is delivered. Any ideas what is causing this delay?
In terms of connectors I have all the defaults. And I created 1 for internal relays from devices. Which works fine.
I have two Exchange 2013 servers configured in a DAG, but I don't have a load balance in place as of yet. So only server 1 is being accessed as the CAS.
Thanks

Hi,
According to your description, the mail flow is slow only between Exchange 2010 and Exchange 2013 server. If I misunderstand your meaning, please feel free to let me know.
If yes, I’d like to confirm if there are multiple NICs on your Exchange servers. And you can refer to the following thread:
http://social.technet.microsoft.com/Forums/exchange/en-US/66f0629f-21fb-444b-b3f1-99ed8a4f52b2/slow-mail-flow?forum=exchangesvrsecuremessaging
We have ONLY 1 network adapter, but if we select "All network adapters" instead of Hyper-V, we will get delays.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Single name space in between Exchange 2010 and 2013

Hi,
In my current environment I have 2 Exchange 2010 servers with DAG no CAS NLB. I installed Exchange 2013 with 2 CAS with WNLB and 2 Mailboxes with DAG. The main requirement is to configure Single name space to access in between Exchange 2010 and Exchange
2013. On Exchange 2010 DAG there is a URL using is owa.domain.com and I also configured in Exchange 2013 all the virtual directories with this name owa.domain.com but having an issue that when I open explorer and use the owa.domain.com URL the user on Exchange
2013 gets their mailbox but user on Exchange 2010 gets error HTTP 403 blank page.
I observed that in Exchange Organization settings CAS settings one server OWA, ECP etc shows their internal external URL but the other server unable to open the OWA, ECP URL and give error message that "An IIS directory entry
couldn't be created. The error message is Access is denied. HResult = -2147024891"
Please guide how to resolve this issue and use the same name URL in Exchange 2010 and Exchange 2013
Thanks,

Hi,
See the below brief:
User will connect to mail.contoso.com as his namespace endpoint. CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox version is 2010 and is located within the local AD site. CAS2013 will proxy the
request to an Exchange 2010 Client Access server which will retrieve the necessary data from the Exchange 2010 Mailbox server
Go through the full blog for better understanding of the redirection.
Client Connectivity with Exchange 2013
Hope you have changed your DNS records to direct connections only to your new Exchange 2013 server. You'll move the host names (for example, mail.contoso.com) users have been using to connect to Outlook Web Access, Autodiscover, and so on, from your
Exchange 2010 server to your Exchange 2013 server. When an Exchange 2010 user tries to open their mailbox, the Exchange 2013 server will proxy their request and communicate with the Exchange 2010 server on their behalf.
Configuring DNS includes the following:
Change the primary host names, such as mail.contoso.com, autodiscover.contoso.com, and owa.contoso.com (if used) to point to the external, publically-accessible, IP address of the Exchange 2013 Client Access server with your public DNS provider.
Change the primary host names, such as mail.contoso.com (or internal.contoso.com if you're using different internal host names) and owa.contoso.com (if used) to point to the internal machine name of the Exchange 2013 Client Access server on your internal
DNS servers.
NOTE- Go through the Exchange Deployemnt Assitant - Configure DNS Records section
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

MS Outlook 2013 Error message "The microsoft exchange administrator had made a change that requires you to quit and restart outlook"

I am currently running 2 HP Servers, SAN Storage. I have Exchange 2013 installed and MS Outlook 2013 randomly appears with the message
"The Microsoft exchange administrator has made a change that requires you to quit and restart outlook" It is happening very frequently and is appearing every few seconds on a lot of users.

Hi WeeMac22,
If you migrated from Exchange 2010 to Exchange 2013, I found a KB for your reference:
Outlook 2013 cannot connect after an Exchange Server 2010 mailbox is moved to Exchange Server 2013
http://support.microsoft.com/kb/2934750/en-us
If not, I suggest using OWA to verify whether this issue remains.
1. If everything works well in OWA, it seems an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I suggest re-create profile to refresh the caches.
I suggest re-install the Outlook if all methods above not working.
2. If this issue remains in OWA, please verify whether all users on the Exchange 2013 have this isse.
If only one user has this issue, I suggest create a test user to check whether the test user has this issue.
If the test user works well, I suggest try to re-create the specific user account.
Please make a full back up before re-creating.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook 2010 SP1 Profile Does Not Update After Moving Mailbox Between Exchange 2010 SP2 Sites

I am working on a large mailbox migration from one AD site to another.
Exchange version at both sites:Exchange 2010 SP2
Two Mailbox Servers: MBX01 in site A / MBX02 in site B
(There is a DAG but keeping this simple)
Two CAS Arrays: CASA.domain.com / CASB.domain.com
The RPCClientAccessServer property is set accordingly. Where MBX01 is set to CASA.domain.com and MBX02 is set to CASB.domain.com
Clients:Outlook 2010 SP1
Scenario: I successfully move a mailbox from Site A to Site B. The Outlook client does not automatically update its server settings to point to the new cas array (CASB.domain.com) and continues to connect to the old CAS server (CASA.domain.com).
I have seen a few articles regarding this pointing to workarounds such as:
- repairing the outlook profile on the client
- delete the existing outlook profile
- run a script to update the prf file (re-cache's email at the client)
I am interested in knowing if anyone else has experienced this, what their solution was for a large migration and if any roll-ups or service packs have possibly fixed this problem.
I would also like to know if you have seen this affect ActiveSync devices. I am getting mixed results in my tests and thought it may be contributed toward different device types, mobile os versions, etc...
I have posted this to the Exchange 2010 forum as well, just wasn't sure where to start.
Thanks.
Mike

Hi,
Seems you got several replies in the thread below that you posted in Exchange forum:
http://social.technet.microsoft.com/Forums/exchange/en-US/68ae67c1-59f5-44bb-aadc-0aea3f72ad2d/outlook-profile-not-updated-to-new-cas-array-after-mailbox-move-between-sites?forum=exchange2010#68ae67c1-59f5-44bb-aadc-0aea3f72ad2d
Please come back to the thread above and check if the replies are helpful.
Since this issue is more related to Exchange, we can provide rarely assistance on this problem. If you need any help on Outlook client side, please don't hesitate to let me know.
I would appreciate it if you could post the solution here when you found it, so that other community members who have same question in this forum will benefit from it.
Best Regards,
Steve Fan
TechNet Community Support

Change to Exchange 2010 after SP3, Update 5 installed

After updating Exchange 2010 from SP3 Update 2 to Update 5, a change has occurred for users with SendAs and Full Access to other mailboxes. Version 14.3 (build 123.4).
Before the Update, after giving a user these permissions to another user's mailbox, the mailbox would show in their Outlook 2010 client, and everything worked as expected.
After Update 5 was installed, when users select the other user's mailbox, they get a message "the folders are not available," or the connection to the Exchange server is not working." They can access their own mailbox with no issues.
The other mailbox has to be added to the Outlook client via Account Settings, Account Settings, Change, More Settings, Advanced tab, Add the other mailbox. The mailbox then shows up twice on the client, but only the one that has been added works,
the original still gives the same error.
Lou H.

Hi,
I have seen some people have the same issue with you. After upgrading to Rollup 5, they need to add others' mailboxes that they have full access permission and send as permission manually on Outlook. But when they upgrade Outlook to 2010 SP2, this issue
is solved. I recommend you upgrade your Outlook to 2010 SP2 and check the result.
Besides, I'm not sure what changes after Rollup 5 lead to this issue, there is no official article explain it, thanks for your understanding.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Cannot read message bodystructure from Exchange 2010 with IMAP

Hi,
I'm trying to read mails from MS Exchange 2010 that have multipart/mixed content type and contain only one text/html part. I'm using IMAP and the newest Javamail 1.4.3. The mail processing fails when trying to fetch the bodystructure. I can process the same message perfectly well from Exchange 2003:
BODYSTRUCTURE from Exchange Server 2003 (Works fine with javamail)
* 1 FETCH (BODYSTRUCTURE (("TEXT" "HTML" ("charset" "UTF-8") NIL NIL "7BIT" 242 5 NIL ("inline" NIL) NIL) "mixed" ("boundary" "----=_Part_28_1466852274.1263305065649") NIL NIL))BODYSTRUCTURE from Exchange Server 2010 (Does not obey specification, doesn't work with javamail)
* 1 FETCH (BODYSTRUCTURE ("multipart" "mixed" ("boundary" "----=_Part_1_1045289550.1263292469650") NIL NIL NIL 0 NIL NIL NIL NIL))Does anyone have same kind of problems? This seems to me like a bug in Exchange 2010, but does anyone know any work-around for this other than using POP3 that works with the same message?
Here's the message (slightly edited to protect the guilty):
Received: from XXX (10.1.2.152) by
YYY (10.1.3.154) with Microsoft SMTP Server id
14.0.639.21; Tue, 12 Jan 2010 12:34:29 +0200
From: "XXX@YYY" <XXX@YYY>
Reply-To: <XXX@YYY>
To: Receiver <XXXX@YYY>
Message-ID: <1765234390.11263292469652.JavaMail.XXX@YYY>
Subject: Phone order: Mobile phone for mobile employees
Content-Type: multipart/mixed;
 boundary="----=_Part_1_1045289550.1263292469650"
Return-Path: ZZZ@YYY
Date: Tue, 12 Jan 2010 12:34:29 +0200
X-MS-Exchange-Organization-AuthSource: XYZ
X-MS-Exchange-Organization-AuthAs: Anonymous
MIME-Version: 1.0
------=_Part_1_1045289550.1263292469650
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
 I would like to order the following phone:
 Mobile phone for mobile employees
 
 
 Best regards,
 XXX@YYY
 
------=_Part_1_1045289550.1263292469650--Cheers,
Kai

Yup, looks like a bug in Exchange 2010, please report it to Microsoft.
If Microsoft gives you a bug ID or any way to track this bug, please let me know.
Try this workaround:
[http://java.sun.com/products/javamail/FAQ.html#imapserverbug|http://java.sun.com/products/javamail/FAQ.html#imapserverbug]

How to reset logs on Exchange 2010 after Event 518 stops backups from completing?

I'm only able to find references to resetting logs Exchange 2000 and 2003. I'm looking for info for Exchange 2010.
There appears to be some kind of corrupt logs issue with one of our mailbox databases. The corrupt logs cause the full backup to fail and because the full backup fails, the logs just get worse and keep growing.
The server has event ID 518 that says a log is "is missing (error -528) and cannot be used. If this log file is required for recovery, a good copy of the log file will be needed for recovery to complete successfully. "
How do e get past this and stop the backup job from trying to look for this log file and start over? I know that a full backup is supposed to clear the logs, but it will not happen because the backup never completes due to this log error.

its still same for 2010
Stop all the databases in the storage group.
Verify the state of each database file in the particular storage group. For information about how to verify the state of each database file, see the "Database states" section.
Perform one of the following actions:
If one or more of the databases are in a Dirty Shutdown or Inconsistent state, determine which transaction log files can be removed without affecting database consistency.
For more information, see the "Log files" section.
If all the databases are in a Clean Shutdown or Consistent state, you may remove all the transaction log files except for the current transaction log file. Removing the
current log file when all databases are in a Clean Shutdown state will cause a reset of the log file sequence. This does not prevent databases from starting. However, a reset of the log file sequence affects the ability to roll a
database forward from a previous backup if the situation occurs.
Copy all the transaction log files that you want to remove to a different location before you permanently remove them from the transaction log hard disk. Do not permanently delete the transaction log files until you have
successfully completed a full online backup of all the databases in the storage group.

Cannot install Exchange 2010 after installing Exchange 2013

Hi,
I have the current setup as explained below.
Exchange 2010 SP3 Version 14.3 (Build 123.4)
I installed Exchange 2013 as well to the setup. After installation everything was fine, but my backup solution was not as good enough to support Ex2013. So, I had to roll back. I uninstalled Ex 2013.
On the new server (on which I actually installed EX 2013) I tried installing Ex 2010 but it failed. But, when I execute Get-ExchangeVersion I get these two.
AdminDisplayVersion                     ExchangeVersion
Version 14.3 (Build 123.4)              0.1 (8.0.535.0)
Version 14.0 (Build 639.21)             0.1 (8.0.535.0)
The first one is the live Exchange 2010 ( The first one which we had). When I try to run the setup, I am getting the following Error.
Error:
The following error was generated when "$error.Clear(); get-OfflineAddressBook -DomainController $RoleDomainController | where { $_.IsDefault } | Enable-OabWebDistribution" was run: "Object is read only because it was created by a future version
of Microsoft Exchange: 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0).".
What can I do now? My intention is just to create another Exchange Server for redundancy. I only have one EXchange server now. I tried installing EX 2013, and it seems not suit me because of backup issue. What I have in my mind is to get 2 Ex 2010 Servers.
Should I try uninstalling EX 2010 and installing it from the beginning on the new EX Server?
Thanks

Hi Steve,
I have the same situation, On a new server (on which I actually installed EX 2013) I tried installing Ex 2010.
In the Client Access Role install setup, I getting:
Error:
the following error was generated when "$error.Clear(); get-OfflineAddressBook -DomainController $RoleDomainController | where {$_.IsDefault} | Enable-OabWebDistribution" was run: "Object is read only because it was created by a future version of Microsoft
Exchange: 0.20 (15.0.0.0). Current supported version is 0.10 (14.0.100.0)
Admin Display Version
server 1 version 14.3
server 2 version 14.0 (Client Access Role Error)
how can I resolve this error?
Thanks.
Regards.

Ports Required to open between Exchange 2010 & 2013

Hi,
I have to introduce Exchange 2013 into Exchange 2010 environment that is in same Organization. There are 3 sites connected on which Exchange 2010 installed and 4 site will be Exchange 2013 and then mailbox will migrate to E2k13 servers.
All 4 sites and connected to MPLS link, please let me know what ports are required to open for Communication between mail flow.
From Internet OWA : 443 & 25 is sufficient for Mail flow.
Amit

Exchange does not support blocking any ports between individual Exchange Servers as well as Exchange to DC communication, so for internal communication everything has to be opened.
If you are just talking client traffic (OWA, ActiveSync, Outlook Anywhere) and smtp mail traffic from external sources, then you should only need 443 (client traffic) and 25 (smtp traffic).
https://social.technet.microsoft.com/Forums/en-US/bc21b467-76bb-4c86-b7e1-21daa82cc37a/ports-required-for-exchange-2013-installation?forum=exchangesvrdeploy

Recomendations/limitations or Pre-requisites from Account perspective for Exchange hybrid between Exchange 2010 & O365

Hi
I need to migrate a few users from Exchange 2010 on premises to O365. I will be using Hybrid mode. I need to know what are the recommendations & Pre-requisites or limitations from Account\Mailbox perspective?Please suggest.

Hello,
I think it will be more efficient to ask this question on Exchange Online forum:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2010 & different domains

Hi,
Inputs:
forest root domain ROOT1.xxx.com
root domain ROOT2.xxx.com
Exchange 2010 servers installed to ROOT2, all Microsoft Exchange Security Groups created in ROOT1.
Before the Exchange setup I did all preparations.
All default settings after install, group membership, permissions is OK.
Problem: when I trying to create new role group via ECP or PoSh I receive error message:
Active Directory operation failed on DC1.ROOT1.xxx.com. This error is not retriable. Additional
information: Access is denied.
Active directory response: 00000005: SecErr: DSID-03152612, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

Hi ,
Thank you for your question.
By the error, it has caused by permission. We could refer to the following steps to troubleshoot:
We could user administrator to if we could create a new role group, if administrator didn’t create a new role group, we could rebuild administrator or admin window profile. If administrator could create a new role group, we could check the permission.
With this specific admin, if she/or could create a database, recipient or public folder.
We could verified the server objects are added to Exchange Trusted Subsystems by the following steps:
   a. Open Active Directory Users and Computers
   b. Navigate Microsoft Exchange Security Group>Exchange Trusted Subsystem>Properties
   c. we could check if Exchange server has listed in Member tab
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Exchange 2010 Mailbox Recipient List changing

I’m running up against a brick wall.
This is the Exchange 2010 server (non SBS, running on W2012 Std physical, not Hyper-V). Customer did their own migration from Exchange 2003 several months ago, but were never able to complete decommissioning their old Exchange 2003 server, which I did.
I ran through cleanup on the new Exchange 2010 (Windows 2012) server. Their primary A/D is another Windows 2003 server, and did cleanup of DNS, etc.
They've been having a problem with a specific user (Debra) even before I decommissioned the old Exchange. Email on her new Win 8.1 system is flaky -- sometimes it works, sometimes it sort of works and sometimes it doesn’t work at all – meaning
that sometimes she gets mail in/out and other times she can send out mail, but people will get NDRs trying to send her email, and other times Outlook 2013 just says “disconnected”. Saying that, they have other users on Win 8.1 with no issues at all.
So, yesterday we created a whole new, different user name (Debra1) -- different email address, different display name, and deleted her old account (Debra) from both Exchange and AD. That didn't help. It worked for a while, and then stopped working.
Today, we reloaded her machine from scratch. The customer’s IT person on site just called me to report that not only are things still not working, but get this: if he goes to EMC, he does NOT see the new user account (Debra1) we created yesterday
for Debra, but the old one (Debra) which we deleted is appearing, And, another user (Anna) that we deleted yesterday is showing up in EMC.
But Active Directory on the win 2003 server shows the new Debra1 account, and the old Debra and Anna accounts do NOT appear.
What am I missing? What could be causing Exchange to reload mailbox users??
Thanks in advance!
Kevin Weilbacher
-Kevin Weilbacher (SBS MVP)
"The days pass by so quickly now, the nights are seldom long"
KW Support MVP Blog
MVP's do NOT work for Microsoft. We give our time freely to support the SBS community!

Hi Kevin,
From your description, I recommend you run the Get-Mailbox cmdlet and check if user Debra1 is in the list.
What's more, you can click Actions -> Refresh on right side of EMC to update users.
Besides, if a user cannot send or receive emails using Outlook , I recommend you check if OWA has the same issue at first.
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2010 accepted domain and email address policy

So I need some help as to which accepted domain is right for us. We are a single forest single domain that is subbed to a parent domain.
sub.domain.com
We run our own exchange 2010 separate from domain.com. We want all mail to show up as @domain.com for our users. The @domain.com will be configured to forward to @sub.domain.com. This is free Linux mail server that is separate from us.
In order to configure an email address policy for @domain.com I need to pick from the 3 types. I am pretty sure we are not authoritative for @domain.com (they are the parent). So it is either an internal relay or external relay. We all
use the same networking, and our DNS servers point to domain.com as forwarders and they host a secondary copy of our DNS.
It is a little unclear as to which to use. I have gone to each account individually to test, and that works perfectly, but I would like to set this Globally.
Thanks
Tim

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2010 Sp3 AD Schema Changes

I am looking for a listing of Active Directory Schema Updates that Exchange 2010 SP3 makes. We are currently on SP1, and we will most likely end up at SP2 RU6, but if the changes are minimal to SP3, we may go ahead and extend the AD Schema to SP3 just
so we don't need to involve the AD Team again. Does anyone know where to find a complete list of AD Schema updates from Exchange 2010 SP3? I've checked:
Exchange Server changes to the Active Directory Schema webpage, but it does not have SP3, only Sp2.
Any help would be GREATLY appreciated.
Thanks!
Mark Currans

Please ensure that SP3 has been tested and validated by all the 3rd party apps and services in your org. You do not want to install it to find out that vendor X will no longer support you.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Message looping between Exchange 2003 & Exchange 2010 after domain type changed to internal relay

Similar Messages

Maybe you are looking for