dslreports logo
 
    All Forums Hot Topics Gallery
spc

spacer

Search Topic:
uniqs
518
share rss forum feed

BobbyS

join:2008-03-02
Montreal, QC

[DSL] unable to reach a site

My son is nagging me about not being able to access endoftheinter.net.
Apparently he was a regular on this site and now it doesn't load. Was using Tek's DNS #'s in my router, also tried using Google's as well, no joy.
Anything I can try to fix this ?
Thanks


Old Martin
Premium
join:2006-02-23
kudos:33

the end.
Hello,

Here is my testing.

»www.isitdownrightnow.com/endofth ··· net.html

tracert endoftheinter.net

Tracing route to endoftheinter.net [208.100.47.160]
over a maximum of 30 hops:

2 1 ms 1 ms 1 ms ge-1-3-0_500-bdr01-tek.teksavvy.com [69.165.221.
33]
3 6 ms 6 ms 6 ms ae0_3231-agg02-tor.teksavvy.com [69.165.221.138]

4 6 ms 6 ms 6 ms ae0_2110-bdr04-tor.teksavvy.com [69.196.136.36]

5 6 ms 6 ms 6 ms 10ge2-1.core2.tor1.he.net [216.66.39.113]
6 27 ms 24 ms 24 ms 10ge12-1.core1.chi1.he.net [184.105.213.150]
7 * * * Request timed out.
8 19 ms 19 ms 19 ms ip59.208-100-32.static.steadfastdns.net [208.100
.32.59]
9 18 ms 18 ms 18 ms ip160.208-100-47.static.steadfastdns.net [208.10
0.47.160]

Trace complete.


--
TSI Martin (E-Services) - TekSavvy Solutions Inc.
Authorized TSI employee ( »»TekSavvy FAQ »Official support in the forum )
Follow us on Twitter : @TekSavvyBuzz ; @TekSavvyNetwork ; @TekSavvyCSR

mikee

join:2012-12-21
Gloucester, ON
kudos:1

1 edit
reply to BobbyS
site works for me, but lets hope not or else teksavvy is going to go out of business

wow.. andre... you have some godly routing? my routing is horrible compared to yours. you using dsl or cable?


RizzleQ
Cunningham's Law Enthusiast

join:2006-01-12
Windsor, ON
kudos:5
Reviews:
·TekSavvy Cable
·TekSavvy DSL

1 edit
There is no Andre in this thread... TSI's Internet is neither DSL nor Cable; it's business LAN or something. Assuming Martin used his work Internet, you can't compare to his business level Internet with your consumer level Internet. Although you can compare to my TSI Cable:

Tracing route to endoftheinter.net [208.100.47.160] over a maximum of 30 hops:

1 1 ms 1 ms 1 ms router [192.168.1.1]
2 8 ms 7 ms 8 ms 10.195.236.1
3 17 ms 16 ms 15 ms 192-171-63-10.cpe.pppoe.ca [192.171.63.10]
4 15 ms 19 ms 15 ms ae2_6220-bdr01-tor.teksavvy.com [192.171.63.11]
5 18 ms 16 ms 19 ms ae1_2150-bdr04-tor.teksavvy.com [69.196.136.164]
6 16 ms 18 ms 17 ms 10ge2-1.core2.tor1.he.net [216.66.39.113]
7 28 ms 27 ms 68 ms 10ge12-1.core1.chi1.he.net [184.105.213.150]
8 * * * Request timed out.
9 29 ms 29 ms 29 ms ip59.208-100-32.static.steadfastdns.net [208.100.32.59]
10 50 ms 51 ms 49 ms ip160.208-100-47.static.steadfastdns.net [208.100.47.160]

Trace complete.

mikee

join:2012-12-21
Gloucester, ON
kudos:1
reply to BobbyS
yeah woops lol

BobbyS

join:2008-03-02
Montreal, QC

1 edit
reply to BobbyS
Thanks guys, I knew it was up for other people, just don't know what's wrong on my end or even where to start to look.

