Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: FGBullet on January 14, 2012, 02:57:24 PM
-
About 2 weeks ago I started discoing approximately every 45 - 60 minutes.
I ran pingplotter and noticed 40% and 100% packet loss on two of the hops. I've attached the text from the pingplotter trace. Hopefully this will address why I'm discoing.
Target Name: www.hitechcreations.com
IP: 70.85.193.18
Date/Time: 1/14/2012 2:48:11 PM to 1/14/2012 2:50:26 PM
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 31 ms 23 ms 28 ms 27 ms 21 ms 22 ms 14 ms 40 ms 40 ms 28 ms [96.19.192.1]
3 12 ms 11 ms 12 ms 32 ms 29 ms 12 ms 30 ms 15 ms 33 ms 13 ms [192.168.26.77]
4 19 ms 17 ms 22 ms 19 ms 20 ms 18 ms 20 ms 44 ms 38 ms 35 ms [192.168.100.226]
5 65 ms 59 ms 34 ms 39 ms 34 ms 36 ms 35 ms 82 ms 34 ms 35 ms xe-5-0-3.edge5.Atlanta2.Level3.net [4.28.26.5]
6 36 ms 55 ms 56 ms 36 ms 36 ms 56 ms 38 ms 42 ms 38 ms 40 ms ae-1-51.edge4.Atlanta2.Level3.net [4.69.150.13]
7 40 ms 36 ms 37 ms 55 ms 36 ms 37 ms 35 ms 71 ms 41 ms 37 ms te2-5.bbr01.tl01.atl01.networklayer.com [4.59.12.66]
8 37 ms 79 ms 36 ms 55 ms 56 ms 34 ms 37 ms 71 ms 38 ms 49 ms ae7.bbr01.tl01.atl01.networkl ayer.com [173.192.18.172]
9 42 ms 44 ms 39 ms 65 ms 41 ms 44 ms 58 ms 87 ms 80 ms * ae13.bbr02.eq01.dal03.network layer.com [173.192.18.134]
10 40 ms 41 ms 42 ms 45 ms 43 ms 42 ms 42 ms 73 ms 46 ms 42 ms po32.dsr01.dllstx3.networklay er.com [173.192.18.229]
11 * * * * * * * * * * [-]
12 41 ms 43 ms 52 ms 41 ms 43 ms 43 ms 40 ms 80 ms 53 ms 48 ms po1.car03.dllstx5.networklaye r.com [70.87.254.18]
13 42 ms 40 ms 46 ms 44 ms 63 ms 42 ms 80 ms 89 ms 63 ms 59 ms 12.c1.5546.static.theplanet.c om [70.85.193.18]
Ping statistics for www.hitechcreations.com
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 40ms, Maximum = 89ms, Average = 56ms
Thanks,
Bullet
-
how old is your router?
-
About 8 months old. I took the router out of the equation and was still discoing.
Thanks...
-
Your pinging the wrong server. The LW server is 206.16.60.41 Run the ping to that and see what you get.
-
Your pinging the wrong server. The LW server is 206.16.60.41 Run the ping to that and see what you get.
What he said.
-
Hmmmmm, the Technical FAQ page states to trace to www.hitechcreations.com??? :headscratch:
The disconnects started approximately 2 weeks ago and I disco every 45-60 minutes. I've tried cable directly into computer, (eliminating the router) and new ethernet cables.
Here's the results after pinging to 206.16.60.41
Target Name: N/A
IP: 206.16.60.41
Date/Time: 1/15/2012 11:53:44 PM to 1/15/2012 11:55:59 PM
1 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms [192.168.1.1]
2 26 ms 24 ms 27 ms 47 ms * 15 ms 22 ms 27 ms 21 ms 47 ms [96.19.192.1]
3 12 ms * 10 ms 51 ms * 55 ms 11 ms 12 ms * 30 ms [192.168.26.77]
4 21 ms 32 ms 20 ms 26 ms * 30 ms 19 ms 28 ms 20 ms 39 ms [192.168.100.50]
5 35 ms 36 ms 57 ms 37 ms * 36 ms 38 ms 57 ms 37 ms 37 ms xe-5-0-3.edge5.Atlanta2.Level3.net [4.28.26.5]
6 37 ms 37 ms 38 ms 39 ms * 37 ms 54 ms 44 ms 45 ms 36 ms att-level3.atlanta2.level3.net [4.68.62.226]
7 43 ms 43 ms 42 ms 62 ms * 43 ms 45 ms 44 ms 62 ms 42 ms cr1.attga.ip.att.net [12.122.141.234]
8 64 ms 45 ms 43 ms 43 ms * 46 ms 83 ms 42 ms 46 ms 81 ms cr2.dlstx.ip.att.net [12.122.28.174]
9 122 ms 49 ms 41 ms 38 ms 40 ms 41 ms 62 ms 40 ms 40 ms 49 ms ggr1.dlstx.ip.att.net [12.122.138.1]
10 42 ms N/A 43 ms N/A 39 ms N/A N/A N/A N/A 42 ms [12.122.251.66]
11 41 ms 42 ms * 42 ms 41 ms 59 ms 42 ms 74 ms 41 ms 44 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
12 42 ms 62 ms 43 ms 79 ms 39 ms 60 ms 42 ms 40 ms 43 ms 42 ms [206.16.60.41]
Ping statistics for 206.16.60.41
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 39ms, Maximum = 79ms, Average = 49ms
-
You need to contact your ISP about this one. Your problems are all over the first couple of hops, which appear to be multiple NAT routers having issues. Send that data to them as well.
Be forewarned, the first level support contacts will only test your local Internet connection, and they will probably tell you everything is fine. You need to reach an actual network support person and not even bother dealing with the first guys that answer the phone.
-
Thanks, I'll give them a call soon.