Howard H. MarkB_MI- update computer prob..

Yep - you"re probably right... I read that to mean he got an active statement saying "over the max of 30 hops", not thinking about just the boilerplate title line...

In thinking about this problem, I guess we should have expected DNS to return OK, since 2x4"s original message said the error was "timed out" not "page cannot be found" or the throwback to a general search engine.

2x4 - are you by chance running a proxy server or filtering service - like Dan"s Guardian or Squid or Wingate or anything like that?? What antivirus and firewall do you use? Are you running Windows XP? Have you ever had any trouble with malware or viruses??

A lot of malware these days tries to "filter" where you go on the Internet and redirect you to their own sites, instead of where you want to go.

Also, you are talking Internet Explorer, aren"t you?? If so, you might "manage add-ons" and/or try installing Firefox and trying it - since malware add-ons can also hijack web addresses - or at least try to "check in" with their own websites everytime you go somewhere...

Howard

Norton's firewall also "filters" Internet traffic - I was working on a PC the other day that could not connect to the Internet at all.

Finally uninstalled the entire Norton package and it partially connected. Finally downloaded Norton's "total removal" tool that completely removes all traces of Norton and then their Internet connection was fine.

HH

BUT, if you are going over the default max of 30 hops with a tracert, someone providing connectivity between your PC and ytmag has some really convoluted routing.

The actual max # of hops that a packet wandering the Internet can make is higher than that (depending on your operating system and some other things), but that many hops could certainly cause trouble.

Try to check # of hops on a day when it is working fine.

If it corresponds to high # of hops=not working, versus low #=working, it essentially boils down to a problem of how well your ISP, YTmag's ISP, and everyone between the two are working together/have their act together...

Who is your ISP, BTW? Are you really on Bellsouth near Atlanta?

You wouldn't by chance have a pretty elaborate network where you are trying connect from? For example, a couple of routers tied together behind the ISP connection and/or some older or oddball router equipment?

Howard

I don't think he's actually going 30 hops; I think he's saying that there's no response after nine hops which is pretty typical of what traceroute reports when you run into a firewall.

Here's what my traceroute results look like:

[mark@leghorn2 ~]$ traceroute ytmag.com
traceroute to ytmag.com (209.219.50.2), 30 hops max, 40 byte packets 1 gw2-53.sfld-mi.123.net (74.126.0.12) 194.870 ms 213.725 ms 253.666 ms 2 vl-27.sfld-mi.123.net (74.126.0.1) 237.637 ms 281.665 ms * 3 ge-6-11-262.car2.Detroit1.Level3.net (4.79.14.5) 307.543 ms * * 4 * * * 5 * * ae-8-8.ebr2.Chicago1.Level3.net (4.69.133.242) 424.297 ms 6 * ae-78.ebr3.Chicago1.Level3.net (4.69.134.62) 185.881 ms 198.858 ms 7 ae-3.ebr2.Denver1.Level3.net (4.69.132.61) 228.066 ms 246.787 ms * 8 * ae-2.ebr2.Seattle1.Level3.net (4.69.132.53) 293.643 ms * 9 ae-21-54.car1.Seattle1.Level3.net (4.68.105.98) 196.897 ms * *
10 g1-0.border1.rap.sea.transedge.com (63.211.199.6) 196.928 ms * 204.200 ms
11 f0-0.agg1.rap.sea.transedge.com (216.171.128.33) 192.807 ms 193.410 ms 191.840 ms
12 114.61.19.209.transedge.com (209.19.61.114) 220.838 ms 209.583 ms 203.290 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

It doesn't sound like a problem with your ISP.

When I do an "nslookup ytmag.com" from my machine I get "209.219.50.2". If that's what you saw, then your ISP's DNS server is most likely OK.

When I do a "traceroute ytmag.com", it times out after "114.61.19.209.transedge.com (209.19.61.114)", which is 11 hops for me. 209.19.61.114 is pretty close to 209.219.50.2 (ytmag.com), so traceroute just can't get by a firewall. (This is normal.) So assuming the last IP that traceroute reports is "209.19.x.x", your requests are being routed OK. If that's the case, ytmag was probably down for a few minutes.