Slowness?

[jimnyc]

Anyone experiencing slowness right now on the board? If so, can someone please run a tracert and let me know the results?

On windows machines:

Start - Run - type in "cmd"

At dos prompt type in "tracert debatepolicy.com"

I'm interested in the last line which will be this server, and the 3 response times listed in "ms"

Thanks!

[CockySOB]

Bottleneck at ewok.nocdirect.com resulting in latencies in the 230-240ms range. Everything else is normal.

[CockySOB]

Also an intermittent spike at chi-bb1-link.telia.net with latency normally in the <100ms area, but occasional spikes to >150ms and the sporadic timeout.

[CockySOB]

I bounced a few traces off other servers with the same effect at ewok.nocdirect.com (latencies in the 230-240ms range).

[jimnyc]

Bottleneck at ewok.nocdirect.com resulting in latencies in the 230-240ms range. Everything else is normal.

Exactly! And that's the server we are on here. Here are my results, read after for my comments!



Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 7 ms 6 ms 6 ms 10.120.0.1
3 6 ms 7 ms 7 ms dstswr2-vlan2.rh.mmrnny.cv.net [67.83.229.162]
4 * * * Request timed out.
5 8 ms 11 ms 7 ms rtr4-tg10-2.wan.whplny.cv.net [64.15.8.29]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 44 ms 44 ms 43 ms atl-bb1-link.telia.net [213.248.80.142]
10 133 ms 211 ms 208 ms globalnet-103907-atl-bb1.c.telia.net [213.248.90
.54]
11 30 ms 27 ms 29 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
12 30 ms 31 ms 31 ms 209.51.131.90
13 204 ms 203 ms 204 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

I opened a support ticket, and gave them multiple tracert results to show them as an example. The tech that replied said the server load was fine, but I was receiving data loss at hops 4,6,7 & 8 - and that I should call my internet provider! LOL

Those are simply routers that are configured NOT to reply to ping requests! I then had to give him remote ping tests from no less than 10 sites around the world that perform remote tracert and they ALL showed high latency on the server. Now they stopped replying to my ticket!

I installed a top of the line remote monitoring program that tests every 60 seconds. Every ping to the server is over 200ms, and every test to my POP server is over 600ms!

Call my ISP when the IP returning high latency is the server in their facility? WTF?

[CockySOB]

Everything is showing ~60ms now, which is about what it should be I would think.

[jimnyc]

Everything is showing ~60ms now, which is about what it should be I would think.

Yes, they must have done something, my tests all just starting returning results between 25-30ms.

Sure, but it's my ISP causing me to get high returns from their server, and from locations all around the world on remote tests!

I can't believe he had the audacity to tell me the hops not responding were causing data loss.

[glockmail]

Anyone experiencing slowness right now on the board? If so, can someone please run a tracert and let me know the results?

On windows machines:

Start - Run - type in "cmd"

At dos prompt type in "tracert debatepolicy.com"

I'm interested in the last line which will be this server, and the 3 response times listed in "ms"

Thanks!

Yeah sure you just want to hunt me down and find out where I really live. :slap:

;)

[Mr. P]

Been having problems for a few days connecting here....but then I am dial-up.
Then again, it's ONLY this site..

[Yurt]

14 108 ms 219 ms 102 ms
15 86 ms 83 ms 83 ms
16 83 ms 84 ms 83 ms

Trace complete.

[jimnyc]

Been having problems for a few days connecting here....but then I am dial-up.
Then again, it's ONLY this site..

I gave it to them pretty good last night. I out and out told them I was astonished at their lack of knowledge, and that quite frankly, I was very disappointed at their ineptitude at pointing out non-responsive hops as "data loss" when it's fairly common knowledge that lots of routers are configured purposely NOT to respond to such requests.

I told them I installed a remote monitoring program and that if I could prove this becomes a recurring issue that I want to be moved to a faster, less loaded server, or that I would cancel my service and look for another host.

I'll keep pushing them. This isn't a nickel and dime "fly by night" host. They're HUGE in the industry and I expect much better for the money I spend. Hopefully we'll see better performance in the very near future.

[glockmail]

1 <1ms
2 7ms
3 6ms
4 8ms
5 12ms
6 23ms
7 23ms
8 23ms
9 24ms
10 27ms
11 23ms
12 26ms
13 24ms
trace complete

I moved my company site from Hostway to Startlogic and save about 1/2 and have huge storage and bandwidth (for my tiny bit of use). Same test results to my site:

1 <1ms
2 7ms
3 6ms
4 9ms
5 19ms
6 13ms
7 31ms
8 25ms
9 27ms
10 26ms
11 27ms
12 45ms
13 47ms
14 84ms
15 82ms
16 84ms
17 * request timed out :pee:
18 83ms

