Second Exchange Server Mail Delivery Issues

DeLynn Berry · Joined: 06 Aug 2007 Posts: 7

I've recently added a second exchange server to my organization with
the intention of moving all my current users onto the new server.

To test that the new server was working correctly I created a new user
account in Active Directory and created a mailbox on the older server.
After confirming that mail could be delivered from both inside and
outside my network, I moved the mailbox to the new server. Doing so
causes mail originating from outside the network or from accounts on
the old server to no longer being delivered. I noticed that any email
addressed to this moved account shows up in the SMTP queue of the old
server and the connection is listed as "exchange-02.domain.com"
instead of like a regular external deliver attempt entry (which looks
like "exchange-01 - fqdn.outsidedomain.com").

I have also created a new Active Directory account with the mailbox
existing first on the new server. Mail delivery to and from this
account to the account that was moved from the first server works just
fine, but does not work for mail attempting to go to or from the first
server. Again mail destined from the second server to the first ends
up in the second server's SMTP queue and is listed as
"exchange-01.domain.com".

I've spent several hours searching these message boards and the rest
of the Internet trying to figure out the issue, but as of yet haven't
found anything. I have confirmed most of the solutions that have be
listed for the issues even remotely sounding like they relate to my
issue. These items are:

1. SMTP connections can manually be made manually between the two
servers by telneting to port 25. Mail is delivered correctly via this
method as well.

2. Smart hosts are not configured on the SMTP instances of either
server.

3. Smart hosts are not configured on the default "exchange-01" routing
group connector.

4. Adding a connector for "exchange-02" doesn't solve the problem.
Adding "exchange-02" to the Local bridgeheads list of the exchange-01
connector doesn't solve the problem.

5. A DNS record for "exchange-02" does exist and resolves correctly.

6. Adding an internal MX record for "exchange-02.domain.com" does not
solve the issue (currently removed).

7. According to the properties of each server, the exchange version is
identical (Version 6.0 Build 6249.4: Service Pack 3).

I really am at a loss. Obviously a connection between the two servers
is missing, but I just don't know what else it could be. I'm hoping
someone here might be able to help me out. Thanks in advance.

--
DeLynn Berry
delynn@gmail.com

Archived from group: microsoft>public>exchange2000>setup>installation

Leif Pedersen [MVP] · Joined: 05 Aug 2007 Posts: 193

Hi,

Sounds like you have tested everything.

Can you from exchange02 telnet exchange-02.domain.com on port 25?

This tool might help:
http://www.microsoft.com/downloads/details.aspx?FamilyID=c5a8afbf-a4da-45e0-adea-6d44eb6c257b&DisplayLang=en

Leif

"DeLynn Berry" wrote in message @o11g2000prd.googlegroups.com...
> I've recently added a second exchange server to my organization with
> the intention of moving all my current users onto the new server.
>
> To test that the new server was working correctly I created a new user
> account in Active Directory and created a mailbox on the older server.
> After confirming that mail could be delivered from both inside and
> outside my network, I moved the mailbox to the new server. Doing so
> causes mail originating from outside the network or from accounts on
> the old server to no longer being delivered. I noticed that any email
> addressed to this moved account shows up in the SMTP queue of the old
> server and the connection is listed as "exchange-02.domain.com"
> instead of like a regular external deliver attempt entry (which looks
> like "exchange-01 - fqdn.outsidedomain.com").
>
> I have also created a new Active Directory account with the mailbox
> existing first on the new server. Mail delivery to and from this
> account to the account that was moved from the first server works just
> fine, but does not work for mail attempting to go to or from the first
> server. Again mail destined from the second server to the first ends
> up in the second server's SMTP queue and is listed as
> "exchange-01.domain.com".
>
> I've spent several hours searching these message boards and the rest
> of the Internet trying to figure out the issue, but as of yet haven't
> found anything. I have confirmed most of the solutions that have be
> listed for the issues even remotely sounding like they relate to my
> issue. These items are:
>
> 1. SMTP connections can manually be made manually between the two
> servers by telneting to port 25. Mail is delivered correctly via this
> method as well.
>
> 2. Smart hosts are not configured on the SMTP instances of either
> server.
>
> 3. Smart hosts are not configured on the default "exchange-01" routing
> group connector.
>
> 4. Adding a connector for "exchange-02" doesn't solve the problem.
> Adding "exchange-02" to the Local bridgeheads list of the exchange-01
> connector doesn't solve the problem.
>
> 5. A DNS record for "exchange-02" does exist and resolves correctly.
>
> 6. Adding an internal MX record for "exchange-02.domain.com" does not
> solve the issue (currently removed).
>
> 7. According to the properties of each server, the exchange version is
> identical (Version 6.0 Build 6249.4: Service Pack 3).
>
> I really am at a loss. Obviously a connection between the two servers
> is missing, but I just don't know what else it could be. I'm hoping
> someone here might be able to help me out. Thanks in advance.
>
> --
> DeLynn Berry
> delynn@gmail.com
>

