[Vpn-help] cannot connect to a fortigate with shrew vpn client on windows
Oscar Vidakovic Mercader
oscar at vidakovic.es
Thu Nov 20 04:47:11 CST 2008
The reason I'm running this build is beacase the person who registered
the fortigate is out this week and I cannot contact him. Therefore I'll
try to find a way to update it.
I'm not able to create an internal to internal policy as the VPN is
configured in WAN2.
I got the following policies:
- WAN2 to WAN2 DHCP encrypt
- internal to WAN2 all encript
Is something wrong?
thank you very much
Noach Sumner escribió:
> I don't remember which build sat where but there were a good number of
> builds where Fortigate had completely broken the VPN connectivity. But
> I wonder if you have a policy from internal to internal with service
> set to DHCP and policy set to encrypt? BTW is there a reason you are
> running the old build? MR5 is on P6 I believe and MR7 is on P1 and P2
> is around the corner (actually 4MR1 is supposed to be out before the
> end of the year).
> BTW, Matthew have you had a chance to look at the multiple IP issue yet?
> On Wed, Nov 19, 2008 at 5:15 PM, Oscar Vidakovic Mercader
> <oscar at vidakovic.es <mailto:oscar at vidakovic.es>> wrote:
> I'm testing a VPN between a fortigate 50A in my office and dialup
> I followed carefuly the steps in the wiki:
> once the VPN is connected the client ask for an IP and the Fortigate
> sends it, so the client does not receive it. client answer is no dhcp
> response from the gateway.
> Can anyone help me?
> My fortigate firmware version is 3.00-b0568(MR5 Patch 3)
> the shew client version is 2.1.4
> Tested in windows xp sp2
> Thank you very much in advance
> vpn-help mailing list
> vpn-help at lists.shrew.net <mailto:vpn-help at lists.shrew.net>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vpn-help