Looks like you're doing better than me.

[Mr. P]

Jim, here is trace at 10 am and 10:30 am..................
**********************************

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 125 ms 139 ms 129 ms ipt-mtce17.dial.aol.com [64.12.8.17]
2 130 ms 130 ms 129 ms iptfarme-mr4-sw0.conc.aol.com [64.12.120.158]
3 130 ms 140 ms 130 ms wc2-mtc-ae4.router.aol.com [172.20.201.76]
4 140 ms 130 ms 130 ms dar2-mtc-G1-1-0.atdn.net [172.21.44.73]
5 140 ms 139 ms 129 ms pop2-ash-S1-3-0.atdn.net [66.185.151.97]
6 130 ms 129 ms 140 ms GlobalCrossing.atdn.net [66.185.141.194]
7 150 ms 149 ms 150 ms 64.209.99.62
8 150 ms 150 ms 149 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 150 ms 149 ms 149 ms 209.51.131.90
10 150 ms 149 ms 150 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 195 ms 590 ms 309 ms ipt-mtce17.dial.aol.com [64.12.8.17]
2 410 ms 149 ms 309 ms iptfarme-mr4-sw0.conc.aol.com [64.12.120.158]
3 149 ms 400 ms 409 ms wc2-mtc-ae4.router.aol.com [172.20.201.76]
4 159 ms 139 ms 139 ms dar2-mtc-G1-1-0.atdn.net [172.21.44.73]
5 811 ms 148 ms 239 ms pop2-ash-S1-2-0.atdn.net [66.185.138.249]
6 140 ms 430 ms 139 ms GlobalCrossing.atdn.net [66.185.141.194]
7 461 ms 499 ms 490 ms 64.209.99.62
8 270 ms 330 ms 409 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 490 ms 200 ms 189 ms 209.51.131.90
10 400 ms 750 ms 390 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

[glockmail]

Did you type all that in? I couldn't "copy" from my DOS window.

[jimnyc]

Did you type all that in? I couldn't "copy" from my DOS window.

While the DOS window is open, click on the dos icon (c:\) in the upper left hand corner. Choose "edit - mark". Now highlight everything you want to copy. After that, go back to the menu and choose "edit - copy"

[Hagbard Celine]

Anyone experiencing slowness right now on the board?

Yeah, now that you mention it, some of the conservative posters are a lot slower today than usual :dance:

[jimnyc]

Yeah, now that you mention it, some of the conservative posters are a lot slower today than usual :dance:

And yet they're still quicker than the libs! :laugh2:

[Mr. P]

11:35 am
************

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 1190 ms 601 ms 140 ms ipt-mtce17.dial.aol.com [64.12.8.17]
2 964 ms 1193 ms 1203 ms iptfarme-mr4-sw0.conc.aol.com [64.12.120.158]
3 621 ms 290 ms 149 ms wc2-mtc-ae4.router.aol.com [172.20.201.76]
4 146 ms 150 ms 140 ms dar2-mtc-G1-1-0.atdn.net [172.21.44.73]
5 292 ms 159 ms 331 ms pop2-ash-S1-2-0.atdn.net [66.185.138.249]
6 493 ms 381 ms 340 ms GlobalCrossing.atdn.net [66.185.141.194]
7 422 ms 1093 ms 611 ms 64.209.99.62
8 1024 ms 912 ms 1203 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 1524 ms 1524 ms 340 ms 209.51.131.90
10 161 ms 160 ms 170 ms ewok.nocdirect.com [69.73.181.50]

[glockmail]

While the DOS window is open, click on the dos icon (c:\) in the upper left hand corner. Choose "edit - mark". Now highlight everything you want to copy. After that, go back to the menu and choose "edit - copy"
Cool. Learned someting today. :thumb:

[Mr. P]

2:10 PM
***********************


Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 987 ms 850 ms 780 ms ipt-mtce17.dial.aol.com [64.12.8.17]
2 860 ms 720 ms 440 ms iptfarme-mr4-sw0.conc.aol.com [64.12.120.158]
3 800 ms 590 ms 360 ms wc2-mtc-ae4.router.aol.com [172.20.201.76]
4 660 ms 680 ms 640 ms dar2-mtc-G1-1-0.atdn.net [172.21.44.73]
5 700 ms 470 ms 680 ms pop2-ash-S1-3-0.atdn.net [66.185.151.97]
6 860 ms 740 ms 907 ms GlobalCrossing.atdn.net [66.185.141.194]
7 480 ms 790 ms 800 ms 64.209.99.62
8 1091 ms 910 ms 710 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 931 ms 1040 ms 710 ms 209.51.131.90
10 1091 ms 800 ms 400 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

[glockmail]

