<html><head></head><body>Hi Kevin and everyone else watching this, <br>
<br>
I'll try to answer the simple questions first and will grab a copy of configuration file and logs tomorrow morning. (it's 3am here) <br>
<br>
The error message appears inside the vpn trace utility on the client. <br>
As far as xauth goes, I know that we have no individual user authentication via xauth. Pushing IP configuration via xauth is a feature I've not heard of yet, but I'll investigate that part if that's possible independent of authentication via xauth. <br>
-- <br>
Gruß,<br>
Benedikt Bauer<br><br><div class="gmail_quote"><br>
<br>
Kevin VPN <kvpn@live.com> schrieb:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif">On 05/14/2012 08:25 PM, Benedikt Bauer wrote:<br />> Hello everyone,<br />><br />> I've got a strange problem/situation I don't understand.<br />> IKE Phase 1 is established successfully, but my Phase 2 is rejected<br />> because no matching inbound policy can be found.<br />> The connection general tab is set to use a virtual adapter and when the<br />> adapter should automatically assign an IP address the VPN Client doesn't<br />> seem to set the correct security policies itself.<br />><br />> Remote LAN is <a href="http://192.168.0.0/24">192.168.0.0/24</a>, local LAN is <a href="http://192.168.99.0/27">192.168.99.0/27</a><br />> The VPN Client always trys to assign <a href="http://192.168.99.16">192.168.99.16</a> to the virtual adapter.<br />><br />> If I assign anything but <a href="http://192.168.99.16/32">192.168.99.16/32</a> to the virtual adapter I!
KE<br
/>> Phase 2 fails.<br />><br />> I've got another 2 computers with The Greenbow VPN Client that work fine<br />> and both of them have not assigned any static IP address to their<br />> virtual adapter. (VPN Client Address: 0.0.0.0)<br />> Can anyone explain to me why that doesn't work with automatically<br />> assigned IPs instead of static IP?<br />><br /><br />Hi Benedikt,<br /><br />I would guess that you've somehow got the Shrew configuration setup <br />incorrectly, but that is just a guess. The fail message about "no <br />matching inbound policy can be found" - is that shown on the Shrew <br />client or the VPN gateway logs?<br /><br />Do you use XAUTH on the gateway to push the IP configuration to the <br />client - if so, have you configured Shrew to expect XAuth (under <br />Authentication tab -> Authentication Method)?<br /><br />Are you able to send us a copy of your Connection configuration as well <br />as a log file so we can help !
sort
this out? Instructions for generating <br />the log file are here:<br /><a href="http://www.shrew.net/support/wiki/BugReportVpnWindows">http://www.shrew.net/support/wiki/BugReportVpnWindows</a><br /><br /><hr /><br />vpn-help mailing list<br />vpn-help@lists.shrew.net<br /><a href="http://lists.shrew.net/mailman/listinfo/vpn-help">http://lists.shrew.net/mailman/listinfo/vpn-help</a><br /></pre></blockquote></div></body></html>