<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
Paul Wouters wrote:
<blockquote
cite="midPine.LNX.4.44.0406020316430.27241-100000@expansionpack.xtdnet.nl"
type="cite">
<pre wrap="">On Wed, 2 Jun 2004, Magnus Hyllander wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I ran into a problem with Openswan 2.1.2 and Windows XP. In the
oakley.log in Windows XP I get the error message "Peer failed to send
valid machine certificate". Looking for a solution I came across the
following thread on the openswan dev list, which describes my problem
exactly:
<a class="moz-txt-link-freetext"
href="http://lists.openswan.org/pipermail/dev/2004-April/000246.html">http://lists.openswan.org/pipermail/dev/2004-April/000246.html</a>
I tried the suggestion to set "leftsendcert=always", and it does solves
the problem. Just thought I would mention this in case anyone else has
the same problem.
</pre>
</blockquote>
<pre wrap=""><!---->
Did you put the proper certificate in /etc/ipsec.d/cacerts ? Is it loaded
properly? Check with ipsec auto --listall
Paul
</pre>
</blockquote>
Yes, all certificates are correct. My setup is an existing one that I
have used with both SuperFreeswan and Freeswan 2.0x before switching to
Openswan. "leftsendcert=always" was the only change to my existing
configuration that I had to make to get it to work after the switch.<br>
<br>
/Magnus<br>
</body>
</html>