2:10 PM
***********************


Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 987 ms 850 ms 780 ms ipt-mtce17.dial.aol.com [64.12.8.17]
2 860 ms 720 ms 440 ms iptfarme-mr4-sw0.conc.aol.com [64.12.120.158]
3 800 ms 590 ms 360 ms wc2-mtc-ae4.router.aol.com [172.20.201.76]
4 660 ms 680 ms 640 ms dar2-mtc-G1-1-0.atdn.net [172.21.44.73]
5 700 ms 470 ms 680 ms pop2-ash-S1-3-0.atdn.net [66.185.151.97]
6 860 ms 740 ms 907 ms GlobalCrossing.atdn.net [66.185.141.194]
7 480 ms 790 ms 800 ms 64.209.99.62
8 1091 ms 910 ms 710 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 931 ms 1040 ms 710 ms 209.51.131.90
10 1091 ms 800 ms 400 ms ewok.nocdirect.com [69.73.181.50]

Trace complete. You do realize that this and the last few runs now enables The Man to zero in on your exact location within about 8 feet, don't you? :poke:

[Mr. P]

You do realize that this and the last few runs now enables The Man to zero in on your exact location within about 8 feet, don't you? :poke:

:laugh2: Yeah, but as slow as it is now, I can take a nap, eat and leave town before they'll get here. :cheers2:


2:25pm
**************
Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 1861 ms 1779 ms 1503 ms ipt-mtce17.dial.aol.com [64.12.8.17]
2 892 ms 2065 ms 1965 ms iptfarme-mr4-sw0.conc.aol.com [64.12.120.158]
3 3761 ms 4274 ms 2899 ms wc2-mtc-ae4.router.aol.com [172.20.201.76]
4 1961 ms 2065 ms 2206 ms dar2-mtc-G1-1-0.atdn.net [172.21.44.73]
5 2724 ms 1203 ms 1684 ms pop2-ash-S1-3-0.atdn.net [66.185.151.97]
6 810 ms 932 ms 1154 ms GlobalCrossing.atdn.net [66.185.141.194]
7 761 ms 903 ms 741 ms 64.209.99.62
8 641 ms 761 ms 691 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 591 ms 631 ms 832 ms 209.51.131.90
10 581 ms 661 ms 721 ms ewok.nocdirect.com [69.73.181.50]

[Mr. P]

2:29pm...I feel like a slug..:laugh2:
Dial-up is great, I can get a nap and never miss a thing. :laugh2:

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 786 ms 907 ms 611 ms ipt-mtce17.dial.aol.com [64.12.8.17]
2 681 ms 601 ms 761 ms iptfarme-mr4-sw0.conc.aol.com [64.12.120.158]
3 983 ms 521 ms 902 ms wc2-mtc-ae4.router.aol.com [172.20.201.76]
4 716 ms 521 ms 541 ms dar2-mtc-G1-1-0.atdn.net [172.21.44.73]
5 613 ms 721 ms 521 ms pop2-ash-S1-3-0.atdn.net [66.185.151.97]
6 673 ms 661 ms 962 ms GlobalCrossing.atdn.net [66.185.141.194]
7 721 ms 822 ms 611 ms 64.209.99.62
8 761 ms 440 ms 842 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 908 ms 631 ms 812 ms 209.51.131.90
10 894 ms 1092 ms 1132 ms ewok.nocdirect.com [69.73.181.50]

[Mr. P]

2:56PM...OUCH!!! I'll be running into my own text soon, and I type SLOOOOOOW!:laugh2:

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 1000 ms 611 ms 1171 ms ipt-mtce17.dial.aol.com [64.12.8.17]
2 1051 ms 1022 ms 911 ms iptfarme-mr4-sw0.conc.aol.com [64.12.120.158]
3 671 ms 697 ms 440 ms wc2-mtc-ae4.router.aol.com [172.20.201.76]
4 750 ms 1112 ms 933 ms dar2-mtc-G1-1-0.atdn.net [172.21.44.73]
5 834 ms 872 ms 611 ms pop2-ash-S1-3-0.atdn.net [66.185.151.97]
6 1035 ms 982 ms 681 ms GlobalCrossing.atdn.net [66.185.141.194]
7 637 ms 962 ms 871 ms 64.209.99.62
8 532 ms 841 ms 1093 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 630 ms 812 ms 832 ms 209.51.131.90
10 1135 ms 801 ms 1162 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

[glockmail]

2:56PM...OUCH!!! I'll be running into my own text soon, and I type SLOOOOOOW!:laugh2:

.... Man, you're gettin obsessed with this thing. This thread needs to move to the Steel Cage! :laugh2:

[jimnyc]

I'm experiencing issues again today and am currently fighting with support. The guy answering my tickets HAS NO IDEA what he's talking about and is assuming I don't either. His replies are absolutely laughable! I have sent off an email to management seeking a resolution...

