Is it just me... - Page 2

Ziroc · 10-19-2002, 07:55 PM

I have been talking to my friend at the ISP, and he had a DNS server hic-up, so I had him reboot the server.. This should correct it..

I was thinking it was because I turned back ON the search feature, but that wasn't it. [img]smile.gif[/img] So everything SHOULD be ok now.

-- UPDATE:

I DON'T think that is was OUR DNS server. I did a traceroute to ironworksforum.com and it listed all of them ok, then the LAST one before our server times out. (100% packet loss). So I emailed and my friend is calling them right now. It was even slow last night...

Here is my tracert:

---
Tracing route to ironworksforum.com [24.129.133.61]
over a maximum of 30 hops:

1 12 ms 12 ms 8 ms 10.100.208.1
2 12 ms 11 ms 12 ms 653210hfc182.tampabay.rr.com [65.32.10.182]
3 12 ms 14 ms 11 ms 65327hfc93.tampabay.rr.com [65.32.7.93]
4 42 ms 33 ms 24 ms 4700-atm.tampabay.rr.com [24.92.0.253]
5 * * * Request timed out.
6 14 ms 28 ms 25 ms rrcs-se-24-129-133-61.biz.rr.com -that is us![24.129.133.61]
---

Post your trace routes if you know how to use DOS. just type:

tracert ironworksforum.com (and hit enter)
then, right click, and click on 'mark' (in WinXP) and copy the text to the clipboard.

[ 10-19-2002, 08:08 PM: Message edited by: Ziroc ]

Megabot · 10-19-2002, 08:41 PM

Hmmm have you thinking on to move the IW to a BIG ISP Z? Then maby some of us dont get this damn DNS error 90% of the time we try to log on to IW? I had this problem now for about 6 months and still have problems and dont tell me to call my isp they dont find any problems so it have to be in your end of the line, and i have not any problems with other forums or webpages only IW!!

LennonCook · 10-19-2002, 09:22 PM

Quote:

Originally posted by Megabot:
Hmmm have you thinking on to move the IW to a BIG ISP Z? Then maby some of us dont get this damn DNS error 90% of the time we try to log on to IW? I had this problem now for about 6 months and still have problems and dont tell me to call my isp they dont find any problems so it have to be in your end of the line, and i have not any problems with other forums or webpages only IW!!

