I'm in the process of moving an existing Exchange 2000 SP3 (with august 2004 roll-up) which we'll call SERVER1, to a new Exchange 2000 SP3 (with august 2004 roll-up) which we'll call SERVER2.
I configured the PF to replicate to the new server. The folders seemed to replicate fine, but only some of the content was delivered to the new server. Then suddenly a day later, a little more content was delivered.
I have all of the diagnostic logging turned on, you can see the request and replies flowing through both servers correctly.
What I've found in troubleshooting, is that the content backfill request and other updates sit in the outbound SMTP queue on SERVER1. If I force a connection, you can see the 87 messages (14MB of data) spool off SERVER1. Once the size goes to zero the queue resets and all the messages are still there, almost as if SERVER2 is rejecting the transfer. Eventually the backfill requests timeout on SERVER2, so it re-issues another request and the cycle begins again. The recieving SERVER2 shows that SERVER1 authenticates correctly for the SMTP transfer, and I have no errors on either server. There is nothing stuck in the SMTP queue on SERVER2.
There is no anti-virus or anti-spam on SERVER2, it's a fresh install. I've tried disabling the anti-spam & anti-virus on the production SERVER1 server and the behavior is the same.
I've read many other posts about how replication takes weeks, but I'm only looking at 300MB or so of data. If I could figure out why the SMTP transfer is being rejected, then maybe I can get this thing replicating. And also figure out why a transfer was sporadically allowed.
Nothing like a 8 hour migration turning into a week long process, and I'll be damned if I'll pay Micro$oft for a $500 weekend support call.
Thanks in advance.