[bacobits1]

why I can't access 3 sites from here?

innerfidelity.com

A hosting company in El Segundo,CA using Net2Ez as its ISP.
this is the hosting for 3 sites.

www.stereophile.com
www.analogplanet.com
www.audiostream.com

the only sites out of 100 bookmarks I cannot access.
I can access via a proxy server site.

testing with  nwtools.com >>as follows

A connection with the server could not be established
No headers downloaded

ping >> 64.93.76.214
4 sent 32 bits> received 0> 4 timed out> lost 4 (100% loss)

Command promt ping direct>>as follows

ping >> 64.93.76.214
4 sent 32 bits> received 0> 4 timed out> lost 4 (100% loss) 

Win 10 machines 2, windows 7, 2 machines, Android tablet. All browsers IE, Firefox etc.
All router settings default factory, reset rebooted
browsers set to default and on 4 machines.

What gives here?

Anyone? Anyone else have this problem?
Posted to "Windows Secret" lounge and still no remedy.

[simoon]

Have you tried to do a tracert?

Your pings tell you that you can't get there. A tracert will tell you where the failure is occurring.

EDIT: I can't ping those addresses either. That would probably mean their servers don't allow ping, to protect from DDoS attacks.

[bacobits1]

Simoon thanks!
Here it is>

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>tracert www.stereophile.com

Tracing route to stereophile.com [64.93.76.214]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  COPPER-MONKEY [192.168.1.1]
  2     3 ms     2 ms     1 ms  MyRouter.Home [192.168.254.254]
  3     9 ms     9 ms     9 ms  172.16.100.1
  4     9 ms     8 ms     8 ms  h176.34.130.40.static.ip.windstream.net [40.130.34.176]
  5     9 ms     9 ms     9 ms  h130.35.130.40.static.ip.windstream.net [40.130.35.130]
  6    10 ms    11 ms     9 ms  et8-0-0-0.cr02.chrl01-nc.us.windstream.net [40.128.248.160]
  7    14 ms    13 ms    14 ms  h32.59.132.40.static.ip.windstream.net [40.132.59.32]
  8    14 ms    14 ms    14 ms  67.106.215.81.ptr.us.xo.net [67.106.215.81]
  9    66 ms    66 ms    65 ms  207.88.13.54.ptr.us.xo.net [207.88.13.54]
 10    66 ms    79 ms    89 ms  207.88.12.179.ptr.us.xo.net [207.88.12.179]
 11    66 ms    67 ms    75 ms  rcb1.dallas2-tx.us.xo.net [207.88.12.153]
 12    72 ms    67 ms    66 ms  207.88.12.130.ptr.us.xo.net [207.88.12.130]
 13    67 ms    66 ms    66 ms  207.88.14.213.ptr.us.xo.net [207.88.14.213]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\WINDOWS\system32>

So what does this tell you?
My end or theirs?

[Phil A]

Well I don't see Stereophile's IP Address (unless I missed it) per this - http://stereophile.com.ipaddress.com/

[bacobits1]

What don't you see?


C:\WINDOWS\system32>tracert www.stereophile.com

Tracing route to stereophile.com [64.93.76.214]
over a maximum of 30 hops:

[rjbond3rd]

It's not that unusual for site(s) to be inaccessible due to a routing issue.

Ask your ISP if there is a route between your location and those sites.   (Evidently there isn't, but they need to acknowledge the issue -- they might be aware of it.)  Good luck!

[Phil A]

What don't you see?


C:\WINDOWS\system32>tracert www.stereophile.com

Tracing route to stereophile.com [64.93.76.214]
over a maximum of 30 hops:

Yes missed it - was focused at looking at the stuff below it.

[bacobits1]

Thanks!!
I'll see what Windstream has to say.

[bacobits1]

This has been fixed apparently at their server end. Not Windstream.