![]() ![]() Ike 0:dialup_p1:46: type=AUTH_METHOD, val=PRESHARED_KEY. Ike 0:dialup_p1:46: type=OAKLEY_HASH_ALG, val=SHA. Ike 0:dialup_p1:46: type=OAKLEY_ENCRYPT_ALG, val=3DES_CBC. Ike 0:dialup_p1:46: encapsulation = IKE/none Ike 0:dialup_p1:46: protocol id = ISAKMP: Ike 0:dialup_p1:46: responder: main mode get 1st message. Here is teh diagnose debug application log from our connection if it helps anyone point out the fault? We have tried connecting from Win 7 and XP with the same result. We are using a Fortigate 60C and having EXACTLY the same issue, with teh exception of IP addressing out setup is identical and the errors and logs to identical. ![]() ![]() Is the prblem rather on the fortinet side or on the client side? The fortinet vpn client is a bit short-spoken on how to set up he windows native vpn client, this is what i did: The Fortinet Eventlog doesn' t report an error while setting up Phase 1 and 2. From a Windows 7 Client i get the same result. I tried connecting from a windows 2008 server, but while connecting, the windows vpn client returns a error 789. Configure Firewall policies (see attached image) Configure Phase1 and 2 via Gui (see attached image)ĥ. Setup a Usergroup " VPN-Nutzer" in the GUI and associate one Testuser with this groupĤ. I used the IPsec VPN Guide for setup: (p. Here are the Details:įortinet 50B: Firmware: v4.0,build0313,110301 (MR2 Patch 4) I' m trying to set up a L2TP-over-IPsec VPN on a 50B.and it won' t work. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |