Hello

I have problems with two exchange servers

After I installed new Exchange 2003 Server on Exchange 2000 Organization I
get NDR message when I send messages from the old server (or from the
Internet) to the new one (Old server is Exchange 2000 and a new one is
Exchange 2003)

When I send message from the old server to the new one (TestUser have
mailbox on new server) i get this NDR:

The following recipient(s) could not be reached:
TestUser on 24.8.2004 15:48
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.
<exchange.domain.local #5.3.5>

I have only one default SMPT connector which is routing all messages to the
Internet (Local Bridgehead is Exchange2000 Server, address space is *, and
cost is 1)

Thanks in anticipation,
Vice

[ Post a follow-up to this message ]

This NDR indicates a loop due to name resolution or DNS.

Firstly, if you have any internal MX records remove them; CNAMES improperly
configured should follow suit. Secondly, verify that the FQDN specified on
the SMTP virtual server properties resolves only to the IP of that the
sending and receiving servers respectively. You can use Nslookup to verify
this.


Eg. Nslooup
set q=any
oldSErver

"vice" <vice@lama.hr> wrote in message
news:OF67sQeiEHA.636@TK2MSFTNGP12.phx.gbl...
> Hello
>
> I have problems with two exchange servers
>
> After I installed new Exchange 2003 Server on Exchange 2000 Organization I
> get NDR message when I send messages from the old server (or from the
> Internet) to the new one (Old server is Exchange 2000 and a new one is
> Exchange 2003)
>
> When I send message from the old server to the new one (TestUser have
> mailbox on new server) i get this NDR:
>
> The following recipient(s) could not be reached:
> TestUser on 24.8.2004 15:48
> 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.
> <exchange.domain.local #5.3.5>
>
> I have only one default SMPT connector which is routing all messages to
> the
> Internet (Local Bridgehead is Exchange2000 Server, address space is *, and
> cost is 1)
>
> Thanks in anticipation,
> Vice
>
>

[ Post a follow-up to this message ]

Hi,

I have the same problem. So, Ade Famoti, can you tell me more detial or guid
e me how to fix it step-by-step ? 

Thanks for millions !!!!

[ Post a follow-up to this message ]

Can you give some more detail on your configuration.

Things to look for are:

1. On the SMTP virtual server : Advanced : delivery tab : make sure the
smarthost is not the IP or servername of the server having the issue.

2. On your SMTP connectors, make sure none of them have the address space of
"yourdomain.com"

3. On your SMTP connectors, make sure you dont have a connector that has the
smarthost has the local server name or IP.

4. If you are using smarthosts correctly, make sure the DNS entry for the
smarthost servers points to the smarthost , and not the local server.

Let me know if any of these help.

Ade

"quynhtuan" <quynhtuan.1dc3x4@mail.webservertalk.com> wrote in message
news:quynhtuan.1dc3x4@mail.webservertalk.com...
>
> Hi,
>
> I have the same problem. So, Ade Famoti, can you tell me more detial or
> guide me how to fix it step-by-step ?
>
> Thanks for millions !!!!
>
>
>
> --
> quynhtuan
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message363576.html
>

[ Post a follow-up to this message ]

Hi Ade Famoti [MSFT],

First, I wanna thank for enduring with me.
Second, I want to you know I'm not expert in MS Exchange so that I just only
 answer your question and do what you think I should do.

Here is some informations:

1. On the SMTP virtual server : Advanced : delivery tab : make sure the smar
thost is not the IP or servername of the server having the issue.  <--------
  It's OK.

2. On your SMTP connectors, make sure none of them have the address space of
 "yourdomain.com"  <---- I don't know, I can't find any connector except the
 connector which located in Routine Group, so that I attached the pic about 
my configuration to seeing clearly. 

3. On your SMTP connectors, make sure you dont have a connector that has the
 smarthost has the local server name or IP. <---------- please see the pictu
re attached.

4. If you are using smarthosts correctly, make sure the DNS entry for the sm
arthost servers points to the smarthost , and not the local server. <-------
---  I guess I'm using smarthost, please see the picture 


Hope hear you soon !

[ Post a follow-up to this message ]

This thread is old, but I had this problem, and the cause was a little stran
ge, so I'll post it here in case someone Googles in for a solution.

The problem was arising when moving the bridghead servers for outgoing SMTP 
to a new SMTP gateway server - all outgoing mail was bouncing with a 5.3.5 N
DR. 

It turned out that the "Fully qualified domain name" (Delivery Tab/Advanced)
 was set to present the new server with its official (outside) name when rec
eiving mail, as many administrators do. However, this name was in the intern
al DNS pointing to to the old bridgehead, which was a store server.

When routing the message, exchange seems to do the following:
1. Pick the SMTP virtual server to use from the address space definitions.
2. Get the "Fully qualified domain name" from the picked SMTP virtual server
s definition.
3. Make a DNS lookup for the name above.
4. Connect to the IP received.

That IP address was the address of the sending server, so it was talking to 
itself  before returning the NDR.

The problem was solved by changing the IP on the A-record in DNS for the ser
ver named above (In the "Fully quallified domain name" field) to the correct
 IP address of the new bridgehead server.

[ Post a follow-up to this message ]