Jump to content

cartera

Members
  • Content Count

    2
  • Joined

  • Last visited

About cartera

  • Rank
    Candidate
  1. We have EXACTLY the same issue in exactly the same scenario. Upgraded to the new release and started getting the warning. We have never used encryption and are not licensed to use it. Can you please advise us also what the solution to this issue is. It only occurs for us on the file server version of the package, the workstation version of the program does NOT display the same issue.
  2. I had trouble with all connections to and from my machine only, being blocked on the KSC10 machine. When we disabled the network attack blocker it returned to normal. It now seems that module under KES10 is very sensitive. It logs attacks on port 13111 but doesn't say what IP it was from but it looks to be mine. When I added the local subnet to the exclude list it then blocked everyone so I had to disable the network attack blocker from the server's console. That's OK for when I'm at work but it would be a pain from home.
×
×
  • Create New...

Important Information

We use cookies to make your experience of our websites better. By using and further navigating this website you accept this. Detailed information about the use of cookies on this website is available by clicking on more information.