<div dir="ltr">Seems to work now. Thanks.<br><br>Ethernet adapter Local Area Connection* 9:<br><br> Connection-specific DNS Suffix . : nbn.lan<br> Description . . . . . . . . . . . : Shrew Soft Virtual Adapter<br> Physical Address. . . . . . . . . : AA-AA-AA-AC-BE-00<br>
DHCP Enabled. . . . . . . . . . . : No<br> Autoconfiguration Enabled . . . . : Yes<br> Link-local IPv6 Address . . . . . : fe80::bd75:683a:f321:5742%37(Preferred)<br> IPv4 Address. . . . . . . . . . . : 192.168.48.13(Preferred)<br>
Subnet Mask . . . . . . . . . . . : 255.255.255.0<br> Default Gateway . . . . . . . . . :<br> DHCPv6 IAID . . . . . . . . . . . : 631941802<br> DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-7B-D3-E5-00-1E-4F-A9-9A-C1<br>
<br> DNS Servers . . . . . . . . . . . : 172.16.10.10<br> 172.16.10.11<br> NetBIOS over Tcpip. . . . . . . . : Disabled<br><br><br><div class="gmail_quote">On Mon, Dec 20, 2010 at 6:44 AM, Matthew Grooms <span dir="ltr"><<a href="mailto:mgrooms@shrew.net">mgrooms@shrew.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div class="h5">On 12/16/2010 12:36 AM, Matthew Grooms wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
On 12/15/2010 11:10 PM, Noach Sumner wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Okay, I tested on 2 more computers (all are Windows 7 but 2 were 32 bit<br>
and 1 is 64). The results are reproducible... I am connecting to a<br>
Fortigate unit and have tried connecting to 2 different Fortigate units<br>
with the same results. I can ping things on the remote side if I know<br>
the IP, I can do an nslookup since I know the IP of the DNS server but<br>
all in all things are pretty bleak. I am also getting disconnected from<br>
the key daemon regularly and it doesn't work again without restarting my<br>
computer (probably I could just restart some services I admit).<br>
<br>
Okay indeed if I restart the Shrew IKE Daemon things work again (the<br>
service was no longer running BTW). I pulled this out of the event log.<br>
<br>
</blockquote>
<br>
Right. That doesn't look good. I would fall back to 2.1.7 and give me a<br>
few days to try and reproduce some of these issues. I'm guessing some of<br>
the DHCP over IPsec code got out of sync between the two versions. I<br>
placed this on my todo list and will get back with you once I think I<br>
have things in order.<br>
<br>
</blockquote>
<br></div></div>
Noach,<br>
<br>
Please give this a try and let me know if the issue is resolved.<br>
<br>
<a href="http://www.shrew.net/download/vpn/vpn-client-2.2.0-dhcpfix-1.exe" target="_blank">http://www.shrew.net/download/vpn/vpn-client-2.2.0-dhcpfix-1.exe</a><br>
<br>
Thanks again for testing,<br><font color="#888888">
<br>
-Matthew<br>
</font></blockquote></div><br></div>