[glockmail]

I'm experiencing issues again today and am currently fighting with support. The guy answering my tickets HAS NO IDEA what he's talking about and is assuming I don't either. His replies are absolutely laughable! I have sent off an email to management seeking a resolution...
I hate when support does this. My ski buddy had major problems with his new custom fit boots last year due to this odd bone in his foot and we took them in on a friday night and ended up talking with this wise-ass B crew techhie. He tried to convince us ajustments we made, AS DESCRIBED IN THE MANUAL, fucked up the $800 boots permanently. I went home and grinded the inside of his boot myself. I met the techie's boss later that week at a party and explained to him what happened. Guess what- the techie no longer works there.

[Mr. P]

Man, you're gettin obsessed with this thing. This thread needs to move to the Steel Cage! :laugh2:

Just doing it for Jims info. Donno if it matters since I'm dial-up. Here's the latest.

@ 5pm************

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 1137 ms 1661 ms 1141 ms ipt-dtcc15.dial.aol.com [205.188.70.79]
2 1390 ms 1892 ms 1952 ms iptfarmc-dr2-sw0-vlan3.conc.aol.com [205.188.120
.94]
3 1259 ms 1902 ms 1671 ms wc2-dtc-ae2.net.aol.com [172.18.30.44]
4 1590 ms 851 ms 770 ms dar2-dtc-GE1-1-0.net.aol.com [172.18.52.73]
5 1071 ms 690 ms 1832 ms pop2-ash-S0-2-0.atdn.net [66.185.141.69]
6 1209 ms 1091 ms 780 ms GlobalCrossing.atdn.net [66.185.136.10]
7 891 ms 630 ms 750 ms 64.209.99.62
8 1211 ms 700 ms 1141 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 1600 ms 1301 ms 1091 ms 209.51.131.90
10 1450 ms 1401 ms 1151 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

[jimnyc]

Just doing it for Jims info. Donno if it matters since I'm dial-up. Here's the latest.

@ 5pm************

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 1137 ms 1661 ms 1141 ms ipt-dtcc15.dial.aol.com [205.188.70.79]
2 1390 ms 1892 ms 1952 ms iptfarmc-dr2-sw0-vlan3.conc.aol.com [205.188.120
.94]
3 1259 ms 1902 ms 1671 ms wc2-dtc-ae2.net.aol.com [172.18.30.44]
4 1590 ms 851 ms 770 ms dar2-dtc-GE1-1-0.net.aol.com [172.18.52.73]
5 1071 ms 690 ms 1832 ms pop2-ash-S0-2-0.atdn.net [66.185.141.69]
6 1209 ms 1091 ms 780 ms GlobalCrossing.atdn.net [66.185.136.10]
7 891 ms 630 ms 750 ms 64.209.99.62
8 1211 ms 700 ms 1141 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 1600 ms 1301 ms 1091 ms 209.51.131.90
10 1450 ms 1401 ms 1151 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

Mr. P - admittedly, your ping requests on the 10th hop to the server itself are astronomically high. BUT, your entire path is just as high! Based on your path and all results, I would say the final time is right in line as it should be. You'll know the problem is the server when the final result is MUCH higher than the rest of the hops. I'm afraid to say, you're problem is likely being on dial-up.

[jimnyc]

I hate when support does this. My ski buddy had major problems with his new custom fit boots last year due to this odd bone in his foot and we took them in on a friday night and ended up talking with this wise-ass B crew techhie. He tried to convince us ajustments we made, AS DESCRIBED IN THE MANUAL, fucked up the $800 boots permanently. I went home and grinded the inside of his boot myself. I met the techie's boss later that week at a party and explained to him what happened. Guess what- the techie no longer works there.

That's what happens when you hire those less informed or less trained in the field. My ticket has now been transferred to the senior support admin. I've worked with him in the past and he's awesome, so I'm crossing my fingers that he'll be more helpful.

[Mr. P]

Mr. P - admittedly, your ping requests on the 10th hop to the server itself are astronomically high. BUT, your entire path is just as high! Based on your path and all results, I would say the final time is right in line as it should be. You'll know the problem is the server when the final result is MUCH higher than the rest of the hops. I'm afraid to say, you're problem is likely being on dial-up.

I really don't feel I have a problem..tell me though would post #23 show a server problem?

[jimnyc]

