[Vpn-help] cannot connect to a fortigate with shrew vpn client on windows

[Noach Sumner]

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> wrote:

> Hello,
>
> I'm testing a VPN between a fortigate 50A in my office and dialup users.
> I followed carefuly the steps in the wiki:
>
> http://www.shrew.net/support/wiki/HowtoFortigate
>
> 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
> http://lists.shrew.net/mailman/listinfo/vpn-help
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.shrew.net/pipermail/vpn-help/attachments/20081120/6384f4bb/attachment-0001.html>