Mega, it *IS* on your end. It *IS* your ISP`s problem (or maybe, but probably not, your broswer`s).
And no, don`t call them. ISPs will NEVER find any problems, always say it is someone elses problem, and would (hopefully) never be called by any sane person.

If it is DNS, the following *will* fix it:
Go into DOS Prompt (Start -> Run -> Command )
Type: CD C:\WINDOWS
Type: Edit hosts.sam
Add the line:
24.129.133.61 www.ironworksforum.com
To the bottom of the file; save and exit;
Type: Edit lmhosts.sam
Add the line:
www.ironworksforum.com 24.129.133.61
To the bottom of the file; save, exit;
Back in DOS type: ren hosts.sam hosts
ren lmhosts.sam lmhosts

If at either of the "Edit" stages it says "Bad command or file name", simply type the line again without the .sam ; and leave out the relevant "ren" step.

EDIT: Tracer route of www.ironworksforum.com :

Tracing route to ironworksforum.com [24.129.133.61]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms spirit.mshome.net [192.168.0.1]
2 211 ms 98 ms 68 ms 172.31.17.152
3 69 ms 38 ms 109 ms 172.31.52.24
4 58 ms 39 ms 39 ms CPE-61-9-207-29.nsw.bigpond.net.au [61.9.207.29]

5 108 ms 39 ms 49 ms CPE-61-9-193-8.nsw.bigpond.net.au [61.9.193.8]
6 38 ms 39 ms 39 ms GigabitEthernet3-1.pit2.Sydney.telstra.net [139.
130.94.97]
7 48 ms 39 ms 39 ms GigabitEthernet1-2.pic1.Sydney.telstra.net [203.
50.12.29]
8 38 ms 39 ms 39 ms GigabitEthernet11-1.ken-core4.Sydney.telstra.net
[203.50.12.117]
9 77 ms 39 ms 39 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22
]
10 57 ms 39 ms 39 ms GigabitEthernet0-1.syd-core01.Sydney.net.reach.c
om [203.50.13.246]
11 227 ms 229 ms 429 ms 202.84.143.41
12 227 ms 229 ms 229 ms 134.159.63.62
13 227 ms 229 ms 229 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137
]
14 227 ms 229 ms 228 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73]
15 316 ms 319 ms 319 ms so-3-0-0.mp2.Atlanta1.Level3.net [64.159.1.46]
16 316 ms 319 ms 319 ms gigabitethernet11-1.hsipaccess2.Atlanta1.Level3.
net [64.159.3.10]
17 316 ms 319 ms 319 ms POS11-0.hsipaccess2.Atlanta2.Level3.net [209.244
.15.122]
18 266 ms 269 ms 269 ms pop2-atm-P0-2.atdn.net [66.185.138.33]
19 265 ms 269 ms 269 ms bb2-atm-P0-1.atdn.net [66.185.147.213]
20 285 ms 289 ms 289 ms bb1-tby-P7-0.atdn.net [66.185.152.244]
21 285 ms 289 ms 279 ms pop2-tby-P0-0.atdn.net [66.185.136.177]
22 283 ms 289 ms 289 ms rr-tampa.atdn.net [66.185.136.186]
23 284 ms 289 ms 289 ms 65327hfc89.tampabay.rr.com [65.32.7.89]
24 283 ms 289 ms 289 ms 4700-atm.tampabay.rr.com [24.92.0.253]
25 * * * Request timed out.
26 290 ms 289 ms 289 ms rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61]

Trace complete.

[ 10-19-2002, 09:28 PM: Message edited by: LennonCook ]

RevRuby · 10-19-2002, 09:28 PM

it's been real slow for me too, i did what you asked ziroc:

1 * * * Request timed out.
2 260 ms 261 ms 262 ms yago-1-ve-1.hbg2.mindspring.net [207.69.129.225]

3 271 ms 275 ms 314 ms dir01-se-4-1-0.va-ashburn0.ne.earthlink.net [209
165.109.93]
4 283 ms 275 ms 275 ms bor01-ge-1-2.va-ashburn0.ne.earthlink.net [209.1
5.104.129]
5 279 ms 288 ms 288 ms gigabitethernet5-1-113.ipcolo1.Washington1.Level
.net [64.158.57.49]
6 290 ms 288 ms 288 ms ae0-53.mp1.Washington1.Level3.net [64.159.18.65]

7 280 ms 288 ms 288 ms so-2-0-0.mp2.Atlanta1.Level3.net [64.159.1.1]
8 284 ms 288 ms 288 ms gigabitethernet11-1.hsipaccess2.Atlanta1.Level3.
et [64.159.3.10]
9 278 ms 288 ms 288 ms POS11-0.hsipaccess2.Atlanta2.Level3.net [209.244
15.122]
10 284 ms 288 ms 288 ms pop2-atm-P0-2.atdn.net [66.185.138.33]
11 277 ms 301 ms 288 ms bb2-atm-P0-3.atdn.net [66.185.138.42]
12 304 ms 301 ms 301 ms bb1-tby-P7-0.atdn.net [66.185.152.244]
13 300 ms 314 ms 314 ms pop2-tby-P0-0.atdn.net [66.185.136.177]
14 323 ms 301 ms 314 ms rr-tampa.atdn.net [66.185.136.186]
15 293 ms 314 ms 314 ms 65327hfc89.tampabay.rr.com [65.32.7.89]
16 299 ms 314 ms 301 ms 4700-atm.tampabay.rr.com [24.92.0.253]
17 * * * Request timed out.
18 303 ms 314 ms 301 ms rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61]

and that's what i got. hope that helps

Ziroc · 10-19-2002, 09:45 PM

Quote:

Originally posted by Megabot:
Hmmm have you thinking on to move the IW to a BIG ISP Z? Then maby some of us dont get this damn DNS error 90% of the time we try to log on to IW? I had this problem now for about 6 months and still have problems and dont tell me to call my isp they dont find any problems so it have to be in your end of the line, and i have not any problems with other forums or webpages only IW!!

I can't leave my friends ISP, because he charges MUCH less, and a large ISP would cost $200+.

I am telling you, it is NOT our server that is the problem. It IS your ISP, regardless of what they say. They just don't want to deal with it. TRUST me, 99.9% of people can get in here.

Scholarcs · 10-20-2002, 02:57 AM

I have not had any problems with IW for ages, it is almost certainly your ISPs guys. Also over the last few months I have noticed a huge increase in the number of people complaining of ISPs lacking DNS entries for various websites :/

LennonCook · 10-20-2002, 05:22 AM

Ok, it seems to be going slowly again, so I did another trace route:
Tracing route to ironworksforum.com [24.129.133.61]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms spirit.mshome.net [192.168.0.1]
2 44 ms 39 ms 39 ms 172.31.17.152
3 46 ms 49 ms 39 ms 172.31.50.24
4 37 ms 39 ms 46 ms CPE-61-9-207-17.nsw.bigpond.net.au [61.9.207.17]

5 41 ms 39 ms 39 ms CPE-61-9-193-8.nsw.bigpond.net.au [61.9.193.8]
6 44 ms 38 ms 39 ms GigabitEthernet3-1.pit2.Sydney.telstra.net [139.
130.94.97]
7 39 ms 39 ms 39 ms GigabitEthernet1-2.pic1.Sydney.telstra.net [203.
50.12.29]
8 44 ms 39 ms 39 ms GigabitEthernet11-1.ken-core4.Sydney.telstra.net
[203.50.12.117]
9 48 ms 39 ms 39 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22
]
10 45 ms 38 ms 39 ms GigabitEthernet0-1.syd-core01.Sydney.net.reach.c
om [203.50.13.246]
11 225 ms 228 ms 229 ms 202.84.143.41
12 227 ms 229 ms 227 ms 134.159.63.62
13 235 ms 239 ms 229 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137
]
14 235 ms 229 ms 228 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73]
15 315 ms 319 ms 319 ms so-3-0-0.mp2.Atlanta1.Level3.net [64.159.1.46]
16 314 ms 319 ms 317 ms gigabitethernet11-1.hsipaccess2.Atlanta1.Level3.
net [64.159.3.10]
17 312 ms 319 ms 319 ms POS11-0.hsipaccess2.Atlanta2.Level3.net [209.244
.15.122]
18 263 ms 269 ms 269 ms pop2-atm-P0-2.atdn.net [66.185.138.33]
19 275 ms 269 ms 269 ms bb2-atm-P0-1.atdn.net [66.185.147.213]
20 286 ms 289 ms 289 ms bb1-tby-P7-0.atdn.net [66.185.152.244]
21 283 ms 289 ms 289 ms pop2-tby-P0-0.atdn.net [66.185.136.177]
22 283 ms 289 ms 289 ms rr-tampa.atdn.net [66.185.136.186]
23 285 ms 289 ms 289 ms 65327hfc89.tampabay.rr.com [65.32.7.89]
24 285 ms 289 ms 289 ms 4700-atm.tampabay.rr.com [24.92.0.253]
25 * * * Request timed out.
26 * * * Request timed out.
27 * * 3061 ms rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61]

Trace complete.

Timed out twice, this time...

Kormar the Wanderer · 10-20-2002, 05:36 AM

It loaded almost instantly for me. Maybe the problems are over...

LennonCook · 10-20-2002, 06:16 AM

Quote:

Originally posted by Kormar the Wanderer:
It loaded almost instantly for me. Maybe the problems are over...

Sometimes it`s fast, sometimes it`s slow... been like that all day. Can you do a trace route for me ?? Instructions up there somewhere *points upwards in the thread*

I just did another one in a fast-bit, and this result *REALY* surprised me:

Tracing route to ironworksforum.com [24.129.133.61]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms spirit.mshome.net [192.168.0.1]
2 42 ms 38 ms 39 ms 172.31.17.152
3 43 ms 39 ms 39 ms 172.31.52.24
4 38 ms 39 ms 39 ms CPE-61-9-207-29.nsw.bigpond.net.au [61.9.207.29]

5 45 ms 39 ms 39 ms CPE-61-9-193-8.nsw.bigpond.net.au [61.9.193.8]
6 46 ms 39 ms 39 ms GigabitEthernet3-1.pit2.Sydney.telstra.net [139.
130.94.97]
7 40 ms 39 ms 39 ms GigabitEthernet1-2.pic1.Sydney.telstra.net [203.
50.12.29]
8 45 ms 39 ms 38 ms GigabitEthernet11-1.ken-core4.Sydney.telstra.net
[203.50.12.117]
9 45 ms 39 ms 39 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22
]
10 45 ms 46 ms 39 ms GigabitEthernet0-1.syd-core01.Sydney.net.reach.c
om [203.50.13.246]
11 230 ms 229 ms 229 ms 202.84.143.41
12 232 ms 229 ms 229 ms 134.159.63.62
13 231 ms 228 ms 229 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137
]
14 232 ms 229 ms 229 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73]
15 320 ms 319 ms 318 ms so-3-0-0.mp2.Atlanta1.Level3.net [64.159.1.46]
16 319 ms 319 ms 318 ms gigabitethernet11-1.hsipaccess2.Atlanta1.Level3.
net [64.159.3.10]
17 315 ms 319 ms 319 ms POS11-0.hsipaccess2.Atlanta2.Level3.net [209.244
.15.122]
18 265 ms 269 ms 269 ms pop2-atm-P0-2.atdn.net [66.185.138.33]
19 272 ms 269 ms 269 ms bb2-atm-P0-1.atdn.net [66.185.147.213]
20 291 ms 289 ms 289 ms bb1-tby-P7-0.atdn.net [66.185.152.244]
21 281 ms 289 ms 289 ms pop2-tby-P0-0.atdn.net [66.185.136.177]
22 282 ms 289 ms 279 ms rr-tampa.atdn.net [66.185.136.186]
23 291 ms 289 ms 289 ms 65327hfc89.tampabay.rr.com [65.32.7.89]
24 281 ms 289 ms 289 ms 4700-atm.tampabay.rr.com [24.92.0.253]
25 * * * Request timed out.
26 3028 ms 3102 ms * rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61]

27 3317 ms * * rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61]

28 * * 2997 ms rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61]

Trace complete.

100% packet loss once, 66% twice, 33% once... and all trying to get to the IW server... very strange.

LennonCook · 10-20-2002, 07:30 AM

Compare and Contrast to a *VERY* slow time (about 10 minutes on BROADBAND to load a thread):

Tracing route to ironworksforum.com [24.129.133.61]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms spirit.mshome.net [192.168.0.1]
2 44 ms 39 ms 38 ms 172.31.17.152
3 58 ms 38 ms 39 ms 172.31.50.24
4 46 ms 39 ms 39 ms CPE-61-9-207-17.nsw.bigpond.net.au [61.9.207.17]

5 42 ms 39 ms 39 ms CPE-61-9-193-8.nsw.bigpond.net.au [61.9.193.8]
6 46 ms 39 ms 38 ms GigabitEthernet3-1.pit2.Sydney.telstra.net [139.
130.94.97]
7 44 ms 49 ms 39 ms GigabitEthernet1-2.pic1.Sydney.telstra.net [203.
50.12.29]
8 38 ms 39 ms 39 ms GigabitEthernet11-1.ken-core4.Sydney.telstra.net
[203.50.12.117]
9 45 ms 39 ms 38 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22
]
10 36 ms 39 ms 39 ms GigabitEthernet0-1.syd-core01.Sydney.net.reach.c
om [203.50.13.246]
11 225 ms 229 ms 229 ms 202.84.143.41
12 227 ms 229 ms 229 ms 134.159.63.62
13 227 ms 239 ms 229 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137
]
14 231 ms 229 ms 239 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73]
15 316 ms 319 ms 319 ms so-3-0-0.mp2.Atlanta1.Level3.net [64.159.1.46]
16 315 ms 319 ms 319 ms gigabitethernet11-1.hsipaccess2.Atlanta1.Level3.
net [64.159.3.10]
17 315 ms 319 ms 319 ms POS11-0.hsipaccess2.Atlanta2.Level3.net [209.244
.15.122]
18 266 ms 269 ms 269 ms pop2-atm-P0-2.atdn.net [66.185.138.33]
19 270 ms 269 ms 269 ms bb2-atm-P0-1.atdn.net [66.185.147.213]
20 281 ms 286 ms 289 ms bb1-tby-P7-0.atdn.net [66.185.152.244]
21 282 ms 289 ms 289 ms pop2-tby-P0-0.atdn.net [66.185.136.177]
22 291 ms 289 ms 289 ms rr-tampa.atdn.net [66.185.136.186]
23 287 ms 288 ms 289 ms 65327hfc89.tampabay.rr.com [65.32.7.89]
24 287 ms 289 ms 289 ms 4700-atm.tampabay.rr.com [24.92.0.253]
25 * * * Request timed out.
26 526 ms 289 ms 289 ms rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61]

Trace complete.

One timeout on slow, 3 and 2 thirds on fast... I think Telstra`s broken again

