?
Solved

Exchange 2010 Not Replicating Public Folders Back to Exchange 2003

Posted on 2013-01-08
7
Medium Priority
?
357 Views
Last Modified: 2013-04-03
We have an Exchange Server 2010 running on a VMware virtual Windows Server 2008R2 x64.  We also have our older Exchange 2003 server running on Windows Server 2003 x32.  We are running both servers in tandem while we upgrade a number of other systems to be compatible.  I have configured the replication of the public folders from 2003 to 2010 and messages are coming across fine.  But posts to the 2010 server seem to take hours if not days to migrate back to the 2003 server.  I don't have much experience with 2010 but everything looks to be OK.  How do I troubleshoot this?
0
Comment
Question by:CIPortAuthority
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
7 Comments
 

Author Comment

by:CIPortAuthority
ID: 38758584
Sorry, but I don't think my original post was clear.  The user mailboxes are fine and email gets sent without issue.  It is only posts to public folders done by users connected to the Exchange 2010 server that are not getting replicated back to the Exchange 2003 server.  This is only an issue with public folders.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38758610
Public Folder replication can be very slow, there is nothing much you can do about it to speed things up. Unusual to see new items being that slow though - so ensure that you have public folder replication set to Always under the time settings.

Simon.
0
 

Author Comment

by:CIPortAuthority
ID: 38758762
I should also post a correction.  It looks like changes made by 2010 users to public folders are not being replicated to the 2003 server at all.  I had originally assumed they were because I was getting error emails about conflicts between changes made to the same item on both servers.  I guess it is only the change from the 2003 server replicating to the 2010 server causing the error.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 

Author Comment

by:CIPortAuthority
ID: 38758976
Here is a content message from the Exchange 2010 server (PROSPECT) to the Exchange 2003 server (SAVANAH):
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 EHLO - +EXCHANGE2010.local 250 0 315 28 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 x-exps - +GSSAPI 0 0 22 13 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 MAIL - +FROM:<PublicFolderDatabase0765155492@local> 250 0 70 83 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 RCPT - +TO:<SAVANAH-IS@local> 250 0 0 48 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 xexch50 - +144+2 354 0 22 13 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 received: - +from+EXCHANGE2010.local+([fe80::ec2f:xxx:xxx:xxx])+by 500 0 32 71 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 - - +EXCHANGE2010.local+([fe80::ec2f:xxx:xxx:xxx%14])+with+mapi+id 500 0 32 70 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 - - +14.02.0318.004;+Wed,+9+Jan+2013+08:51:40+-0500 500 0 32 47 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 content-type: - +application/ms-tnef;+name="winmail.dat" 500 0 32 53 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 content-transfer-encoding: - +binary 500 0 32 33 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 from: - +Public+Folder+Database+<PublicFolderDatabase0765155492@local> 500 0 32 76 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 subject: - +Status+Request 500 0 32 23 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 thread-topic: - +Status+Request 500 0 32 28 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 thread-index: - +Ac3ucHLb7xZlBGIbR5u+tmMHx+9FiA== 500 0 32 46 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 date: - +Wed,+9+Jan+2013+13:51:39++0000 500 0 32 36 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 message-id: - +<D1DC9AD876BF874D82291DC9B855836A0106B40EB7@EXCHANGE2010.local> 500 0 32 80 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 keywords: - - 500 0 32 9 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 x-ms-has-attach: - - 500 0 32 16 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 x-ms-tnef-correlator: - +<D1DC9AD876BF874D82291DC9B855836A0106B40EB7@EXCHANGE2010.local> 500 0 32 90 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 mime-version: - +1.0 500 0 32 17 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 MAIL - +FROM:<PublicFolderDatabase0765155492@local>+SIZE=4162+BODY=BINARYMIME 503 0 36 83 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 RCPT - +TO:<SAVANAH-IS@local> 250 0 0 48 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 RCPT - +TO:<SPOTBAY-IS@local> 250 0 0 48 31 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 MAIL - +FROM:<PublicFolderDatabase0765155492@local> 250 0 70 83 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 RCPT - +TO:<SAVANAH-IS@local> 250 0 0 48 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 MAIL - +FROM:<PublicFolderDatabase0765155492@local> 250 0 70 83 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 RCPT - +TO:<SAVANAH-IS@local> 250 0 0 48 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 MAIL - +FROM:<PublicFolderDatabase0765155492@local> 250 0 70 83 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 RCPT - +TO:<SAVANAH-IS@local> 250 0 0 48 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 MAIL - +FROM:<PublicFolderDatabase0765155492@local> 250 0 70 83 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 RCPT - +TO:<SAVANAH-IS@local> 250 0 0 48 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 MAIL - +FROM:<PublicFolderDatabase0765155492@local> 250 0 70 83 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 RCPT - +TO:<SAVANAH-IS@local> 250 0 0 48 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 xexch50 - +144+2 354 0 22 13 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 RCPT - +TO:<SAVANAH-IS@local> 250 0 0 48 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 xexch50 - +144+2 501 0 36 13 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 received: - +from+EXCHANGE2010.local+([fe80::ec2f:xxx:xxx:xxx])+by 500 0 32 71 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 - - +EXCHANGE2010.local+([fe80::ec2f:xxx:xxx:xxx%14])+with+mapi+id 500 0 32 70 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 - - +14.02.0318.004;+Wed,+9+Jan+2013+09:04:51+-0500 500 0 32 47 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 content-type: - +application/ms-tnef;+name="winmail.dat" 500 0 32 53 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 content-transfer-encoding: - +binary 500 0 32 33 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 from: - +Public+Folder+Database+<PublicFolderDatabase0765155492@local> 500 0 32 76 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 subject: - +Folder+Content 500 0 32 23 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 thread-topic: - +Folder+Content 500 0 32 28 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 thread-index: - +Ac3uckotrKMxPmprSu+nLIasFwk/EQ== 500 0 32 46 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 date: - +Wed,+9+Jan+2013+14:04:50++0000 500 0 32 36 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 message-id: - +<D1DC9AD876BF874D82291DC9B855836A0106B41F55@EXCHANGE2010.local> 500 0 32 80 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 keywords: - - 500 0 32 9 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 x-ms-has-attach: - +yes 500 0 32 20 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 x-ms-tnef-correlator: - +<D1DC9AD876BF874D82291DC9B855836A0106B41F55@EXCHANGE2010.local> 500 0 32 90 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 mime-version: - +1.0 500 0 32 17 0 SMTP - - - -
2013-01-09 14:05:24 172.16.xxx.xx EXCHANGE2010.local SMTPSVC1 SAVANAH 172.16.xxx.xx 0 QUIT - EXCHANGE2010.local 240 297 32 4 0 SMTP - - - -

Open in new window


Maybe some clues can come from this?
0
 

Accepted Solution

by:
CIPortAuthority earned 0 total points
ID: 38759452
I have figured out what is happening.  We have GFI MailEssentials 2012 on our Exchange 2003 server and its Directory Harvesting anti-spam module is blocking the emails because the SAVANAH-IS@local address is not a valid AD address.  I am working with GFI to find a solution.
0
 

Author Closing Comment

by:CIPortAuthority
ID: 38773802
Discovered the solution myself.
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
In this video we show how to create an Address List in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Organization >> Ad…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question