Can't open one particular website - comics.com

[rbethune]

One of the three computers here at home, namely this one, adamantly refuses to open comics.com. It won't open it with Explorer, Chrome or Safari. It won't open it at the exact same time the other two will.

It acts as if there's something wrong at the DNS level. IE displays "Internet Explorer could not connect." This computer won't even PING comics.com--it returns "TTL expired in transit." As I say, my other computers on the same simple home network have no trouble.

Mind, this is the ONLY website that won't open on this computer. It opens Google, Yahoo, Comcast, everything under the sun without a problem--it just won't open comics.com. I am in fact writing this post from that very computer, so it does browse websites--such as this one!

I've tried dumping the temporary Internet files and all that other cache stuff. No joy.

What the heck is going on with this machine? Is it possessed by the spirit of Rat from Pearls Before Swine?

 

[Ardneh]

Will it open this one?

Your favorite comics like Get Fuzzy, Pearls Before Swine, Luann, Frazz, 9 Chickweed Lane and more.

 

[rbethune]

No it won't. Interesting idea to run it through tinyurl, but it doesn't seem to change anything. I tried it with all three browsers.

 

[rbethune]

Here's another way it doesn't work:

I go to --www.seattlepi.com/fun/chickweed.asp-- and I see this:

This webpage is not available.

The webpage at --comics.com/affiliate/seattle/get_strips/?ComicID=1-- might be temporarily down or it may have moved permanently to a new web address.

Mind you, all the seattlepi.com content loads just fine. The only part that won't load is the payoff piece from comics.com.

At the exact same moment, the other computers in our house display it all just fine.

Any ideas, anybody?

 

[rbethune]

Here's what I see when I try to probe the network:

C:\Users\rbethune>ping comics.com

Pinging comics.com [64.58.142.26] with 32 bytes of data:
Reply from 68.4.13.157: TTL expired in transit.
Reply from 68.4.13.89: TTL expired in transit.
Reply from 68.4.13.157: TTL expired in transit.
Reply from 68.4.13.157: TTL expired in transit.

Ping statistics for 64.58.142.26:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\rbethune>tracert comics.com

Tracing route to comics.com [64.58.142.26]
over a maximum of 30 hops:

1 11 ms 9 ms 11 ms 68.40.68.1
2 10 ms 11 ms 11 ms 68.85.48.161
3 10 ms 11 ms 11 ms te-0-3-0-6-ar01.taylor.mi.michigan.comcast.net [
68.87.190.161]
4 24 ms 25 ms 23 ms pos-3-3-0-0-cr01.ashburn.va.ibone.comcast.net [6
8.86.90.105]
5 24 ms 25 ms 25 ms pos-0-5-0-0-pe01.ashburn.va.ibone.comcast.net [6
8.86.87.14]
6 26 ms 25 ms 25 ms ashbbprj02-ae1.312.rd.as.cox.net [68.105.31.201]

7 107 ms 107 ms 107 ms rsmtdsrj01-ae0.0.rd.oc.cox.net [68.1.0.185]
8 105 ms 108 ms 106 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]
9 106 ms 106 ms 107 ms rsmtsysj02.rd.oc.cox.net [68.4.14.214]
10 106 ms 109 ms 107 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]
11 105 ms 107 ms 124 ms rsmtsysj02.rd.oc.cox.net [68.4.14.214]
12 107 ms 108 ms 106 ms rsmtdsrj02-xe030.0.rd.oc.cox.net [68.4.13.89]
13 118 ms 109 ms 105 ms ip68-4-13-90.oc.oc.cox.net [68.4.13.90]
14 164 ms 107 ms 107 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]
15 107 ms 106 ms 107 ms rsmtsysj02.rd.oc.cox.net [68.4.14.214]
16 106 ms 107 ms 121 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]
17 110 ms 106 ms 106 ms rsmtsysj02.rd.oc.cox.net [68.4.14.214]
18 107 ms 108 ms 109 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]
19 106 ms 107 ms 106 ms ip68-4-13-90.oc.oc.cox.net [68.4.13.90]
20 105 ms 108 ms 106 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]
21 106 ms 106 ms 107 ms rsmtsysj02.rd.oc.cox.net [68.4.14.214]
22 107 ms 106 ms 107 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]
23 106 ms 107 ms 106 ms ip68-4-13-90.oc.oc.cox.net [68.4.13.90]
24 105 ms 104 ms 125 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]
25 108 ms 107 ms 107 ms rsmtsysj02.rd.oc.cox.net [68.4.14.214]
26 112 ms 199 ms 124 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]
27 106 ms 106 ms 116 ms rsmtsysj02.rd.oc.cox.net [68.4.14.214]
28 164 ms 107 ms 107 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]
29 106 ms 107 ms 106 ms rsmtsysj02.rd.oc.cox.net [68.4.14.214]
30 106 ms 107 ms 107 ms rsmtdsrj02-xe230.0.rd.oc.cox.net [68.4.13.157]

Trace complete.

C:\Users\rbethune>

 

[rbethune]

And I tried this:

netsh int ip reset reset.log
netsh winsock reset catalog

which reported success and indicated that a reboot was in order, which I did. No joy.