Jump to content

LUSO

Members
  • Posts

    152
  • Joined

  • Last visited

Posts posted by LUSO

  1. If it's a Firewall/Security Suite setting

     

    It sounds like you have a Firewall rule set for DCS.exe,

    but the Firewall software is only applying it to the DCS.exe on the E:/Drive.

     

    Add a 2nd rule or modify the current rule for DCS.exe on the C:\ Drive.

     

     

    Thank you to you, but I chose another solution, after to have had failures.

     

    I updated the Open Beta, the same level of my main installation.

  2. I was talking about before Beta Update 1.2.8 made​​, but which remains on my system two separate Installation.

     

    Saying that I tested the beta is not updated yet, I go and I see the available servers.

     

    If what you say is true, I have never yet made ​​rules separately for both front and all facilities worked.

  3. It would be very helpful if anyone with the error, will try to gather some windows event log records about failed login attempts. It requires some moderate technical skills: You will have to temporarily increase SChannel logging level on your system: http://ipswitchft.force.com/kb/articles/FAQ/How-do-I-gather-more-debugging-on-SSL-errors-such-as-SSL-handshake-failed-1307565984914

    After doing this, try to login and then take a look into windows system event log for "schannel"-related errors.

     

    We still can't reproduce the bug on systems which are available to us, so your help will be greatly appreciated.

     

     

    I think doing what you ask, here's a file in XML result:

     

    https://dl.dropboxusercontent.com/u/55220861/Schannel%20(1).xml

     

    Tell us if this is it.

     

    Windows 8.1/64bits, Windows Defender.

×
×
  • Create New...