New Exchange 2003 Server will not act as a bridgehead properly

Posted on 2007-07-24
Last Modified: 2010-03-06
I have just added a new Exchange 2003 server to my environment which currently consists of 6 2003 Exchange server and 1 2003 Exchange Front End server.
Currently 2 of my existing servers act as Bridgeheads and handle sending all mail. I would like to make the new one a bridgehead.
All sites are connected using MPLS circuits.
My new Exchange server will not receive mail from the other servers in order to attempt to deliver. I have confirmed this by removing all servers as bridgeheads except the new one. Whenthis happens all mail queues. When I add one of my other servers as a bridgehead then mail flows again.
I can access mailboxes on the new server via the Front End using OWA. Also, I can send mail out to the internet from mailboxes located on the new server. Finally if I telnet to 25 I get a valid response.

I am at a loss.
Question by:woolieb

    Author Comment

    Just to give an update, I can telnet "servername" 25 internally between servers. I can do this both ways.
    LVL 13

    Accepted Solution

    After you move bridgehead from the working server to a new machine you must manually run
    IISRESET command on the new server and also restart exchange MTA service.
    This will force the system to use the new bridgehead.
    Try and tell me
    LVL 104

    Assisted Solution

    Are you using routing groups and routing group connectors?
    Have you adjusted the FQDN on the SMTP virtual server to something other than the server's internal name? (That isn't a bad thing, just need to know if you have done that).

    Exchange routes email using information that you may not be aware of, incuding the value of the FQDN on the SMTP virtual server. If the SMTP VS is set to All unasssigned you can also get problems. Changing it to a specific IP address and then recreating any RGCs/SMTP Connectors will often fix the issue.

    Running IIS Reset and the service restart simply speeds up the process. Exchange will start using the new information on its own after about 10 minutes.


    Author Comment

    The changes to the SMTP Virtual Server and restarting of services seems to do the trick. I will continue testing and post my findings shortly.

    Thanks to both of you.


    Author Comment

    OK, I have a new problem related to this.

    I successfully moved a mailbox from the old server to the new one. Now, internal and external mail for the user moved are stuck in the "Messages queued for deferred delivery" folder.

    I had previously created a new mailbox on the new server and that user can send and receive all mail with no problems.

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Join & Write a Comment

    Use email signature images to promote corporate certifications and industry awards.
    Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
    In this video we show how to create an email address policy 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…
    The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

    754 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

    Need Help in Real-Time?

    Connect with top rated Experts

    20 Experts available now in Live!

    Get 1:1 Help Now