[CLUE-Tech] CLUE: DSL - PCISYS
Richard Knechtel
rknech at pcisys.net
Wed Jul 3 12:55:19 MDT 2002
Well I did some network troubleshooting. Thanks for the info on that.
Here is my trace:
# IP address Host name Round trip time
-------------------------------------------------------------------------------
1 10.0.0.1 Unavailable 1 ms
2 216.229.32.177 cartman.pcisys.net 20 ms
3 157.130.162.57 Serial2-11.GW7.DEN1.ALTER.NET 28 ms
4 152.63.93.6 160.at-5-0-0.XR1.SLT4.ALTER.NET 41 ms
5 152.63.1.210 0.so-0-1-0.TL1.SLT4.ALTER.NET 48 ms
6 152.63.0.181 0.so-4-0-0.TL1.DFW9.ALTER.NET 87 ms
7 152.63.0.194 0.so-7-0-0.XL1.DFW9.ALTER.NET 72 ms
8 152.63.101.250 0.so-7-0-0.XR1.DFW9.ALTER.NET 72 ms
9 152.63.100.169 185.ATM6-0.BR3.DFW9.ALTER.NET 78 ms
10 144.232.18.29 Unavailable 105 ms
11 144.232.18.242 sl-bb20-ana-8-0.sprintlink.net 124 ms
12 144.232.20.101 sl-bb24-sj-10-0.sprintlink.net 107 ms
13 144.232.20.70 sl-st20-sj-15-1.sprintlink.net 108 ms
14 144.223.242.6 sl-supernews-2-0.sprintlink.net 139 ms
15 216.168.3.40 corp.supernews.com 139 ms
It seems IP 144.232.18.29 (Sprint) is the deathbringer here. everything
gets bad from then on out.
I am looking at americanisp.net (their pricing chart is a little confusing,
but a phone call should clear that up.) and going to look at
forethought.net . I used to have PCI for dialup years ago and they were
very good. Seems like things change.
At 06:56 PM 7/2/02 -0600, you wrote:
>Richard Knechtel wrote:
>>Does anyone else have DSL with PCI Systems?
>>Since Friday I have had SERIOUS issues with my DSL. Sending/receiving
>>emails takes forever, trying to browse web pages is god awful slow! And
>>forget trying to use Usenet newsgroups! I am down to 56K modems speeds
>>or less on my 256K DSL line. I have contcted PCI twice via email and
>>called them twice. They don't seem to have a clue! (no pun intended). I
>>am wondering if anyone else is using PCI for their DSL and having
>>problems as well. Or is it just me???
>
>I assume your getting slow connections to many different places so you
>know it's your end. If you can hit someplace you know is unloaded (like
>work after hours) that may help troubleshoot.
>
>Here are some things you can try to see what the problem is.
>
>Use nslookup to check dns. The first request may be slow, but repeating
>it should return quickly.
>
>Use ping to see if any packets get dropped.
>
>Use traceroute to see if there are any very slow hops. If there are some
>close to you, it's likely to be your ISP.
>
>Use ethereal or tcpdump to look at the packets. A lot of retransmissions
>indicate network problems.
>
>I'm no expert at network analysis, but maybe you'll find something that
>jumps out at you.
>
>Dave
>
>_______________________________________________
>CLUE-Tech mailing list
>CLUE-Tech at clue.denver.co.us
>http://clue.denver.co.us/mailman/listinfo/clue-tech
More information about the clue-tech
mailing list