Re: Cannot access w3schools.com

JohnGeddes · ‎31-07-2017

Uniquely among websites, I cannot access pages at w3schools.com - pages come back with "ERR_CONNECTION_TIMED_OUT" (not just today - it's been happening for at least a couple of weeks). I can't even ping their numeric IP (66.29.212.110: confirmed using Google DNS) - it times out.

External site checkers say the site is OK, and I can access it via a Proxy (eg proxysite.com). But not otherwise.

Ideas?

VileReynard · ‎31-07-2017

Try www.w3schools.com

:crazy3:

"In The Beginning Was The Word, And The Word Was Aardvark."

Anonymous · ‎31-07-2017

Hello and Welcome to the Forums. It may be of no help to you @JohnGeddes but I can access this site, I wonder what others are experiencing?

https://www.w3schools.com/

JohnGeddes · ‎31-07-2017

Same problem with www.w3schools.com, I'm afraid.

Anonymous · ‎31-07-2017

You can't ping it because it doesn't respond to pings.

Mustrum · ‎31-07-2017

The links work fine for me.

Pete11 · ‎31-07-2017

Links work fine here too.

A float tip is pleasing in its appearance and even more pleasing in its disappearance.
Growing old is inevitable...But growing up is optional.

alanf · ‎31-07-2017

Works for me too.

I use http://downforeveryoneorjustme.com to check if a site is available to others.

JohnGeddes · ‎31-07-2017

"I use http://downforeveryoneorjustme.com to check if a site is available to others." - Yes, I had confirmed that the site was up before posting.

The multiple confirmations that other Plusnet users are OK reaching the site puts paid to my hypothesis of a Plusnet issue, and that prompted me (why didn't I think of this sooner?) to test from a different PC on the same network: that is OK too. So it is a machine-specific issue with reaching that site. If anyone has any suggestions of likely cause, that would be brilliant: meanwhile, thanks to all who tested for me.

John

Browni · ‎31-07-2017

Hosts file?

Live router stats

VileReynard · ‎31-07-2017

fat finger?

"In The Beginning Was The Word, And The Word Was Aardvark."

Shep41 · ‎31-07-2017

The link works for me

JohnGeddes · ‎10-10-2017

Postscript - problem solved.

The cause was my subnet mask. I had moved away from 255.255.255.0 because I wanted to access devices in the ranges:

192.168.0.xxx ,
192.168.1.xxx and
192.168.2.xxx

My intention had been to set up for 192.168.anything - which needs a mask of 255.255.0.0

Instead, I had erroneously used 255.0.0.0 - meaning that my PC would consider any IP address beginning "192." to be local. And the IP address for w3schools begins with "192."

Thanks to those who offered suggestions.

John