2:29pm...I feel like a slug..:laugh2:
Dial-up is great, I can get a nap and never miss a thing. :laugh2:

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 786 ms 907 ms 611 ms ipt-mtce17.dial.aol.com [64.12.8.17]
2 681 ms 601 ms 761 ms iptfarme-mr4-sw0.conc.aol.com [64.12.120.158]
3 983 ms 521 ms 902 ms wc2-mtc-ae4.router.aol.com [172.20.201.76]
4 716 ms 521 ms 541 ms dar2-mtc-G1-1-0.atdn.net [172.21.44.73]
5 613 ms 721 ms 521 ms pop2-ash-S1-3-0.atdn.net [66.185.151.97]
6 673 ms 661 ms 962 ms GlobalCrossing.atdn.net [66.185.141.194]
7 721 ms 822 ms 611 ms 64.209.99.62
8 761 ms 440 ms 842 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 908 ms 631 ms 812 ms 209.51.131.90
10 894 ms 1092 ms 1132 ms ewok.nocdirect.com [69.73.181.50]

Looking at post #23 at your request!

While a little higher than the rest, it's really not an unusually high result based on your route. For example, you'll see in my results that the majority of routers will generally respond in the 20-60ms range, but jumps to 200ms when it reaches the server. That's 4-10x increase in response time compared to the rest.

What speed are you connecting at with your dial-up? Have you tried connecting via different numbers to see if the route gets any better? The fact that you're getting over 700ms response time within AOL's own network is disturbing, and appears your problem starts at the outset. Please don't ask me my opinion of AOHELL! Ever give thought to their broadband option if you don't want to leave them?

[Missileman]

Anyone experiencing slowness right now on the board? If so, can someone please run a tracert and let me know the results?


Jim,

My trace found a Truthmatters worm. It repeats the same thing over and over eating up system resources.

[jimnyc]

Wow, now I'm getting pissed. Here's the latest response from their senior admin!


This is the last traceroute you provided:

3 6 ms 7 ms 7 ms dstswr2-vlan2.rh.mmrnny.cv.net [67.83.229.162]
4 * * * Request timed out.
5 8 ms 7 ms 7 ms rtr4-tg10-2.wan.whplny.cv.net [64.15.8.29]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 42 ms 44 ms 44 ms atl-bb1-link.telia.net [80.91.251.86]

