[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 219
  • Last Modified:

Error 421 service not available remote server has closed connection

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
Deorali
Asked:
Deorali
  • 3
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
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
 
DeoraliAuthor Commented:
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
 
Simon Butler (Sembee)ConsultantCommented:
Is this an SBS Server?

Simon
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Mohammed KhawajaCommented:
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
 
DeoraliAuthor Commented:
@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
 
DeoraliAuthor Commented:
Please close this ticket.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now