"Error: Connection Closed" frequently when using VPN

[Colin Prime]

I'm frequently getting the following error when my VPN is turned on.

This happens for all websites and happens even when I'm using an Ethernet cable instead of Wifi.

Turning off the VPN seems to get around this, but the VPN should not be causing this in the first place. This started up ever since I renewed my subscription a few weeks ago.

 

System Info

Microsoft Windows 10, Version 22H2 (OS Build 190945.4046)

Kaspersky VPN 21.16.6.467 (c)

[Berny]

@Colin Prime

Please turn on your VPN and ping your ISP DNS Server IP address ?

 

[Colin Prime]

Here's the info I got from the using ipconfig/all in CMD:

 

Unknown adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Kaspersky VPN
   Physical Address. . . . . . . . . :
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 10.102.37.150(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.252
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 198.51.100.1
                                       198.51.100.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

 

Wireless LAN adapter Wi-Fi 2:

   Connection-specific DNS Suffix  . : phub.net.cable.rogers.com
   Description . . . . . . . . . . . : TP-Link Wireless Nano USB Adapter
   Physical Address. . . . . . . . . : 34-E8-94-D6-4A-79
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2607:fea8:c19c:fa00::dcf7(Preferred)
   Lease Obtained. . . . . . . . . . : Thursday, April 4, 2024 11:53:06 AM
   Lease Expires . . . . . . . . . . : Wednesday, April 10, 2024 4:18:54 PM
   IPv6 Address. . . . . . . . . . . : 2607:fea8:c19c:fa00:67cc:8a3c:ed1c:790a(Preferred)
   Temporary IPv6 Address. . . . . . : 2607:fea8:c19c:fa00:1d47:41cf:e6eb:e4aa(Preferred)
   Link-local IPv6 Address . . . . . : fe80::c1f:3a78:d1cf:efb3%12(Preferred)
   IPv4 Address. . . . . . . . . . . : 10.0.0.92(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Tuesday, April 2, 2024 2:53:57 PM
   Lease Expires . . . . . . . . . . : Saturday, April 6, 2024 11:55:49 AM
   Default Gateway . . . . . . . . . : fe80::82d0:4aff:fe6f:797%12
                                       10.0.0.1
   DHCP Server . . . . . . . . . . . : 10.0.0.1
   DHCPv6 IAID . . . . . . . . . . . : 758442132
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-E4-34-2C-28-F1-0E-02-9C-85
   DNS Servers . . . . . . . . . . . : 2001:4860:4860::8888
                                       2001:4860:4860::8844
                                       8.8.8.8
                                       8.8.4.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Edited April 4 by Colin Prime

[Berny]

@Colin Prime

15 minutes ago, Colin Prime said:

 DNS Servers . . . . . . . . . . . : 198.51.100.1

Here is the current ping without Kaspersky VPN  🤔

[Colin Prime]

9 minutes ago, Berny said:

@Colin Prime

Here is the current ping without Kaspersky VPN  🤔

So it's a bad server? Or is the info I provided just wrong?

Edited April 4 by Colin Prime

[Berny]

@Colin Prime

Please try Cloudflare DNS 1.1.1.1 and 1.0.0.1 as secondary ?

[Colin Prime]

3 minutes ago, Berny said:

@Colin Prime

Please try Cloudflare DNS 1.1.1.1 and 1.0.0.1 as secondary ?

Not sure what you mean by that. Do you mean pinging those servers? If so, here is the result.

 

C:\Users\rgrun>ping 1.1.1.1

Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=32ms TTL=58
Reply from 1.1.1.1: bytes=32 time=32ms TTL=58
Reply from 1.1.1.1: bytes=32 time=33ms TTL=58
Reply from 1.1.1.1: bytes=32 time=31ms TTL=58

Ping statistics for 1.1.1.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 33ms, Average = 32ms

 

C:\Users\rgrun>ping 1.0.0.1

Pinging 1.0.0.1 with 32 bytes of data:
Reply from 1.0.0.1: bytes=32 time=33ms TTL=58
Reply from 1.0.0.1: bytes=32 time=40ms TTL=58
Reply from 1.0.0.1: bytes=32 time=31ms TTL=58
Reply from 1.0.0.1: bytes=32 time=34ms TTL=58

Ping statistics for 1.0.0.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 40ms, Average = 34ms

[Berny]

@Colin Prime

Please switch to Cloudflare DNS in your network settings ?

[Schulte]

Please excuse me for interfering here.
'198.51.100.1' and '198.51.100.2' are KSeC's own DNS servers. They cannot be changed at the moment. This is only planned for one of the upcoming versions.

[Berny]

@Schulte Correct 👍

@Colin Prime Please try this ?

• Power off / on router
• Clear Browser cache + reboot
• Flush DNS : CMD → '  ipconfig /flushdns ' + reboot
• Winsock reset : CMD →  ' netsh winsock reset ' + reboot
• Reinstall on-top Kaspersky VPN + reboot

[Colin Prime]

On 4/5/2024 at 3:16 AM, Berny said:

@Schulte Correct 👍

@Colin Prime Please try this ?

• Power off / on router
• Clear Browser cache + reboot
• Flush DNS : CMD → '  ipconfig /flushdns ' + reboot
• Winsock reset : CMD →  ' netsh winsock reset ' + reboot
• Reinstall on-top Kaspersky VPN + reboot

None of the above worked for long. Still getting the issue.

I'm guessing at this point the answer is "Don't try any DIY fix; all you can do is wait for the devs to fix it".