AnsweredAssumed Answered

Service Stopped Responding

Question asked by Michael Clemens on Jul 5, 2019
Latest reply on Jul 9, 2019 by Michael Clemens

During multiple VM scans of one specific Windows host I get the following error:


"Service Stopped Responding - 3 consecutive connection attempts failed after a total number of 61 successful connections."


The port of the affected service is 3269.


Around the time this happened, we have the following logs that might have to do with this issue:


  • The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. Client IP:
  • The following fatal alert was generated: 20. The internal error state is 960. (record_overflow Received a TLSCiphertext record which had a length more than 2^14+2048 bytes, or a record decrypted to a TLSCompressed record with more than 2^14+1024 bytes. This message is always fatal.)


Do you have an idea what the problem might be?