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

Socket error 10054 when testing email alerts.

Question

I'm getting this error whenever I test an email alert: 'Socket error 10054 - connection reset by peer'. What's causing this?

Solution

This error happens when a connection is started (and working), but then closed by the other side of things before the SMTP conversation is completed. This can also be caused by a firewall in between you and the server that might be 'proxying' the SMTP conversation, and then terminates it.

There are several common reasons:

  • The wrong SMTP server was specified (Edit -> Options, Email). Check your email client to see what it's using for an SMTP server, or talk to your system administratory.
  • There is a firewall or antivirus package running that's aborting the SMTP conversation. This might be something running on your machine (like Norton Antivirus), or some hardware firewall that does stateful inspection. If other software works, but PingPlotter/MultiPing does not, then it's probably local to your machine - something that is filtering by which application is sending data.
  • There might be something wrong with the SMTP server. Try using another email client and make sure the same SMTP server works with that.
Attachments Attachments
There are no attachments for this article.
Related Articles
Alerting on multiple targets / best practices.
Viewed 1517 times since Mon, Jul 6, 2009
Generating an SNMP Trap from PingPlotter or MultiPing
Viewed 9753 times since Tue, Aug 24, 2004
Error "Parameters not configured for email alerts".
Viewed 1599 times since Sat, Dec 15, 2007
Alert email data problems
Viewed 2887 times since Wed, Oct 15, 2003
E-mail us