17 Jan
2012
17 Jan
'12
8:18 a.m.
On Tue, Jan 17, 2012 at 7:18 PM, Alberto Martínez <alberto_martinez@deusto.es> wrote:
The problem is ALWAYS the same. The Wiki page describes the problems, and the solutions.
That particular error is known to pop out when a Windows client uses a misconfigured certificate, or the MTU is too high. This case is neither one nor the other.
So just to confirm, you're using the SAME server certificate on BOTH server, which you generate manually, and NOT using the one automatically-created when you install the package (e.g. rpm, deb), right? -- Fajar