John
Wed Aug 16 20:50:27 CDT 2006
We are a small one domain company and want to move Exchange server to a new
computer with a different name in the same routing group. We install Windows
2003 Setandard Server and Exchange 2003 Standard Server with the identical
service pack and hotfixes. Then we move one mailbox to the new server and
test. In the new server it can send and receive all internal and external
emails, but the users in the old server cannot sent emails to the user in
the new server. The following error we got:
A configuration error in the e-mail system caused the message to bounce
between two servers or to be forwarded between two recipients. Contact your
administrator. <oldserver.domain.com#5.3.5>
In the old server event log, we got:
Event Type: Error
Event Source: MSExchangeTransport
Event Category: NDR
Event ID: 3017
Date: 7/08/2006
Time: 10:50:37 AM
User: N/A
Computer: Oldserver
Description:
A non-delivery report with a status code of 5.3.5 was generated for ...
Causes: A looping condition was detected. (The server is configured to route
mail back to itself). If you have multiple SMTP Virtual Servers configured
on your Exchange server, make sure they are defined by a unique incoming
port and that the outgoing SMTP port configuration is valid to avoid looping
between local virtual servers.
Solution: Check the configuration of the virtual server?s connectors for
loops and ensure each virtual server is defined by a unique incoming port.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: cf 02 04 c0 ?..¨¤
We have tried solutions provided by
http://support.microsoft.com/default.aspx?scid=kb;en-us;555418. We have
downloaded and check those 2 configurations before and am sure:
* there is no internal or external DNS configured in the SMTP virtual server
*SMTP address space is Asterisk (*) in the Exchange SMTP connector *there is
no smart host configured in the SMTP virtual server
However, the problem still exists. This makes me pulling my hair out.
"Bharat Suneja [MVP]" <bharatsuneja@no.spam.org> wrote in message
news:%2357aZUZwGHA.4512@TK2MSFTNGP05.phx.gbl...
> Not only is it possible, but it is done all the time.
> Install second server in the Exchange Org (by default installs in the same
> administrative group).
> Move mailboxes, replicate public folders. Follow kba 822931.
>
> If the old server is responsible for inbound internet mail:
> a) Firewall: Forward inbound smtp traffic to the new server
> b) External DNS: Point MX (or create another MX record with lower
> preference) to external/public IP of new server.
>
> Shut down the first/old server for a couple of days. If all looks good,
> uninstall Exchange from the old server.
> --
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> www.exchangepedia.com/blog
> ----------------------------------------------
>
>
> "Mr. JYC" <MrJYC@discussions.microsoft.com> wrote in message
> news:732BDDC3-DD83-419B-A11B-F776CE94A916@microsoft.com...
>> To Whom Can Help:
>>
>> Is it possible to add a second Exchange server on a network with the
>> intention of making the second Exchange server the primary Exchange
>> server?
>> Also, what would be required to migrate the information from the old
>> Exchange
>> server to the new one? Both Exchange servers will be Exchange 2003.
>> Would
>> it make a difference if the second Exchange server has a service pack
>> applied
>> if the first one doesn't?
>>
>> --
>> Thank you for your help!
>> JYC
>
>