![]() ![]() If that is normal and would be caused by a legit website visitor (if I had the server configuredĪnd open) or if the "attacker" was doing something unusual to connect, I don't know. ![]() So apparently that's what was causing it. I blocked those two IPs in firewall and that also stopped the "fatal alert" errors appearing in Event Viewer. I ran a third party utility called "TcpLogView" from Nirsoft which shows you connections made to the server ports in real-time, and I saw 2 IPs trying to conect to port 443 at regular intervals of 1 to 2 minutes. ![]() I also have IIS installed on my Windows Server 2008 R2 but am not using it (is not configured). The internal error state is 1203." errors in Event Viewer that repeated every 1 to 2 minutes. I also had the "The following fatal alert was generated: 10. Would be nice to have an official way of troubleshooting this message and getting rid of it properly and not just silence/mute it. "Received an inappropriate message This alert should never be observed in communication between proper implementations. I totally agree on you with this and even microsoft agrees! "The following alert was generated: 10" (fromĮ) means "unexpected_message" and according to the technect article How TLS/SSL Works that means Something is broken, and ignoring this just floods valid errors out of the event log. Sure, an occasional error is no big deal, but we're getting 2-3 of these PER MINUTE. Sorry, no, expected behavior is clients using the CORRECT PORT to access the CORRECT SERVER. I'm getting almost the same error, but it's a 1207, not a 1203, but it just bugs me when people say "oh, that's expected behavior". A fix would be finding out WHAT client is accessing incorrectly and fixing it so the error goes away.
0 Comments
Leave a Reply. |