Article Rating (143 Votes)
Rate this article
Home » Categories » PingPlotter » Alerts

Socket error 10053 when testing email alerts

Question

I'm getting this error whenever I test an email alert: 'Socket error 10053 - Software caused connection abort'. What's causing this?

Solution

The 10053 error happens when PingPlotter or MultiPing is having problems talking to the SMTP server (this is a standard Winsock error). Specifically, this happens when a connection is properly initiated, but then something abruptly ends the conversation.

Usually, this is because of some kind of firewall running between you and the SMTP server (maybe on your local machine, or someplace between you and the SMTP server). It can also be because of a SMTP server problem of some kind.

If you're running McAfee Anti-Virus 8.0i, make sure PingPlotter (pingplotter.exe) or MultiPing (multiping.exe) is an allowed program.

If you're using any kind of SMTP proxy (Norton Antivirus is one of these that proxies SMTP to make sure you don't send out any viruses), then check to see if you can work around that somehow.

Also, check to see if one of your SMTP servers will allow incoming connections on a non-standard port and try using that port instead of the standard port 25.

Attachments Attachments
There are no attachments for this article.
Related Articles
Socket error 10060 when testing an alert
Viewed 26448 times since Wed, Apr 27, 2005
Alerting on multiple targets / best practices.
Viewed 1516 times since Mon, Jul 6, 2009
Socket error 11004 when testing an alert
Viewed 15456 times since Fri, Jun 10, 2005
Generating an SNMP Trap from PingPlotter or MultiPing
Viewed 9752 times since Tue, Aug 24, 2004
E-mail us