Thanks for the report! It looks like Chrome is seeing connections to that site get reset for some reason. The IP address Chrome is resolving is the same as the one I'm seeing locally, so that's not what's going on. The resets are happening not instantly, but consistently with a somewhat lower RTT than the probing fallback connection.

Is this a corporate network? Do you have some kind of firewall or other network software? I'm wondering if it's misconfigured in some way. (Strangely, you seem to connect to Google properties fine. I would normally have expected firewall problems to apply to everything.)

Copying from the product forums:
"""
Our IT guy is confused as well. All other computers in the office can access qbo.intuit.com accept mine. He checked the router to make sure all the settings were the same as the other pcs that are working fine. But we discovered if we plugged the pc that is having the problem directly into the modem we get no internet. We can only get internet if we connect the pc to the router first. All the other pcs in the office will get internet if plugged into the modem directly bypassing the router. So we're assuming the problem exists in the pc. Our IT guy thinks he's looked at everything and still can't find the problem. It's weird that we can't get to the site on firefox or chrome but IE works fine. This started on May 1st. We were wondering if it's possibly some sort of update that took place on the 1st of the month. None of the other pc's have been update since the 1st but the one having the problem has. As you can probably tell I'm no computer guy. We're just trying to troubleshoot the best we can.
"""
https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!msg/chrome/boVqIAs7sDI/4BLVUW65BQAJ

[I've asked the reporter to continue the discussion here so we don't get things jumbled.]

Both Firefox and the latest version of Chrome don't work around this particular bug anymore for security reasons, so that's probably why you're seeing it only on those two browsers.

Hrm. What kind of router is it? I wonder if it has some bugged up filtering thing. Do other machines in the office have the same setup (same kind of router and modem), or do they do something else?

The router is a Linksys WRT AC1900. All other pc's in the office are connected to the same router as well.

Oh okay, just a normal old router. :-)

I suspected it was something not quite local to the PC since the resets were coming back after a delay, but looking at what you said earlier:

> All the other pcs in the office will get internet if plugged into the modem directly bypassing the router. So we're assuming the problem exists in the pc.

I agree that's a little funny. Do you have perhaps some antivirus or firewall software on the machine? What kind? They've caused problems like this before, though I've never heard of a 1.2-intolerant one. I don't see any evidence of one of those and the delay is fishy, but maybe it's really slow or something.

Another thing that might be worth checking on is if you go to about:conflicts and send me that page. Sometimes this kind of software likes to hook into Chrome directly and that page would show if something's doing that.

We need to make that export something more useful. In the meantime, probably the easiest is to print to a PDF: Three lines menu -> Print... -> change the printer to "Save as PDF".

(Just to make sure, the other PCs are also running Chrome 50 (go to about:version)? That's the release where we stopped working around the version fallback. Firefox also stopped some time ago.)

The standard windows firewall is on this pc but we disabled it to see if that work and it still didn't. We also ESET NOD32 for antivirus. We tried disabling the antivirus with the same results. The other pc's are running version 50.0.2661.94 m (64-bit). Attached are the results from about:conflicts.

Deleted: ChromeConflicts.pdf 1.3 MB

ChromeConflicts.pdf 1.3 MB Download

Hrm. Nothing there looks especially weird beyond ESET (which is on the other PCs, right?) and QBVersionTool.

I actually wouldn't past it for QBVersionTool to have injected something that messes with their site and only their site. And the product forums are showing someone else with the same problem, which makes me think it'd be reasonably common for QuickBooks users.

But this page implies QBVersionTool doesn't really do much. It is "the little bit that gets added to the Windows Explorer that shows you what the last version to open the file was" which really really should not be touching the network.

https://community.intuit.com/articles/1342125-windows-explorer-has-encountered-a-problem-and-needs-to-close-when-you-rename-a-company-data-file

What does about:conflicts show on one of the other PCs on your network here it does work? (Sorry I keep asking for random things. I'm grasping at straws and hoping one of them is connected to something.)

The other PC that is working is running ESET but an earlier version. Attached is the about:conflicts results. The article on the intuit site is for the Quickbooks desktop version. We switched over to Quickbooks online on January 1st. 

Deleted: chrome___conflicts.pdf 124 KB

chrome___conflicts.pdf 124 KB Download

Hrm. Well, you seem to have a remnant of the desktop version installed, and it doesn't appear to be in the other one. If you're not using it anymore, would you be willing to try uninstalling it and then restarting Chrome? (QBVersionTool should no longer appear in about:conflicts.)

Then we can rule out the (somewhat confusing) qbversiontool.dll theory.

Thank you for providing more feedback. Adding requester "davidben@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hi David,
Unfortunately, we still use the desktop version on occasion. 

Good news! I got another report with the same issue and I suspect I know what's up. ESET's SSL filtering feature is probably causing problems.

I haven't heard back from the other reporter yet on whether this works, but if you *disable* ESET SSL protocol scanning, are things resolved? (You may need to restart the browser or something.)

There are instructions here. Scroll down to the bit that says "Disable SSL protocol scanning".
http://support.eset.com/kb3126/?locale=en_US

If that resolves it, I'll try to find contacts at ESET to get them to fix their bug. These kinds of features tend to cause problems a lot. :-/

Yes, it worked! You're a genius and a lifesaver! Thank you so so much for working so hard on this even though it wasn't a Chrome issue. Now I can have my Chrome back.

Thanks again,
Dan

Great, thanks for the confirmation! I'll go ahead and close this then. Now to see if we have any contacts at ESET so they can fix their code.

(For your part, antivirus' SSL scanning features constantly cause problems and keeping it disabled is probably a good plan. But I'm sure there are other ESET users out there who won't know to do that.)