Exchange server on same subnet as other servers from other domains will not transact mail with those other servers

As the title suggests, I have a block of IP addresses in which I have sat a number of servers running Exchange Server, of various versions.

They are all servers I am hosting for clients, and my Exchange Server is in the same block of IPs.

Each Exchange Server is for a different Internet domain, and works as expected, except one.

My server cannot send mail to one of the others. Investigation has found that it will not accept mail from any of the four other Exchange Servers on that block of IPs, either.

If I log on to any of the other Exchange Servers via RDP and Telnet to the rogue server (SBS 2008, Exchange 2007) on port 25 I get:

421 4.3.2 Service not available, closing transmission channel

I figured I would add all the IPs in the block to the Network tab of the default Receive Connector. After doing so I can Telent from any of the server in the IP block to the problem child on port 25 and it opens a connection.


But, mail does not get through, and I get a message that it is queued for a later delivery attempt.

What else should I do?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

snooflehammerAuthor Commented:

This is the latest bounce message (sanitised) after I have attempted to whitelist the IPs in the IP block:

Diagnostic information for administrators:
Generating server: SENDINGSERVER.sendingdomain.local
SBS2008.receivingserver.local #530 5.7.1 Client was not authenticated ##
Original message headers:
Received: from SENDINGSERVER.sendingdomain.local ([fe80::28b8:a53a:7083:343]) by
 SENDINGSERVER.sendingdomain.local ([fe80::28b8:a53a:7083:343%12]) with mapi; Tue,
 20 Oct 2015 17:01:27 +1000
From: Me The Sender <>
To: "" <>
Date: Tue, 20 Oct 2015 17:01:09 +1000
Subject: Tester 3
Thread-Topic: Tester 3
Thread-Index: AdELBReKCB1AFGVrT4W91eiWEaUnzw==
Message-ID: <0E7D484632136044B4B37008508D34340284DF5650CA@SENDINGSERVER.sendingdomain.local>
Accept-Language: en-US, en-AU
Content-Language: en-US
acceptlanguage: en-US, en-AU
x-tm-as-product-ver: SMEX-
x-tm-as-result: No--42.453300-5.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative;
MIME-Version: 1.0
Andy MIT Systems ManagerCommented:
I would start by having a look at the SMTP send and receive logs on the servers. These should indicate if the receiving server has even acknowledged the connection from the sending server, which receive connector is in use, and whats actually happening during the process.

The bounceback you copied indicates that the receiving server is expecting the sending server to authenticate with it before sending email which I wouldn't expect for two un-related servers trying to send emails to each other.

Also having an SBS server on the same subnet as other domain controllers/exchange servers can cause issues as it doesn't play well with others. Ideally each server needs to be on it's own subnet/vlan and communicate with each other via the router rather than directly with each other (which if each server is for a different client) could be seen as a security risk.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.