10-19-2002, 07:55 PM	#11
Ziroc Ironworks Webmaster *Bow to the Meow* Join Date: January 4, 2001 Location: Lakeland, Florida Age: 51 Posts: 11,721	I have been talking to my friend at the ISP, and he had a DNS server hic-up, so I had him reboot the server.. This should correct it.. I was thinking it was because I turned back ON the search feature, but that wasn't it. [img]smile.gif[/img] So everything SHOULD be ok now. -- UPDATE: I DON'T think that is was OUR DNS server. I did a traceroute to ironworksforum.com and it listed all of them ok, then the LAST one before our server times out. (100% packet loss). So I emailed and my friend is calling them right now. It was even slow last night... Here is my tracert: --- Tracing route to ironworksforum.com [24.129.133.61] over a maximum of 30 hops: 1 12 ms 12 ms 8 ms 10.100.208.1 2 12 ms 11 ms 12 ms 653210hfc182.tampabay.rr.com [65.32.10.182] 3 12 ms 14 ms 11 ms 65327hfc93.tampabay.rr.com [65.32.7.93] 4 42 ms 33 ms 24 ms 4700-atm.tampabay.rr.com [24.92.0.253] 5 * * * Request timed out. 6 14 ms 28 ms 25 ms rrcs-se-24-129-133-61.biz.rr.com -that is us![24.129.133.61] --- Post your trace routes if you know how to use DOS. just type: tracert ironworksforum.com (and hit enter) then, right click, and click on 'mark' (in WinXP) and copy the text to the clipboard. [ 10-19-2002, 08:08 PM: Message edited by: Ziroc ] __________________ Ironworks Gaming's Official Youtube Gaming Channel