which is clearly showing packet lost on several hops on your ISP end. Please provide us your IP address by visiting this page: www.myipaddress.com (http://www.myipaddress.com) so we can take a reverse traceroute.

Let us know if you need further assistance. Now the senior admin is also claiming that the "request timed out" indicates packet loss and is my problem rather than the server. Here's how I did my best to explain it to him, with a perfect example showing him that this is ALWAYS the result, even to another server at their datacenter that responds flawlessly:


With all due respect, the request time out are not indicative of data loss at all. These are simply routers that are configured not to reply to ICMP ping requests.

My IP address is *.*.*.*

If you look back at the entire ticket, you'll see the same spikes in response time from EWOK from datacenters around the country, and those don't go through hops with routers configured not to respond. Additionally, I have provided screenshots of remote monitoring tools showing the same results that also take my connection out of the equation.

Allow me to give you another example. I have another account with Jaguar, a VPS server. My main domain there is massgamez.com - here is a tracert result to there. I have no issue whatsoever with that server, all response times are perfect - AND I still see the same routers not responding. They are just simply configured in that manner. This has absolutely nothing to do with my connection, and routers timing out is absolutely normal in many situations as this.

Tracing route to massgamez.com [69.73.183.192]
over a maximum of 30 hops:

1 2 ms <1 ms <1 ms 192.168.2.1
2 8 ms 6 ms 5 ms 10.120.0.1
3 8 ms 8 ms 8 ms dstswr1-vlan2.rh.mmrnny.cv.net [67.83.229.161]
4 * * * Request timed out.
5 7 ms 12 ms 7 ms rtr4-tg11-2.wan.whplny.cv.net [64.15.8.25]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 43 ms 58 ms 51 ms atl-bb1-link.telia.net [80.91.251.86]
10 194 ms 200 ms 208 ms globalnet-103907-atl-bb1.c.telia.net [213.248.90
.54]
11 28 ms 29 ms 27 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
12 29 ms 28 ms 29 ms 209.51.131.90
13 31 ms 27 ms 32 ms 69.73.182.45
14 28 ms 29 ms 27 ms 69.73.183.192

Trace complete.

[jimnyc]

Jim,

My trace found a Truthmatters worm. It repeats the same thing over and over eating up system resources.

LOL!

I don't know what's more frustrating, TM or the techs responding to me!

[jimnyc]

Mr. P - run it again now if you can as the problem appears to have just resurfaced. Here's my latest results:

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 5 ms 5 ms 7 ms 10.120.0.1
3 7 ms 7 ms 7 ms dstswr2-vlan2.rh.mmrnny.cv.net [67.83.229.162]
4 * * * Request timed out.
5 7 ms 7 ms 7 ms rtr4-tg10-2.wan.whplny.cv.net [64.15.8.29]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 43 ms 43 ms 43 ms atl-bb1-link.telia.net [80.91.251.86]
10 29 ms 29 ms 27 ms globalnet-103907-atl-bb1.c.telia.net [213.248.90
.54]
11 28 ms 29 ms 27 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
12 28 ms 30 ms 33 ms 209.51.131.90
13 203 ms 205 ms 204 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

[Mr. P]

Had to go dial-up when I moved. AOL pops up by default I guess..I hear they bought netscape which is my provider. I go back aways on the net, prodigy, compuserve, BBS boards, the days of dos commands. I'd never willingly go to AOL. PLEASE! I should NEG rep yer sorry ass for that you shit!:laugh2:

[Mr. P]

Mr. P - run it again now if you can as the problem appears to have just resurfaced. Here's my latest results:

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.1
2 5 ms 5 ms 7 ms 10.120.0.1
3 7 ms 7 ms 7 ms dstswr2-vlan2.rh.mmrnny.cv.net [67.83.229.162]
4 * * * Request timed out.
5 7 ms 7 ms 7 ms rtr4-tg10-2.wan.whplny.cv.net [64.15.8.29]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 43 ms 43 ms 43 ms atl-bb1-link.telia.net [80.91.251.86]
10 29 ms 29 ms 27 ms globalnet-103907-atl-bb1.c.telia.net [213.248.90
.54]
11 28 ms 29 ms 27 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
12 28 ms 30 ms 33 ms 209.51.131.90
13 203 ms 205 ms 204 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.


HUH what's the "*"?
Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 134 ms 139 ms 450 ms ipt-dtcc15.dial.aol.com [205.188.70.79]
2 138 ms 139 ms 139 ms iptfarmc-dr2-sw0-vlan3.conc.aol.com [205.188.120
.94]
3 140 ms 139 ms 320 ms wc2-dtc-ae2.net.aol.com [172.18.30.44]
4 140 ms 140 ms 139 ms dar2-dtc-GE1-1-0.net.aol.com [172.18.52.73]
5 150 ms 139 ms 420 ms pop2-ash-S0-3-0.atdn.net [66.185.141.77]
6 140 ms 139 ms 139 ms GlobalCrossing.atdn.net [66.185.141.194]
7 470 ms 159 ms 150 ms 64.209.99.62
8 160 ms 159 ms 159 ms atl-core-g-g1-6.gnax.net [63.247.69.178]
9 160 ms 159 ms 160 ms 209.51.131.90
10 * 320 ms 320 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

[jimnyc]

The "*'s" in my case refer to routers that don't respond to the ping requests, which is normal, even though my host thinks otherwise.

You are seeing the slowdown too, but I suppose they'll claim that you're routing through me to get there! LOL

[jackass]

Jim just didnt want to give out his address...

[jimnyc]

Jim just didnt want to give out his address...

tracert reports don't give out your IP's, although they do give out internal IP's from your ISP. No damage can be done from posting the reports, but admittedly you can get a much clearer picture of where someone is running the route from! I'm not worried, I'm pretty sure you bastards all know I live in NY by now!

[jimnyc]

Can anyone else post results for me so that I can provide them as evidence?

[Mr. P]

Ya know, my problem may just be I live in da south, we are slow down here, ya know. I need a real generator too. Hell, every time that damn donkey stops walkin round his circle my lights go out! I'm lucky though, I got winders 3.1!
Plumbins OK too, just dug a new hole this past saturday. :D

[jackass]

Microsoft(R) Windows DOS
(C)Copyright Microsoft Corp 1990-2001.

C:\DOCUME~1\HP_OWNER>tracert debatepolicy.com

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 21 ms 9 ms 13 ms cpe-075-189-096-001.sc.res.rr.com [75.189.96.1]

3 11 ms 11 ms 11 ms 24.31.194.177
4 15 ms 12 ms 14 ms srp4-0.clmascmhe-rtr1.sc.rr.com [24.31.193.129]

5 12 ms 12 ms 12 ms 24.31.194.126
6 18 ms 30 ms 20 ms ge-3-0-0.chrlncsa-rtr6.southeast.rr.com [24.93.6
4.62]
7 20 ms 17 ms 14 ms pop1-cha-P2-0.atdn.net [66.185.138.77]
8 16 ms 17 ms 16 ms bb1-cha-P3-0.atdn.net [66.185.138.64]
9 20 ms 21 ms 20 ms bb1-atm-P6-0.atdn.net [66.185.152.182]
10 24 ms 27 ms 25 ms pop1-atm-P1-0.atdn.net [66.185.147.193]
11 37 ms 33 ms 37 ms savvis.atdn.net [66.185.150.14]
12 24 ms 20 ms 19 ms 216.89.82.82
13 22 ms 20 ms 20 ms 209.51.131.90
14 22 ms 28 ms 36 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

C:\DOCUME~1\HP_OWNER>

[glockmail]

Tracing route to debatepolicy.com [69.73.181.50]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms -----
2 8 ms 9 ms 9 ms ----
3 10 ms 6 ms 8 ms gig2-3.gnboncbr-rtr1.triad.rr.com [24.28.228.137
]
4 8 ms 7 ms 7 ms srp10-0.gnboncsg-rtr2.triad.rr.com [24.28.224.22
6]
5 11 ms 10 ms 12 ms ge3-1-0.chrlncsa-rtr6.southeast.rr.com [24.93.64
.162]
6 25 ms 30 ms 26 ms pop1-cha-P2-0.atdn.net [66.185.138.77]
7 63 ms 198 ms 201 ms bb1-cha-P3-0.atdn.net [66.185.138.64]
8 24 ms 25 ms 24 ms bb1-atm-P6-0.atdn.net [66.185.152.182]
9 24 ms 24 ms 22 ms pop1-atm-P1-0.atdn.net [66.185.147.193]
10 28 ms 30 ms 28 ms savvis.atdn.net [66.185.150.14]
11 26 ms 24 ms 26 ms 216.89.82.82
12 25 ms 26 ms 25 ms 209.51.131.90
13 195 ms 199 ms 198 ms ewok.nocdirect.com [69.73.181.50]

Trace complete.

[Abbey Marie]

Got this email from my husband when I asked him about the site slowness. I have no idea if this helps, or what it means, Jim, but I know you will.

Hey Babe,
Yes, it all makes sense. It doesn't matter that hops 4, 6, 7, and 8 timed out in the traceroute, and frankly I can't understand how anyone drawing an IT-related paycheck would even mention that.
All that matters is that the last hop (12) before the traceroute got to the server was only 30 milliseconds, but then the final hop when the traceroute actually reached the server was 204 milliseconds. That shows clearly that the slowness is due to that last hop. In other words, the problem is all due to the slow connection between the server and the server's Internet connection, which is IP address 209.51.131.90. The server provider should go check their own ISP, or else go check their server again. (I know the tech said he checked the server and its fine, but based on his lame analysis of the traceroute I wouldn't put too much stock in his statements)