DeLynn Berry · Joined: 06 Aug 2007 Posts: 7

> Sounds like you have tested everything.

I thought so. Wink

This problem is very puzzling.

> Can you from exchange02 telnet exchange-02.domain.com on port 25?

Yep, I can telnet and deliver email from the second box to itself.

> This tool might help:http://www.microsoft.com/downloads/details.aspx?FamilyID=c5a8afbf-a4d...

I'll give this a shot and report back my findings.

Thanks.

--
DeLynn Berry
delynn@gmail.com

DeLynn Berry · Joined: 06 Aug 2007 Posts: 7

> > This tool might help:http://www.microsoft.com/downloads/details.aspx?FamilyID=c5a8afbf-a4d...
>
> I'll give this a shot and report back my findings.

Everything reported by WinRoute seems valid. Both servers are in the
same Routing Group and share the same Routing Master (which is the
original server in the organization). The version information for both
servers is identical as is the Routing Group Addresses section. Both
servers are showing up as members and are connected to the Master. The
first server in the organization is the only one that shows up in the
connectors section and all items in this section are identical for
both servers.

Is there something specific that I should be looking for?

--
DeLynn Berry
delynn@gmail.com

Leif Pedersen [MVP] · Joined: 05 Aug 2007 Posts: 193

Hi,

Just seen another similar problem. This was caused by symantec antivirus
software scanning SMTP traffic.

Do you by any chance have file based AV scanning SMTP on the Exchange
servers??

Leif

"DeLynn Berry" wrote in message @m36g2000hse.googlegroups.com...
>> > This tool might
>> > help:http://www.microsoft.com/downloads/details.aspx?FamilyID=c5a8afbf-a4d...
>>
>> I'll give this a shot and report back my findings.
>
> Everything reported by WinRoute seems valid. Both servers are in the
> same Routing Group and share the same Routing Master (which is the
> original server in the organization). The version information for both
> servers is identical as is the Routing Group Addresses section. Both
> servers are showing up as members and are connected to the Master. The
> first server in the organization is the only one that shows up in the
> connectors section and all items in this section are identical for
> both servers.
>
> Is there something specific that I should be looking for?
>
> --
> DeLynn Berry
> delynn@gmail.com
>

DeLynn Berry · Joined: 06 Aug 2007 Posts: 7

> Do you by any chance have file based AV scanning SMTP on the Exchange
> servers??

Okay, just to fill you in. Before getting your email I decided I would
completely uninstall and reinstall Exchange on the new server. My
thinking was that during my attempt to correct the issue I had
completely screwed something up and wanted to start the morning fresh.
Unfortunately this didn't fix a thing, and I was in the exact same
place that I was before.

I'm running NOD32 on both servers with the Exchange Monitor enabled. I
have an exclusion rule on the file scanning side in for the original
server to ignore the entire exchange installation and store
directories, but I did not have one for the new server. I just added
it and rebooted the new server, and I can now send email from accounts
(moved or new) on Exchange-02 to accounts on the Exchange-01 server. I
still cannot send email from an account on Exchange-01 or an account
outside our network to any account on Exchange-02. We're obviously
getting closer! Just so you know, I have verified the virus scanning
exclusion on Exchange-01 and rebooted the server, but I still can't
deliver from Exchange-01 to Exchange-02.

Thanks for your continued help with this issue.

--
DeLynn Berry
delynn@gmail.com

DeLynn Berry · Joined: 06 Aug 2007 Posts: 7

> I'm running NOD32 on both servers with the Exchange Monitor enabled. I
> have an exclusion rule on the file scanning side in for the original
> server to ignore the entire exchange installation and store
> directories, but I did not have one for the new server. I just added
> it and rebooted the new server, and I can now send email from accounts
> (moved or new) on Exchange-02 to accounts on the Exchange-01 server. I
> still cannot send email from an account on Exchange-01 or an account
> outside our network to any account on Exchange-02. We're obviously
> getting closer! Just so you know, I have verified the virus scanning
> exclusion on Exchange-01 and rebooted the server, but I still can't
> deliver from Exchange-01 to Exchange-02.

After sending this message, I decided to stop the File Watcher piece
of NOD32 on both machines. I restarted SMTP on both boxes and
attempted to send another test email from Exchange-02 to Exchange-01.
This email still worked successfully, but my reply from Exchange-01 to
Exchange-02 is still sitting in the Exchange-01 SMTP queue.

--
DeLynn Berry
delynn@gmail.com

DeLynn Berry · Joined: 06 Aug 2007 Posts: 7

