If there is content being sent to a port that is using our UPA protocols, the content should also be using UPA’s protocols. Anything that would cause one of the sockets to believe there is I/O activity will result in triggering the application to read or accept (and the OS to read the bytes that triggered the notification (regardless of what they came from). When these are processed and interpreted by UPA, it does not recognize them so it throws them away and returns an error because an error has occurred.

This is similar for any protocol built on a socket connection. If you send random byte streams to an FTP server, it will also report similar errors as it will not recognize the FTP protocol it is expecting on that socket.

The transports are built to leverage its optimized protocols, and if components are attempting to send other formatted content (telnet, load balancer, etc) to these sockets, these rogue components should be reconfigured or be disabled.