10-19-2002, 09:28 PM	#14
RevRuby Fzoul Chembryl Join Date: July 11, 2002 Location: Limbo Age: 44 Posts: 1,720	it's been real slow for me too, i did what you asked ziroc: 1 * * * Request timed out. 2 260 ms 261 ms 262 ms yago-1-ve-1.hbg2.mindspring.net [207.69.129.225] 3 271 ms 275 ms 314 ms dir01-se-4-1-0.va-ashburn0.ne.earthlink.net [209 165.109.93] 4 283 ms 275 ms 275 ms bor01-ge-1-2.va-ashburn0.ne.earthlink.net [209.1 5.104.129] 5 279 ms 288 ms 288 ms gigabitethernet5-1-113.ipcolo1.Washington1.Level .net [64.158.57.49] 6 290 ms 288 ms 288 ms ae0-53.mp1.Washington1.Level3.net [64.159.18.65] 7 280 ms 288 ms 288 ms so-2-0-0.mp2.Atlanta1.Level3.net [64.159.1.1] 8 284 ms 288 ms 288 ms gigabitethernet11-1.hsipaccess2.Atlanta1.Level3. et [64.159.3.10] 9 278 ms 288 ms 288 ms POS11-0.hsipaccess2.Atlanta2.Level3.net [209.244 15.122] 10 284 ms 288 ms 288 ms pop2-atm-P0-2.atdn.net [66.185.138.33] 11 277 ms 301 ms 288 ms bb2-atm-P0-3.atdn.net [66.185.138.42] 12 304 ms 301 ms 301 ms bb1-tby-P7-0.atdn.net [66.185.152.244] 13 300 ms 314 ms 314 ms pop2-tby-P0-0.atdn.net [66.185.136.177] 14 323 ms 301 ms 314 ms rr-tampa.atdn.net [66.185.136.186] 15 293 ms 314 ms 314 ms 65327hfc89.tampabay.rr.com [65.32.7.89] 16 299 ms 314 ms 301 ms 4700-atm.tampabay.rr.com [24.92.0.253] 17 * * * Request timed out. 18 303 ms 314 ms 301 ms rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61] and that's what i got. hope that helps __________________ peek-a-boo