> After sending this message, I decided to stop the File Watcher piece
> of NOD32 on both machines. I restarted SMTP on both boxes and
> attempted to send another test email from Exchange-02 to Exchange-01.
> This email still worked successfully, but my reply from Exchange-01 to
> Exchange-02 is still sitting in the Exchange-01 SMTP queue.

So after doing some additional searching online I discovered,
downloaded, installed and ran the Exchange Troubleshooting Assistant.
The only issue that it found was during the mail acceptance test. Both
servers say the other fails this test due to the BDAT response not
being correct. The exact error is:

"Remote server exchange-01.domain.com failed the mail acceptance test.
BDAT command: Respond = . Check for firewalls and applications that
can possible block the BDAT command."

Neither machine is running a local firewall and both are on the same
switch, so I don't think the issue is connection related. I also don't
know of any software that is running on both machines that could be
blocking this command. I've searched online in an attempt to figure
out how to get the BDAT response to be correct, but everything that
I'm finding relates to the Exchange SMTP server talking to some other
outside SMTP server.

Anyone have any ideas as to what might be going on here?

Thanks.

--
DeLynn Berry
delynn@gmail.com

Leif Pedersen [MVP] · Joined: 05 Aug 2007 Posts: 193

Hi,

Just read the postings again.

In your original post you wrote that you just added a second server to your
exchange organization, but later when you wrote about the winroute result
you mentioned the original server being the routing group master.

Do you have a ghost server or are there really three servers in the org.??

If there is a ghost server maybe this server should be completely removed
before proceeding.

Leif

"DeLynn Berry" wrote in message @g4g2000hsf.googlegroups.com...
>> After sending this message, I decided to stop the File Watcher piece
>> of NOD32 on both machines. I restarted SMTP on both boxes and
>> attempted to send another test email from Exchange-02 to Exchange-01.
>> This email still worked successfully, but my reply from Exchange-01 to
>> Exchange-02 is still sitting in the Exchange-01 SMTP queue.
>
> So after doing some additional searching online I discovered,
> downloaded, installed and ran the Exchange Troubleshooting Assistant.
> The only issue that it found was during the mail acceptance test. Both
> servers say the other fails this test due to the BDAT response not
> being correct. The exact error is:
>
> "Remote server exchange-01.domain.com failed the mail acceptance test.
> BDAT command: Respond = . Check for firewalls and applications that
> can possible block the BDAT command."
>
> Neither machine is running a local firewall and both are on the same
> switch, so I don't think the issue is connection related. I also don't
> know of any software that is running on both machines that could be
> blocking this command. I've searched online in an attempt to figure
> out how to get the BDAT response to be correct, but everything that
> I'm finding relates to the Exchange SMTP server talking to some other
> outside SMTP server.
>
> Anyone have any ideas as to what might be going on here?
>
> Thanks.
>
> --
> DeLynn Berry
> delynn@gmail.com
>

DeLynn Berry · Joined: 06 Aug 2007 Posts: 7

> In your original post you wrote that you just added a second server to your
> exchange organization, but later when you wrote about the winroute result
> you mentioned the original server being the routing group master.
>
> Do you have a ghost server or are there really three servers in the org.??
>
> If there is a ghost server maybe this server should be completely removed
> before proceeding.

In the WinRoute post when I stated "is the original server in the
organization" I was referring to Exchange-01. Meaning Exchange-01 is
the original server in the organization and it is listed as the
routing group master. The only servers that appear anywhere in any of
the tools I have used are Exchange-01 or Exchange-02.

Any ideas on the BDAT error that I referenced in my last post?

--
DeLynn Berry
delynn@gmai.com

exchange 2003 service pack 2 local delivery queue retry I have a client thats running SBS 2003 with all the service packs installed. They are not receiving emails and the local drlivery queue is backed up. How do I get the messages to deliver to the users mail boxes? Thanks! Mark S. Daly

internet mail connector on front-end server? we currently have an Exchange 2003 SP1 server that's only running the Internet Mail connector. we want to now make it a front-end server (for setting up and configured OWA/VPN question, although the option box is there to switch

Installing new Exchange 2K server to replace old 2K server It is time to replace my old Exchange 2K server. I have another W2K server on my network with Win 2K SP4 and all the currect updates. Both servers are DC's with a single Domain environment. My existing E2K server was installed clean 3 years ago no upgra

how do you keep some exchange users on internal mail only? how do you keep some exchange users on internal mail only? We want to allow some of our user to get mail internally and externally (from the internet). Others we only want to allow interal email (nothing from the internet).

reintsall of exchange server I am planning on doin a complete reformat and reinstall of server 2000 and exchange 2000. Is there a good resource for directions on how ot correctly backup my data and then get the database remounted and running again? Thanks