Hi miknyb,

I'm afraid we're out of things to try at this point. The issue is either a misconfiguration between your client and server, or an environmental issue like a firewall/AV or some other software tampering with the packets, or as original mentioned a routing issue.

Regards,
Eric

Hi Rieder,

Yes it is. Simply set the option and copy it out of Settings.xml in %appdata%\Viscosity like any other setting. The setting is called "BlockIPv6" in the xml.

Regards,
Eric

Hi miknyb,

ncp-disable needs to be set on the server.

Regards,
Eric

Hi miknyb, I've just noticed that your original reply configurations includes the following cipher: cipher AES-256-CBC However the connection is using: jan 07 9:41:40 : Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key jan 07 9:41:40 : Incoming Data Channel: Cipher 'AES-256-GC...

Hi Greg, A bluescreen shouldn't be causing a shutdown unless you have that option specifically selected in Windows, which most likely means the bluescreen is causing the driver to crash rather than the driver causing the bluescreen, however we would like to take a look anyway. Please email us the mi...

Hi Mikael,

It is possible, though unlikely. It is more likely to be one of the issues mentioned in my original reply.

Regards,
Eric

Hi Mikael, Two things stick out: 1. Npcap is known to interfere with VPN connections if not configured correctly. Please try uninstalling it, cold booting your PC, and seeing if the problem persists. 2. One of your vEthernet switches appears to be misconfigured. What is interesting is when Viscosity...

Hi Mikael,

Could you please post a copy of your route table and ipconfig -all after connecting as well?

To do this, open a command prompt and type in the following commands one after another:
route print
ipconfig -all

Regards,
Eric

Hi HelplessRube, I'm running the 21277 prerelease build with 64 bit emulation, so not sure if that would throw a further wrench into the works here as to path being referenced. I'm afraid it does. In this case, it should be looking in C:\Program Files\Common Files, rather than x86 on the current rel...

Hi HelplessRube, All that should be required is the AllowOpenVPNScripts setting to be set. We've just run through a test on ARM64. The only change that was nessecary, which we will update the documentation and Viscosity in the next beta to reflect in messages, is using "Program Files (x86)"...