10-20-2002, 02:57 AM	#16
Scholarcs Red Dragon Join Date: December 5, 2001 Location: Auckland, New Zealand Age: 38 Posts: 1,557	I have not had any problems with IW for ages, it is almost certainly your ISPs guys. Also over the last few months I have noticed a huge increase in the number of people complaining of ISPs lacking DNS entries for various websites :/ __________________ <br />\"A child of five would understand this. Send someone to fetch a child of five\" - Groucho Marx<br />Member of the ORT Clan. <br />\"Some birds are not meant to be caged because their feathers are too bright\"<br />Ma bouche sera la bouche des malheurs qui n\'ont point de bouche, ma voix, la liberté de celles qui s\'affaissent au cachot du désespoir. - Aimé Césaire<br />La plus perdue de toutes les journées est celle où l\'on n\'a pas ri. - Sébastien Roch Nicolas

10-20-2002, 05:36 AM	#18
Kormar the Wanderer Manshoon Join Date: June 1, 2001 Location: Land of Hymdale Posts: 238	It loaded almost instantly for me. Maybe the problems are over... __________________ \"Beware fool that you put too much stock in the power of the spoken word, lest the unspoken one trample you from behind.\"<BR>Kormar

10-19-2002, 08:41 PM	#12
Megabot Ma'at - Goddess of Truth & Justice Join Date: October 18, 2003 Location: Oslo, Norway. Age: 61 Posts: 3,360	Hmmm have you thinking on to move the IW to a BIG ISP Z? Then maby some of us dont get this damn DNS error 90% of the time we try to log on to IW? I had this problem now for about 6 months and still have problems and dont tell me to call my isp they dont find any problems so it have to be in your end of the line, and i have not any problems with other forums or webpages only IW!!

