I suspect the problem has something to do with how the RV340 is storing and fetching the preshared-key value. We had similar problems trying to get the Windows 10 built-in VPN client using "L2TP/IPSec with pre-shared key." It won't work, either! We did manage to get the built-in Mac OSX client to connect using Cisco IPSec, but we'd like to have the L2TP option working and available. It seems to get close, but then complains of "Authentication Failure." We're absolutely sure we have the user credentials and the preshared-key correct, but we cannot get the built-in Mac OSX VPN client to connect to our RV340 with L2TP. The VPN successfully connects but then gets disconnected for an error I cannot decipher.Has anyone successfully gotten the built-in Mac OSX VPN client to connect to an RV340 using L2TP/IPSec? We have tried virtually every combination of settings we can think of, but it simply doesn't work. 20210817 11:37:55 ConfigManager.swift:1522 Config file "/Library/Application Support/Fortinet/FortiClient/conf/ist" not existÄ¢0210817 11:37:55 VpnManager.swift:611 VPN connecting sslConnGotoNextState:307 error (last state: 1, closeOp: 0)Äestroy sconn 0x7f9fc8e300, connSize=0. Sslvpn_reserve_dynip:1156 tunnel vd ip app session idx SSL established: TLSv1.3 TLS_AES_256_GCM_SHA384 SSL state:SSLv3/TLS write session ticket (49.178.7.112) SSL state:TLSv1.3 write server certificate verify (49.178.7.112) SSL state:TLSv1.3 write encrypted extensions (49.178.7.112) It connects but then for reasons unknown gets disconnected. The correct user/pass generates no messages. Also, putting in fake login details generates an client error for the wrong user/pass. the VPN actually connects and authenticates. MacOS does not! The VPN shows "Connecting" and then simply goes back to no message. I have a 100F device (6.2.8) setup for SSL VPN for remote connections using the VPN-only forticlient.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |