30 replies to this topic

[-Storm(BS)-]

once i do that.. what do i do?

[Jac3624]

post the results.

[-Storm(BS)-]

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Travis>tracert moonts.sytes.net

Tracing route to moonts.sytes.net [64.34.179.226]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 20 ms 10 ms 10 ms 10.101.160.1
3 13 ms 10 ms 15 ms gig11-0-0-2042.tampfledc-rtr1.tampflrdc.rr.com [
65.32.25.62]
4 13 ms 13 ms 16 ms 653213hfc134.tampabay.res.rr.com [65.32.13.134]

5 17 ms 16 ms 14 ms ae2s0-orld71-cbr1.noc.bhn.net [72.31.220.1]
6 58 ms 60 ms 55 ms xe-11-0-0.bar1.Orlando1.Level3.net [4.79.118.41]

7 64 ms 55 ms 55 ms ae-8-8.ebr1.Atlanta2.Level3.net [4.69.137.150]
8 62 ms 59 ms 64 ms ae-73-70.ebr3.Atlanta2.Level3.net [4.69.138.20]

9 58 ms 55 ms 61 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

10 96 ms 64 ms 71 ms ae-81-81.csw3.Washington1.Level3.net [4.69.134.1
38]
11 54 ms 57 ms 69 ms ae-3-89.edge2.Washington3.Level3.net [4.68.17.14
0]
12 60 ms 63 ms 71 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
13 59 ms 72 ms 76 ms 216.187.120.253
14 133 ms 118 ms 125 ms 216.187.120.230
15 113 ms 106 ms 101 ms wgn50.wolfservers.com [64.34.179.226]

Trace complete.

C:\Users\Travis>

[DerRaucher]

Mhhh, the diff. of hop 13 and 14 is little bit crazy. The Jump of the Ping in the Network-Area 216.187.120.253 - 216.187.120.250 is little bit high. Could be a Router-Problem. Please correct me if im wrong.

Edited by DerRaucher, 02 November 2010 - 05:47 PM.

[Jac3624]

I have to agree with DerRaucher on this one. A router issue seems like the best bet.


Here's my tracert as a comparison. Note that at 18 & 19 I get "request timed out"

Tracing route to moonts.sytes.net [64.34.179.226]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 17 ms 7 ms ge-9-1-ur01.oakdale.mn.minn.comcast.net [68.85.166.145]
4 8 ms 7 ms 8 ms te-8-3-ur02.oakdale.mn.minn.comcast.net [68.87.174.110]
5 7 ms 23 ms 7 ms te-2-1-ur02.whitebear.mn.minn.comcast.net [68.87.174.137]
6 7 ms 7 ms 7 ms te-8-3-ur01.whitebear.mn.minn.comcast.net [68.87.174.133]
7 9 ms 7 ms 10 ms te-2-1-ur02.shoreview.mn.minn.comcast.net [68.87.174.129]
8 17 ms 7 ms 8 ms te-8-3-ur01.shoreview.mn.minn.comcast.net [68.87.174.125]
9 7 ms 7 ms 8 ms te-0-3-0-2-ar01.crosstown.mn.minn.comcast.net [68.87.174.177]
10 18 ms 18 ms 18 ms te-1-1-0-4-cr01.chicago.il.ibone.comcast.net [68.86.95.5]
11 17 ms 17 ms 17 ms xe-9-3-0.edge1.Chicago2.Level3.net [4.71.248.21]
12 18 ms 18 ms 18 ms vlan52.ebr2.Chicago2.Level3.net [4.69.138.190]
13 57 ms 62 ms 48 ms ae-6-6.ebr2.Washington12.Level3.net [4.69.148.145]
14 46 ms 48 ms 46 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
15 59 ms 56 ms 50 ms ae-92-92.csw4.Washington1.Level3.net [4.69.134.158]
16 48 ms 47 ms 61 ms ae-4-99.edge2.Washington3.Level3.net [4.68.17.204]
17 47 ms 47 ms 58 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.234.6]
18 * * * Request timed out.
19 * * * Request timed out.
20 48 ms 47 ms 48 ms wgn50.wolfservers.com [64.34.179.226]

Trace complete.

[DerRaucher]

And b4 you ask, no you cant change anything on that. Just try to connect the next days.
They will fix it surely within 2-3 days.

[-Storm(BS)-]

Okay, thanks for the help. So much.

[DerRaucher]

Player is now in TS. Prob is solved.

[-Storm(BS)-]

All is fixed and for anyone that has the same problem, all i can say is to just wait it out. let it sit for 2 days and its magically fixed Thanks to all that helped me out!

[Jac3624]

Glad it all worked out.

[Warrior124]

Problem solved. Topic closed.