<div dir="ltr">The "right way" (from a security standpoint) to do this is to use different certificates on each machine. Only if both clients use the same cert should you get a duplicate CN issue.<br><br>David<br>
<br><br><div class="gmail_quote">2008/10/16 Pat Regan <span dir="ltr"><<a href="mailto:thehead@patshead.com">thehead@patshead.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Chris Fowler wrote:<br>
> Here is one I'm not sure what is going on.<br>
<br>
</div>What do the logs say? On both sides?<br>
<br>
There are a few options that have to match on both the client and the<br>
server or you'll never connect. Most of those settings relate to<br>
mtu/mss and fragmentation, though. Can you post the client config as well?<br>
<font color="#888888"><br>
Pat<br>
<br>
</font><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
<br></blockquote></div><br></div>