Announcement

Collapse
No announcement yet.

Public Folder replication problem - only one way

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Public Folder replication problem - only one way

    Hi, it's my turn now.

    Existing Win2003 forest, one domain, all working fine.
    One Exchange 2003 SP2 server, all fine so far.

    I came in and installed another Exchange 2003 SP2 clustered server. All went ok, all working fine, except PF replication. The old server needs to be taken offline in a week or so, so I need to get things going on.

    I've configured all the System PF and the man-made PF on the old server to replicate to the new one, alas none have replicated, at all, and there's nothing in the old server's queue.

    When manually creating a new PF on the new server and configuring it to replicate to the old one, it does replicate just fine. However, if I add content to the same PF on the old server, I do NOT see it back on the new one.

    It seems that PF replication only works one way.

    I've tried to enable diagnostinc logging on the PF, and got several events claiming that users did not have enough permissions on PFs such as the OAB. I don't have it in front of me, but if required, I can get the exact syntax.

    The old server had issues in the past, before I came to that business, so it might be that the entire PF tree is somehow messed up.

    So - what do I do, except of just exporting everything to PST and just importing it to the new server? Should I even bother?
    Cheers,

    Daniel Petri
    Microsoft Most Valuable Professional - Active Directory Directory Services
    MCSA/E, MCTS, MCITP, MCT

  • #2
    Re: Public Folder replication problem - only one way

    What does message tracking say? I have seen this before, where the replication traffic was being sent to the new server and the new server was NDR them.

    Checked for a smart host on the SMTP VS of the old server?

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Public Folder replication problem - only one way

      Also check for external DNS servers on the SMTP Virtual Server.

      Simon.
      --
      Simon Butler
      Exchange MVP

      Blog: http://blog.sembee.co.uk/
      More Exchange Content: http://exchange.sembee.info/
      Exchange Resources List: http://exbpa.com/
      In the UK? Hire me: http://www.sembee.co.uk/

      Sembee is a registered trademark, used here with permission.

      Comment


      • #4
        Re: Public Folder replication problem - only one way

        Double check that sombody hasn't stopped the public folder content replication at the top level. EMS, org level, right click, if it says "resume public folder content replication" then thats your issue.

        Hope it helps

        Comment


        • #5
          Re: Public Folder replication problem - only one way

          Originally posted by Sembee View Post
          What does message tracking say? I have seen this before, where the replication traffic was being sent to the new server and the new server was NDR them.

          Checked for a smart host on the SMTP VS of the old server?

          Simon.
          Thanks Simon. No Smart Host anywhere, already checked that. I will look at message tracking. Thing is that there is nothing related to server-to-server traffic in the Queue of any of the servers (unless I send mail from one mailbox on the old server to another mailbox on the new one).
          Cheers,

          Daniel Petri
          Microsoft Most Valuable Professional - Active Directory Directory Services
          MCSA/E, MCTS, MCITP, MCT

          Comment


          • #6
            Re: Public Folder replication problem - only one way

            Originally posted by fmackie View Post
            Double check that sombody hasn't stopped the public folder content replication at the top level. EMS, org level, right click, if it says "resume public folder content replication" then thats your issue.

            Hope it helps
            Thanks, that's one of the first things I checked. It's not that. Thing is, that PF replication works from new > old, but not old > new...
            Cheers,

            Daniel Petri
            Microsoft Most Valuable Professional - Active Directory Directory Services
            MCSA/E, MCTS, MCITP, MCT

            Comment


            • #7
              Re: Public Folder replication problem - only one way

              Could it be the xexch50 smtp command verb not being used between the two servers? I think this is required for PF replication.

              Comment


              • #8
                Re: Public Folder replication problem - only one way

                Hmmmm... even if it is so, why would it happen? The second server is a brand new one...

                I'm just about to tell the guy to export everything to PST and import via OL to the new server after moving the mailboxes.
                Cheers,

                Daniel Petri
                Microsoft Most Valuable Professional - Active Directory Directory Services
                MCSA/E, MCTS, MCITP, MCT

                Comment

                Working...
                X