10-20-2002, 05:22 AM	#17
LennonCook Jack Burton Join Date: November 10, 2001 Location: Bathurst & Orange, in constant flux Age: 37 Posts: 5,452	Ok, it seems to be going slowly again, so I did another trace route: Tracing route to ironworksforum.com [24.129.133.61] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms spirit.mshome.net [192.168.0.1] 2 44 ms 39 ms 39 ms 172.31.17.152 3 46 ms 49 ms 39 ms 172.31.50.24 4 37 ms 39 ms 46 ms CPE-61-9-207-17.nsw.bigpond.net.au [61.9.207.17] 5 41 ms 39 ms 39 ms CPE-61-9-193-8.nsw.bigpond.net.au [61.9.193.8] 6 44 ms 38 ms 39 ms GigabitEthernet3-1.pit2.Sydney.telstra.net [139. 130.94.97] 7 39 ms 39 ms 39 ms GigabitEthernet1-2.pic1.Sydney.telstra.net [203. 50.12.29] 8 44 ms 39 ms 39 ms GigabitEthernet11-1.ken-core4.Sydney.telstra.net [203.50.12.117] 9 48 ms 39 ms 39 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22 ] 10 45 ms 38 ms 39 ms GigabitEthernet0-1.syd-core01.Sydney.net.reach.c om [203.50.13.246] 11 225 ms 228 ms 229 ms 202.84.143.41 12 227 ms 229 ms 227 ms 134.159.63.62 13 235 ms 239 ms 229 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137 ] 14 235 ms 229 ms 228 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73] 15 315 ms 319 ms 319 ms so-3-0-0.mp2.Atlanta1.Level3.net [64.159.1.46] 16 314 ms 319 ms 317 ms gigabitethernet11-1.hsipaccess2.Atlanta1.Level3. net [64.159.3.10] 17 312 ms 319 ms 319 ms POS11-0.hsipaccess2.Atlanta2.Level3.net [209.244 .15.122] 18 263 ms 269 ms 269 ms pop2-atm-P0-2.atdn.net [66.185.138.33] 19 275 ms 269 ms 269 ms bb2-atm-P0-1.atdn.net [66.185.147.213] 20 286 ms 289 ms 289 ms bb1-tby-P7-0.atdn.net [66.185.152.244] 21 283 ms 289 ms 289 ms pop2-tby-P0-0.atdn.net [66.185.136.177] 22 283 ms 289 ms 289 ms rr-tampa.atdn.net [66.185.136.186] 23 285 ms 289 ms 289 ms 65327hfc89.tampabay.rr.com [65.32.7.89] 24 285 ms 289 ms 289 ms 4700-atm.tampabay.rr.com [24.92.0.253] 25 * * * Request timed out. 26 * * * Request timed out. 27 * * 3061 ms rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61] Trace complete. Timed out twice, this time...

