Solved

Error 421 service not available remote server has closed connection

Posted on 2014-03-07
6
158 Views
Last Modified: 2015-05-31
Hi Exchange Expert,

This morning I had an inbound mail issue. Outbound email was fine and working normal. There was intermittent inbound mail issue. No modification on exchange server configuration.

Error returned:

Error 421 service not available remote server has closed connection. Even when I tried to telnet from outside I got an error 421 4.3.2 service not available.

It started working after I adding 0.0.0.0 - 255.255.255.255 to receive connector -receive mail from remote servers list.

It was working fine until yesterday without specifying this IP range.

Any thoughts?

Thanks,

Deorali
0
Comment
Question by:Deorali
  • 3
  • 2
6 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39912882
You must have had some kind of range in there for it to accept email.
The error you have posted is exactly what I would have expected if the range was wrong.
Furthermore it would have had that range in by default, unless it is an SBS server.

Simon.
0
 
LVL 1

Author Comment

by:Deorali
ID: 39913023
This is what I had before and the mail was flowing without having to add the new range 0.0.0.0 - 255.255.255.255
receiveconnector.JPG
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39913182
Is this an SBS Server?

Simon
0
Don't lose your head updating email signatures!

Do your end users still have the wrong email signature? Do email signature updates bore you or fill you with a sense of dread? You can make this a whole lot easier on yourself by trusting an Exclaimer email signature management solution. Over 50 million users do...so should you!

 
LVL 24

Expert Comment

by:Mohammed Khawaja
ID: 39913185
There could be two possibilities:

1. Low disk space and for more see  http://support.microsoft.com/kb/284204
2. Backpressure feature and for more see http://technet.microsoft.com/en-us/library/bb201658.aspx
0
 
LVL 1

Accepted Solution

by:
Deorali earned 0 total points
ID: 39913314
@Simon: Exchange 201 SP3.  Thanks.  After comparing range of IPs  with the original configuration,  found out that one of the co-workers removed an IP range 10.1.4.56 - 192.168.170 (pretty much this was there when I took over as Exchange admin) last night from the receive connector. Therefore, by me adding IP range 0.0.0.0- 255.255.255.255 might have resolved the issue.


@mnkhwaja: Not an issue with low disk space or backpressure and I mentioned above that after adding 0.0.0.0-255.255.255.255 to the receive connector it started working.

Thanks,

Chatur Tamang
0
 
LVL 1

Author Closing Comment

by:Deorali
ID: 40804718
Please close this ticket.
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Easy CSR creation in Exchange 2007,2010 and 2013
In this video we show how to create a Shared Mailbox 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 Recipients >> Sha…
In this video we show how to create an Address List 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 Organization >> Ad…

708 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

17 Experts available now in Live!

Get 1:1 Help Now