here's a copy of my trace:

Tracing route to ip160.208-100-47.static.steadfastdns.net [208.100.47.160]
ver a maximum of 30 hops:

1 1 ms 1 ms 1 ms unknown [192.168.0.1]
2 12 ms 19 ms 13 ms 206.248.154.104
3 12 ms 12 ms 12 ms ae2_2110-bdr03-tor.teksavvy.com [69.196.136.41]

4 14 ms 12 ms 12 ms te0-7-0-22.ccr22.yyz02.atlas.cogentco.com [38.12
.69.197]
5 28 ms 27 ms 27 ms be2080.ccr42.ord01.atlas.cogentco.com [154.54.42
5]
6 26 ms 27 ms 26 ms te0-6-1-0.ccr22.ord03.atlas.cogentco.com [154.54
6.102]
7 26 ms 30 ms 30 ms te3-1.mag01.ord03.atlas.cogentco.com [154.54.40.
82]
8 26 ms 27 ms 27 ms te0-0-2-3.rcr12.b002281-5.ord03.atlas.cogentco.c
m [154.54.1.210]
9 31 ms 27 ms 27 ms 38.104.103.238
10 26 ms 27 ms 26 ms ip78.208-100-32.static.steadfastdns.net [208.100
32.78]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16

henry128

join:2010-09-03
Mississauga, ON
kudos:1
Perhaps post a traceroute to see if your DNS resolver is working, and whether the server is reachable?

BobbyS

join:2008-03-02
Montreal, QC
edited my last post with a trace
Thanks

henry128

join:2010-09-03
Mississauga, ON
kudos:1
Can't say I can tell what's wrong, but it doesn't look like something on your end. It's strange how all of the above traceroutes and mine route through he.net rather than Cogent, even my route through 206.248.154.104. Same router (206.248.154.104) to the same destination, I'm not sure why it would take a different route?...



henry128

join:2010-09-03
Mississauga, ON
kudos:1
reply to BobbyS
On second thought... is the server reachable (ping?)
Your traceroute ends just one hop before the destination.

Here's a traceroute from Cogent's looking glass (»www.cogentco.com/en/network/look ··· ng-glass). It takes pretty much the same route yours does and successfully reaches the destination:

BobbyS

join:2008-03-02
Montreal, QC
can't ping it: Packets: 5 transmitted, 0 received, 100% lost

BobbyS

join:2008-03-02
Montreal, QC
reply to BobbyS
re-boot the router and like magic it works now :

Tracing route to ip160.208-100-47.static.steadfastdns.net [208.100.47.160]
over a maximum of 30 hops:

Tracing route to ip160.208-100-47.static.steadfastdns.net [208.100.47.160]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms unknown [192.168.0.1]
2 23 ms 12 ms 13 ms lo-100.lns03.tor.packetflow.ca [206.248.154.121]

3 60 ms 12 ms 17 ms ae3_2150-bdr03-tor.teksavvy.com [69.196.136.163]

4 13 ms 13 ms 13 ms te0-7-0-22.ccr22.yyz02.atlas.cogentco.com [38.122.69.197]
5 30 ms 30 ms 28 ms be2080.ccr42.ord01.atlas.cogentco.com [154.54.42.5]
6 27 ms 27 ms 28 ms te0-6-0-0.ccr22.ord03.atlas.cogentco.com [154.54.41.202]
7 28 ms * 28 ms te3-1.mag01.ord03.atlas.cogentco.com [154.54.40.182]
8 28 ms 28 ms 28 ms te0-0-2-0.rcr12.b002281-5.ord03.atlas.cogentco.com [154.54.6.250]
9 27 ms 28 ms 27 ms 38.104.103.238
10 28 ms 29 ms 29 ms ip78.208-100-32.static.steadfastdns.net [208.100.32.78]
11 50 ms 48 ms 49 ms ip160.208-100-47.static.steadfastdns.net [208.100.47.160]

Trace complete.