10-20-2002, 07:30 AM	#20
LennonCook Jack Burton Join Date: November 10, 2001 Location: Bathurst & Orange, in constant flux Age: 37 Posts: 5,452	Compare and Contrast to a VERY slow time (about 10 minutes on BROADBAND to load a thread): Tracing route to ironworksforum.com [24.129.133.61] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms spirit.mshome.net [192.168.0.1] 2 44 ms 39 ms 38 ms 172.31.17.152 3 58 ms 38 ms 39 ms 172.31.50.24 4 46 ms 39 ms 39 ms CPE-61-9-207-17.nsw.bigpond.net.au [61.9.207.17] 5 42 ms 39 ms 39 ms CPE-61-9-193-8.nsw.bigpond.net.au [61.9.193.8] 6 46 ms 39 ms 38 ms GigabitEthernet3-1.pit2.Sydney.telstra.net [139. 130.94.97] 7 44 ms 49 ms 39 ms GigabitEthernet1-2.pic1.Sydney.telstra.net [203. 50.12.29] 8 38 ms 39 ms 39 ms GigabitEthernet11-1.ken-core4.Sydney.telstra.net [203.50.12.117] 9 45 ms 39 ms 38 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22 ] 10 36 ms 39 ms 39 ms GigabitEthernet0-1.syd-core01.Sydney.net.reach.c om [203.50.13.246] 11 225 ms 229 ms 229 ms 202.84.143.41 12 227 ms 229 ms 229 ms 134.159.63.62 13 227 ms 239 ms 229 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137 ] 14 231 ms 229 ms 239 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73] 15 316 ms 319 ms 319 ms so-3-0-0.mp2.Atlanta1.Level3.net [64.159.1.46] 16 315 ms 319 ms 319 ms gigabitethernet11-1.hsipaccess2.Atlanta1.Level3. net [64.159.3.10] 17 315 ms 319 ms 319 ms POS11-0.hsipaccess2.Atlanta2.Level3.net [209.244 .15.122] 18 266 ms 269 ms 269 ms pop2-atm-P0-2.atdn.net [66.185.138.33] 19 270 ms 269 ms 269 ms bb2-atm-P0-1.atdn.net [66.185.147.213] 20 281 ms 286 ms 289 ms bb1-tby-P7-0.atdn.net [66.185.152.244] 21 282 ms 289 ms 289 ms pop2-tby-P0-0.atdn.net [66.185.136.177] 22 291 ms 289 ms 289 ms rr-tampa.atdn.net [66.185.136.186] 23 287 ms 288 ms 289 ms 65327hfc89.tampabay.rr.com [65.32.7.89] 24 287 ms 289 ms 289 ms 4700-atm.tampabay.rr.com [24.92.0.253] 25 * * * Request timed out. 26 526 ms 289 ms 289 ms rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61] Trace complete. One timeout on slow, 3 and 2 thirds on fast... I think Telstra`s broken again

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)