Issue metadata
Sign in to add a comment
|
Chrome Via VPN Has Become Almost Unusable Recently (Last 2 or 3 Weeks)
Reported by
norc...@gmail.com,
Apr 3 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Connect via VPN (ExpressVPN) 2. Start Chrome 3. What is the expected behavior? Normal DNS resolution via VPN provider DNS servers or ISP DNS Servers or Google Public DNS servers. What went wrong? CHrome is unable to effectively resolve DNS names, particularly at startup. Resolution fails. Did this work before? Yes 56, but I am actually not sure when the 57 upgrade occurred. Therefore it may have worked with 57 as well. Chrome version: 57.x Channel: n/a OS Version: Windows 10 Flash Version: From my original discussion group submission: This only occurs when using Chrome. Edge and even Safari are fine. I've uninstalled and re-installed Chrome and the VPN client multiple times. Firewall rules check out OK, as does my anti-virus program. Chrome sits at resolving host, times out, then may resolve after a while. Sometimes not at all. There are times that once it gets going, it's mostly OK, with intermittent slowness. I've tried using the Google Public DNS servers via my router, computer, network adapter, VPN client as well. Flushed Chrome DNS cache. Also, once Chrome gets stuck, it also creates a bottleneck for any other network traffic from my computer. Trace routes look OK, except once Chrome bogs down, TR's and pings fail. Running Windows 10 with a 1gig internet connection. I've attached at netlog that may add additional context to the issue. Update 4/3: I am beginning to suspect that my AV program is involved in this issue. Kaspersky Internet Security 2017.
,
Apr 6 2017
,
Apr 6 2017
I am convinced at this point that this has something to do with Chrome's interaction with Kaspersky Internet Security. The behavior still only occurs within Chrome. If I temporarily disable KIS, the DNS issue stops. Once KIS is re-enabled the issue re-occurs. Still only in Chrome. All other browsers function normally in either scenario.
,
Apr 7 2017
When I say disable KIS, I mean I literally have to shut the application down. Pausing the protection has no effect.
,
Feb 13 2018
,
Feb 13 2018
Given how stale this bug is, and that it was a weird interaction with antivirus which has probably changed by now, I'm going to close it. I'm very sorry that it didn't get to the right place in a reasonable amount of time! For what it's worth, it looks like when a DNS query is sent for "gc.kis.v2.scr.kaspersky-labs.com", that query and the next several will fail with ERR_NAME_NOT_RESOLVED. I'm not sure why Chrome would be triggering that but not other browsers. This is Windows, so we weren't using our own resolver. If there's still a problem, feel free to file a new bug and link to this one. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Apr 4 2017