Forum Discussion
This site can’t be reached The connection was reset error message.
I have come across one website I cannot reach. It is https://www.treasurydirect.gov The error message happens with a PC connected directly to the modem (HT2000W) on Internet Explorer, Chrome and...
Works fine here, took ages to connect, but it worked, you may want to try disabling Web Acceleration to see if that helps.
Please follow the directions below to disable Web-Acceleration.
1: Visit http://192.168.0.1 in your web-browser.
2: Click the "i" icon at the top of the HT1100/2000w System Control Center (also known as the SCC). It is highlighted in red in the image below.
3: Click on "Web Acceleration" then "Control" outlined in red.
4: Click on "Web Acceleration Enabled", this will change to an orange button that says "Web Acceleration Disabled".
5: Restart your browser and try using the service that isn't working, please let us know how that works for you.
Last week I called tech support and got the usual run around without relolving the issue, a case number was assigned and would be forwarded to engineering and I would get a call back in 48 hours. Needless to say, I haven't heard a thing. A friend who also has Gen 5 and uses a laptop running Windows 7 has been able to access the treasury direct web site (he doesn't have an account so can't log on). Since I have logged on to the site last year using my Windows 10 Desktop, I am not sure just what this means.
I called to day to try and get through to Tech Support / Engineering but got a mesasage that there was some sort of major repair effort underway and no one was available - call back later!!!
Today (01/19/2018) I am able to get to TreasuryDirect; it didn't work yesterday, I think. FYI:Several days earlier I tried the unplugging the router trick and the site worked for a while, but only on the computer that was logged on when I did it. I had turned off acceleration before I did it but when plugged back in it reverted to acceleration on, but the treasury site worked properly. So the acceleration is probably not the problem and it needs to be fixed at the network level. Maybe it has been fixed now?
