On Fri, Nov 7, 2014 at 1:57 PM, Niels Peen <niels at peen.ch> wrote: >> The cases that this can happen is when there are no commonly supported >> protocols, or the peer doesn't correctly set the TLS record versions. >> That's almost impossible to occur between two gnutls peers. Could that >> again be related to a firewall that modifies the packets sent/received? > Possible. The user turned off their firewall (ESET), but I'm not convinced > that turning it off completely restores normal behaviour. You mean he still cannot connect even after turning it off? If he gets the same error, could he be in a corporate firewall that tries to perform man-in-the-middle? Having a wireshark transcript of his sessions would help identify the issue. regards, Nikos
