So, I went to the FortiClient VPN download page and downloaded their automatic updater. It doesn't even say when it performed its last update check.
It said "latest version", but for all I know it's been saying that for months. (-5) Checking FortiClient VPN for Updatesīefore uninstalling Windows security updates, I checked to make sure I had the latest version of the FortiClient VPN client utility. The server you want to connect to requests identification, please choose a certificate and try again. If kernel debugger is available get stack backtrace.I got the following warning message when trying to connect to one of my clients via the FortiClient VPN: Warning This is usually caused by drivers using improper addresses. Some snippets:Īn attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high.
The UI feels sluggish, I have two saved connections that if I open them to edit settings all of the settings fields are blanked out.įinally, if there's any interest in the BSOD info, I ran a WinDbg on the memory dump. On a side note - aside from the BSODs the client is pretty bad in general. But if the FortiClient VPN client is the only compatible one, I guess I'll have to live with it, unless there is some alternative compatible 3rd party VPN client out there? So I'm wondering - should I be able to connect to my VPN without the FortiClient software in the first place? If it is possible, I can pursue with my network admin on what might be happening. The error code returned on failure is 789." but I don't find any further details about what the problem might be. But it doesn't connect and Event Viewer reports "user has dialsed a connection which has failed. I thought maybe using the native Windows 10 VPN client would be more stable so I created a new VPN connection, entered my gateway in as the server name, selected "L2TP/IPsec with pre-shared key" and entered my key, and tried to connect. In the FortiClient VPN setup, my connection is "IPsec VPN" with a remote gateway, pre-shared key, and the rest is defaults. The BSODs seem to happen most often if I've changed connections, when I go to reconnect the VPN the entire system will crash. I'm mainly connected to a dock with ethernet, sometimes I'll connect via wifi. This version, as with every other 6.x version I've tried of the FortiClient VPN software keeps giving me intermittent BSODs pointing to "fortips.sys". I am currently connecting to a corporate VPN using the FortiClient VPN v6.
0 kommentar(er)