[jimnyc]

Got this email from my husband when I asked him about the site slowness. I have no idea if this helps, or what it means, Jim, but I know you will.

Hey Babe,
Yes, it all makes sense. It doesn't matter that hops 4, 6, 7, and 8 timed out in the traceroute, and frankly I can't understand how anyone drawing an IT-related paycheck would even mention that.
All that matters is that the last hop (12) before the traceroute got to the server was only 30 milliseconds, but then the final hop when the traceroute actually reached the server was 204 milliseconds. That shows clearly that the slowness is due to that last hop. In other words, the problem is all due to the slow connection between the server and the server's Internet connection, which is IP address 209.51.131.90. The server provider should go check their own ISP, or else go check their server again. (I know the tech said he checked the server and its fine, but based on his lame analysis of the traceroute I wouldn't put too much stock in his statements)

Your hubby and I are in 3000% agreement! And the part I bolded is where my frustration stems from. I'm baffled that they would continually mention that these routers timed out, and make a big deal of it, when it's quite common in the industry.

Tell him I said thank you, at least I know there's some competent people left out there! :)

[Abbey Marie]

Your hubby and I are in 3000% agreement! And the part I bolded is where my frustration stems from. I'm baffled that they would continually mention that these routers timed out, and make a big deal of it, when it's quite common in the industry.

Tell him I said thank you, at least I know there's some competent people left out there! :)

You got it. He's a network architect, so I guess you both know what you're talking about. If I ask him about anything work-related, I just get a deluge of acronyms that are meaningless to me. :dunno:

[jimnyc]

You got it. He's a network architect, so I guess you both know what you're talking about. If I ask him about anything work-related, I just get a deluge of acronyms that are meaningless to me. :dunno:

I'm impressed! Didn't know you were married to a fellow geek! :)

Now we have another person we can send questions to when in need! LOL

[glockmail]

Got this email from my husband when I asked him about the site slowness. I have no idea if this helps, or what it means, Jim, but I know you will.

Hey Babe,
Yes, it all makes sense. It doesn't matter that hops 4, 6, 7, and 8 timed out in the traceroute, and frankly I can't understand how anyone drawing an IT-related paycheck would even mention that.
All that matters is that the last hop (12) before the traceroute got to the server was only 30 milliseconds, but then the final hop when the traceroute actually reached the server was 204 milliseconds. That shows clearly that the slowness is due to that last hop. In other words, the problem is all due to the slow connection between the server and the server's Internet connection, which is IP address 209.51.131.90. The server provider should go check their own ISP, or else go check their server again. (I know the tech said he checked the server and its fine, but based on his lame analysis of the traceroute I wouldn't put too much stock in his statements) Hey you let him call you babe? :laugh2:

