After i had my computer rebooted, and since then my ping sim is always over 70 000 msec, help!

[Marianne Fairlock]

Hi everyone, i would really appreciate some help here... I have seen ping sims questions, but what has been suggested does not help me.  
I can log in perfectly fine, and everything rezzes around the.  I can see the sim, and my avatar looks perfect.  But i CAN NOT move at all.  My ping sim is (when low) around 1500 msec, and has reached 90 000.  
My internect conection works fine, and it dosen't matter if i have my computer connected via cable to the modem, or wireless... is the same problem.  This started after i had my computer reformat, i had Windows installed again, and everything works perfect, the only thing that got affected in a negative way is Second Life :( 
I use firestorm viewer, version 4.3.1.31155
I am using Windows 7 Home Edition, and would appreciate any and all help! 

[Rolig Loon]

WHOA!  That's a huge ping time.  I'm surprised you can log on.  OK, here's how you can start to get a handle on what's happening......  Read Nalates's blog at http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/ .  There's a lot in there, but don't get intimidated.  You'll notice that one of the things she recommends is a tracert test of all the connections between your computer and SL's servers. If you do that, you'll be able to see where your connection may have weak spots.  To get a trace in Windows 7, click the Start button and then, in the search box, type command.  Click on Command Prompt and then type in the command tracert sim5466.agni.lindenlab.com. That's the route to the server that my sim is on in Linden Lab, but you can get your sim's IP address by looking in Help >> About Second Life.  Here's what my trace looks like (with the first couple of lines blanked out so you can't see where I am in RL) :

Tracing route to sim5466.agni.lindenlab.com [216.82.22.109] over a maximum of 30 hops:

  1     *        *        *     Request timed out.

  2    10 ms    10 ms     6 ms  ----------------------------------------------

  3    19 ms    19 ms    18 ms  ----------------------------------------------

  4    20 ms    18 ms    23 ms  ----------------------------------------------

  5    19 ms    19 ms    19 ms  sl-st20-chi-0-0-0.sprintlink.net [144.232.19.144]

  6    24 ms    21 ms    22 ms  144.232.8.114

  7    41 ms    39 ms    41 ms  vlan52.ebr2.Chicago2.Level3.net [4.69.138.190]

  8    41 ms    39 ms    41 ms  ae-14-14.ebr1.Dallas1.Level3.net [4.69.151.118]

  9    41 ms    41 ms    39 ms  ae-81-81.csw3.Dallas1.Level3.net [4.69.151.149]

 10    51 ms    40 ms    42 ms  ae-31-80.car1.Dallas1.Level3.net [4.69.145.131]

 11    41 ms    41 ms    46 ms  LINDEN-RESE.car1.Dallas1.Level3.net [8.9.232.94]

 12    44 ms    54 ms    53 ms  sw-core1-73.dfw.lindenlab.com [216.82.7.174]

 13    44 ms    42 ms    42 ms  sim5466.agni.lindenlab.com [216.82.22.109]

You see that the first few hops, closest to my own computer, were very fast (ping times under 20 milliseconds).  Jumps farther away were slower, but still mostly under 50 milliseconds.  The slowest was right at Linden Lab's front door, and that was still only 54 milliseconds.  In other words, signals are travelling between me and SL very quickly, with no really slow spots.  If you do the same thing, you may be able to see where the slowest parts of your route to SL are.  Read Nalates's blog to see how to use that information.