What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general.

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
More than 500,000 users rely on Paessler PRTG every day. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

What do these messages mean?

Votes:

0

On the Overview tab, under Network Infrastructure, DNS/Gateway/DHCP: 10.0.0.1, I get two messages for each of ports 465, 993, and 995. I don't know what they mean or what, if anything, should be done about them:

"Failed to establish secure connection [Step 0] Socket Error # 10054 Connection reset by peer. [Step 1] Socket Error # 10054 Connection reset by peer. [Step 2] Socket Error # 10054 Connection reset by peer. [Step 3] Socket Error # 10054 Connection reset by peer. [Step 4] Socket Error # 10054 Connection reset by peer."
"Error by lookup value 'No Secure Protocol Available' in Security Rating"

error-#-10054 error-messages secure-protocol

Created on Sep 13, 2016 12:40:29 PM

Last change on Sep 14, 2016 12:02:21 PM by Luciano Lingnau [Paessler]



12 Replies

Votes:

0

Dear Rick

When the sensor tries to connect, it uses the most secure connection protocol available. If no connection is possible, the next best protocol is used. The error message shows that none of the supported protocols (via TLS, SSL) were accepted by the device.

Created on Sep 14, 2016 11:07:42 AM by Arne Seifert [Paessler Support]



Votes:

0

Thanks. What would cause this problem?

Created on Sep 14, 2016 11:45:23 AM



Votes:

0

Since the TCP connection was actively closed ("Socket Error # 10054 Connection reset by peer") it looks like being caused by the firewall configuration, the wrong ports used, or possibly flood protection.

Created on Sep 14, 2016 12:47:28 PM by Arne Seifert [Paessler Support]

Last change on Sep 14, 2016 12:48:00 PM by Arne Seifert [Paessler Support]



Votes:

0

Thanks. Is this something that should be fixed? If so, how?

Created on Sep 14, 2016 8:51:46 PM



Votes:

0

If you want to monitor those DHCP ports, they must be open and the firewall must allow PRTG to access them. If you don't need these ports monitored, you can delete or pause the sensors in question.

Created on Sep 15, 2016 11:17:21 AM by Arne Seifert [Paessler Support]



Votes:

0

Thanks!

Created on Sep 15, 2016 12:33:58 PM



Votes:

0

I'm still having trouble with this. I'm over my head, but I'm hoping you can help. I checked Inbound Rules in Windows Firewall and all four PRTG listings show "Any" under both Local Port and Remote Port. What else should I check? Thanks.

Created on Sep 18, 2016 7:26:38 PM



Votes:

0

Dear Rick

In this case please check the log of the DHCP if you can find any connection related messages. For example it could be the case that a flood protection applies.

Created on Sep 19, 2016 11:26:32 AM by Arne Seifert [Paessler Support]



Votes:

0

Thanks. Where do I find the log of the DHCP?

Created on Sep 19, 2016 12:31:25 PM



Votes:

0

Dear Rick

This depends. Please contact the admin responsible for this DHCP server.

Created on Sep 19, 2016 12:42:46 PM by Arne Seifert [Paessler Support]



Votes:

0

I don't have an admin or a server. This is a home network with a WiFi router.

Created on Sep 19, 2016 1:27:33 PM



Votes:

0

Dear Rick

In this case, I don't think this sensor provides useful information unless there is a reason to specifically monitor these ports.

Created on Sep 19, 2016 1:48:31 PM by Arne Seifert [Paessler Support]




Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.