[jimnyc]

It's a shame that I even had to THINK about giving support, to support, especially their "senior admin" - but I had no choice but to give them this link in my latest update. Pay special attention to the part in bold, which of course supports exactly what I've stated all along.


Understanding a Tracert

The tracert utility determines the route taken to a destination by sending Internet Control Message Protocol (ICMP) echo packets with varying Time-To-Live (TTL) values to the destination. Each router along the path is required to decrement the TTL on a packet by at least 1 before forwarding it, so the TTL is effectively a hop count. When the TTL on a packet reaches 0, the router is supposed to send back an ICMP Time Exceeded message to the source system. The tracert command determines the route by sending the first echo packet with a TTL of 1 and incrementing the TTL by 1 on each subsequent transmission until the target responds or the maximum TTL is reached (usually 30 hops). The route is determined by examining the ICMP Time Exceeded messages sent back by the intermediate routers.
Using tracert

If you wanted to do a tracert to genealogy.org and save the results in a text file, the syntax of the command would be:

tracert genealogy.org >tracert.txt

The results returned might look something like those below:

Tracing route to genealogy.org [207.167.87.50] over a maximum of 30 hops:
1 257 ms 186 ms 183 ms 192.168.255.254
2 195 ms 177 ms 246 ms 199.70.72.65
3 317 ms 187 ms 241 ms 199.70.127.233
4 212 ms 443 ms 281 ms 199.70.95.249
5 * * * Request timed out.
6 190 ms 187 ms 309 ms Vienna5.VA.ALTER.NET [137.39.156.25]
7 194 ms 193 ms 198 ms Fddi0-0.CR2.TCO1.ALTER.NET [137.39.11.20]
8 265 ms 325 ms 273 ms 189.Hssi6-0.CR2.SCL1.Alter.Net [137.39.69.174]
9 337 ms 302 ms 277 ms 107.Hssi0-0.BR1.NUQ1.Alter.Net [137.39.70.125]
10 271 ms 396 ms 270 ms T3-CRL-SFO-01-H1/0.US.CRL.NET [198.32.136.10]
11 311 ms 267 ms 309 ms T3-CRL-SFO-01-H3/0.US.CRL.NET [149.20.64.19]
12 263 ms 309 ms 261 ms E0-CRL-SFO-05-E0X0.US.CRL.NET [165.113.55.5]
13 430 ms 281 ms 357 ms znet-gw.ex.us.crl.net [165.113.120.14]
14 * 434 ms * znet-gw.ex.us.crl.net [165.113.120.14]
15 * * * Request timed out.
16 295 ms 356 ms 301 ms genealogy.org [207.167.87.50]

Understanding the results:

The first column is the hop number, which is the Time-To-Live (TTL) value set in the packet.

Each of the next three columns contains the round-trip times in milliseconds for an attempt to reach the destination with the TTL value.

The fourth column is the host name (if it was resolved) and IP address of the responding system.

In the results you will see the comment, "over a maximum of 30 hops". All this means is that the diameter of the Internet is roughly 30 hops and, therefore, many trace routes will only go that far out in trying to reach a destination.

This first hop is to the modem that answered your call and typically takes 200 to 300 milliseconds.

An asterisk, "*", followed by the words "request timed out" is not out of the ordinary. If the tracert had stopped here and continued to respond with "request timed out", then it might have been indicative of a problem. In the above example, the first "request timed out" is where the interface between our network and the rest of the Internet lies. The asterisk "*" is a normal consequence of our security implementation on that junction.

Generally, a response time of less than 500 milliseconds is considered acceptable. If the example above had indicated results larger than that, then there might have been a problem router at that point in the network.

The first 4 or 5 hops are internal to our network. These hops will not resolve to a domain name.

Hop 6 in the above example is where we connect to alter.net (UUNET). The Vienna5.VA.ALTER.NET hub is commonly referred to MAE east. This is a major junction point for the Internet at large. If you are having problems at this hop and live on the east coast, then you can pretty much count on having problems getting anywhere on the Internet. There are similar hubs on the west coast as well.

Hop 10 is where alter.net connects with crl.net (CRL Network Services) on router T3-CRL-SFO-01-H1/0.US.CRL.NET.

Finally, on hop 16, the connection to genealogy.org is made. The entire trip went through our network (4 hops), alter.net (4 hops), crl.net (5 hops) and genealogy.org (1 hop).


http://www.wurd.com/misc_tracert.php

[Abbey Marie]

Hey you let him call you babe? :laugh2:

What does your wife let you call her? Your Higness? :laugh2:

[glockmail]

What does your wife let you call her? Your Higness? :laugh2: Close. :bow3: