<html><body bgcolor="#FFFFFF"><div>You would typically need to forward UDP port 500, UDP port 4500 and IP protocol ESP. You probably missed 4500 which is used for NAT-T. <br><br>-Matthew</div><div><br>On Jul 24, 2010, at 9:32 AM, <a href="mailto:mikelupo@aol.com">mikelupo@aol.com</a> wrote:<br><br></div><div></div><blockquote type="cite"><div><font color="black" size="2" face="arial">
<div>Matthew,</div>
<div>After some more investigating, we placed that laptop running Shrew in the DMZ and it worked great. So I think it's a matter of proper port forwarding/port triggering settings.</div>
<div>Can you offer any advice to this?</div>
<div> </div>
<div>Thanks,</div>
<div>Mike</div>
<div> </div>
<div><br>
<br>
</div>
<div style="CLEAR: both"></div>
<br>
<br>
<div style="FONT-SIZE: 10pt; COLOR: black; FONT-FAMILY: arial,helvetica">-----Original Message-----<br>
From: Matthew Grooms <<a href="mailto:mgrooms@shrew.net">mgrooms@shrew.net</a>><br>
To: <a href="mailto:mikelupo@aol.com"><a href="mailto:mikelupo@aol.com">mikelupo@aol.com</a></a><br>
Cc: <a href="mailto:vpn-help@lists.shrew.net"><a href="mailto:vpn-help@lists.shrew.net">vpn-help@lists.shrew.net</a></a><br>
Sent: Fri, Jul 16, 2010 12:43 pm<br>
Subject: Re: [vpn-help] Problem with Shrew client via Linksys WRT45g gateway<br>
<br>
<div id="AOLMsgPart_0_681fa878-0670-4109-8b36-080d44b89482" style="FONT-SIZE: 12px; MARGIN: 0px; COLOR: #000; FONT-FAMILY: Tahoma, Verdana, Arial, Sans-Serif; BACKGROUND-COLOR: #fff">On 7/15/2010 11:56 AM, <a href="mailto:mikelupo@aol.com"><a href="mailto:mikelupo@aol.com">mikelupo@aol.com</a></a> wrote: <br>
> I have a shrew VPN client up and running on a Windows 7 professional <br>
> (laptop). With the laptop at home, going through my netgear router, I <br>
> have no problem starting and using the VPN connection reliably. Once the <br>
> connection is made I can ping workstations inside the remote secure LAN. <br>
> The world is good. <br>
> However, now that the laptop has been deployed to the employee for whom <br>
> I built if for, we cannot seem to get the same result. <br>
> Attached is a doc file containing screenshot of the VPN trace utility. <br>
> It appears that we're getting through Phase 1 and Phase 2 reliably. On <br>
> the linksys WRT54G, We've also opened up Port 500 for forwarding and <br>
> triggering just to be safe. <br>
> Remote secure network LAN address 192.168.1.x <br>
> DHCP address given by VPN to shreew client 192.168.2.50 <br>
> Local IP of the laptop sitting in the home/office of employee 10.0.0.4 <br>
> Matthew, do you have any words of wisdom? Whereas this was working <br>
> before on my home network, I don't want to rush to change client <br>
> software versions. The laptop is 120 miles away and talking the employee <br>
> through this isn't going to be easy. <br>
<br>
Mike, <br>
<br>
Its hard to tell whats going on without seeing the debug log output. My guess is that the phase2 negotiation is failing for some reason. What version of the client did your user install? <br>
<br>
-Matthew <br>
</div>
<!-- end of AOLMsgPart_0_681fa878-0670-4109-8b36-080d44b89482 --></div>
</font>
</div></blockquote></body></html>