Learn how to a build a cloud-first strategyRegister Now

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

Unable to send mail - 4.2.1 Unable to connect error

Hi all,

I have a strange problem. everything has been working fine for a number of months then suddenly, no one could send email. recieving email is ok however.

details;
just the one server
Win server 2008
exchange 2007
symantec endpoint protection

the mail queue gives me the below error;
451 4.4.0 Primary Target IP Address responded with:"421 4.2.1 Unable to Connect"

which points me to a DNS error but nothing has changed, have flushed and registered which did not fix it. I did find that I can telnet to port 25 from external to the server but I cannot telnet from the server through port 25. I have tested telnetting to port 25 from a workstation in the same domain and is ok so it has to be the server. I have turned off the firewall and anti-virus just to test but still nothing. I can however telnet through other ports, just not 25.

any help would be appreciated.
0
Timbobaloba
Asked:
Timbobaloba
  • 5
  • 4
1 Solution
 
Glen KnightCommented:
OK, can you have a look at your Queues do they give an error message?

Turning off firewall and antivirus will not help it must be uninstalled to eliminate this as the problem.
0
 
TimbobalobaAuthor Commented:
error;
451 4.4.0 Primary Target IP Address responded with:"421 4.2.1 Unable to Connect"
0
 
Glen KnightCommented:
"Turning off firewall and antivirus will not help it must be uninstalled to eliminate this as the problem."
Please uninstall your virus software/firewall and restart the server.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
TimbobalobaAuthor Commented:
Anti-virus removed , server rebooted and still unable to send.....
0
 
Glen KnightCommented:
Can you check the properties of your Send Connector under organisation Configuration > Hub Transport.
Are you sending via DNS or Smarthost?
0
 
TimbobalobaAuthor Commented:
DNS
0
 
Glen KnightCommented:
OK.
Can you check that you have a valid rDNS (PTR) record configured.
Also check you have an SPF record.  Goto http://www.microsoft.com/mscorp/safety/content/technologies/senderid/wizard/ and check.

There is also a good FAQ here from EE Expert alanhardisty that may help you identiy where the problem lies: http://www.it-eye.co.uk/faqs/readQuestion.php?qid=2
0
 
TimbobalobaAuthor Commented:
rDNS is correct.
SPF record is good

I feel it has something to do with being unable to telnet from the the server. what would stop this?
0
 
TimbobalobaAuthor Commented:
Fixed. Turned out to be the router!!! was blocking port 25 from just the server. replaced the router and all working fine now!
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now