Jump to content

Major connection issues. Unable to get past certain point in traceroute.


Valen Planer
 Share

You are about to reply to a thread that has been inactive for 4286 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

We've just moved to Canada and I can log into SL but can't see names, avatars, or many other things after logging in. 

See the following traceroute and more info after:

Last login: Thu Jul 12 21:44:25 on console
trThomass-iMac:~ Smoo$ traceroute 216.82.30.26
traceroute to 216.82.30.26 (216.82.30.26), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 3.993 ms 1.877 ms 1.810 ms
2 10.125.148.1 (10.125.148.1) 15.128 ms 9.982 ms 10.194 ms
3 69.63.255.77 (69.63.255.77) 15.565 ms 32.967 ms 38.877 ms
4 24-52-255-90.cable.teksavvy.com (24.52.255.90) 9.680 ms
24-52-255-26.cable.teksavvy.com (24.52.255.26) 10.543 ms
24-52-255-90.cable.teksavvy.com (24.52.255.90) 14.664 ms
5 24-52-255-89.cable.teksavvy.com (24.52.255.89) 16.014 ms 13.479 ms 16.785 ms
6 tge6-1.fr3.yyz.llnw.net (208.111.134.237) 13.418 ms 14.286 ms 23.101 ms
7 ve5.fr4.yyz.llnw.net (69.28.171.142) 23.133 ms 23.173 ms 16.123 ms
8 tge22-4.fr3.ord.llnw.net (69.28.189.137) 40.321 ms 36.842 ms 41.313 ms
9 mpr1.ord7.us (206.223.119.86) 35.319 ms 33.393 ms 33.670 ms
10 xe-1-3-0.cr1.ord2.us.above.net (64.125.30.142) 33.098 ms 34.089 ms 33.519 ms
11 xe-3-0-0.cr1.lga5.us.above.net (64.125.24.37) 45.446 ms 44.037 ms 45.987 ms
12 xe-0-0-0.cr2.lga5.us.above.net (64.125.29.42) 44.493 ms 45.424 ms 43.179 ms
13 xe-2-2-0.cr2.dca2.us.above.net (64.125.26.105) 67.906 ms 48.740 ms 50.203 ms
14 xe-0-0-0.mpr1.iad6.us.above.net (64.125.28.189) 50.557 ms 51.008 ms 51.575 ms
15 64.124.65.122.customer.above.net (64.124.65.122) 51.682 ms 49.547 ms 50.625 ms
16 * * *

 

I was able to run a traceroute from another point in Canada using tera-byte.com/cgi-cin/nph-trace?216.82.30.26 and it had the same issues. This seems to clear our computers, router, and ISP as being the cause, and our own ISP also verified this via tech support. They told us to contact LL and LL told us to call the ISP, so this leaves me unable to use SL anymore with no one offering any help.

 

Does anyone have any input that can help me resolve this? Thanks in advance!

 
Link to comment
Share on other sites

I think I am in the same, or nearly the same situation, without any assistance.

Could I get some assistance on my SL problem of not being able to log in most times,  and when I do, nothing works?  The error message I get when not being able to log in says “we’re not able to log you in, check your internet or there is a problem with SL Servers.”  When I can eventually log in sometimes, I have no contacts, no groups, no voice capability, no call buttons, no radar, no camera views, no streaming music, and cannot tp to anywhere else.  This started happening July 13th, and I can’t seem to get any assistance.  I have tried 3 browsers and 2 computers with all the same results.  SL worked fine until the evening of July 13th.  I’m losing DJ money every day,  I need some thoughts on what the problem might be, and a fix of the problem asap.

Link to comment
Share on other sites

I have seen the patttern of partial fails before.  At least twice, it turned out to be a router failure.  SL uses ports not commonly used but other  internet progams.  The problem was resolved when I bypassed the router and got a new router. Here is some more info:

Login fails? Lots of logouts? Summary 

http://virtualoutworlding.blogspot.com/2011/12/kit-login-fails-lots-of-logouts-summary.html

TKR


Link to comment
Share on other sites

I've actually already read that article and it doesn't give me any useful information. I tried the usual suggestions like it makes (unplug router, etc) but it's made no difference. I've also opened the additional ports listed but no luck.

The tracerouts i've  run seem to indiciate the problem isn't with my computer or router, as mentioned in the original post.

 

Also, I have to remote desktop to another computer 12 hours away to be able to access the SL forums. They won't load on my computer, but just give me a loading bar.

Link to comment
Share on other sites

Include your tracert outputs in a trouble ticket to SL Support.

Send the Same information to your ISP and ask for help.

Since the problem is neither at SL or your end of the communication link, there is little you can do about it. The problem has to be worked out by those that have some pull with the backbone providers.

Before firing off the complaints check through the troubleshooting steps to see if you have missed anything.

Troubleshoot Your #SL Connection

Link to comment
Share on other sites

  • 2 weeks later...

This is a common problem that seems to vary from day to day. I am on the east coast and regularly can not log in with the LL viewer as it has now grown to include too much overhead. Firestorm loads a little better and when all fails I just use the Cool VL viewer which never seems to have a problem. Of course it does not allow the loading of mesh but does see them.

 

This is also a problem with companys that centralize their servers in one geographic location. I realize it is expensive to maintain alternate server locations but Second Life has grown to the point that other locations are required for decent service.

 

Speed tests and pings to their locations are always high lately. On a 20 meg cable line I get 200 ms pings regularly and MBPS readouts of .9 to 6 hardly cable speeds. On the other hand anything east of Chicago give very good pings and sppeds ( 40ms and 25 MBPS) so it appears that the server locations play a large part in this problem

Link to comment
Share on other sites

  • 1 month later...

The problems seem to be in above.net as the following appeared after taking my router out of the equation (modem reset).

$ traceroute www.secondlife.com
traceroute to secondlife.com (216.82.2.17), 64 hops max, 52 byte packets
1 10.17.136.1 (10.17.136.1) 101.668 ms 34.941 ms 29.825 ms
2 vl7.aggr1.lnh.md.rcn.net (208.59.202.193) 33.008 ms 72.923 ms 34.771 ms
3 tge0-1-0-0.core2.lnh.md.rcn.net (207.172.15.19) 32.202 ms 132.537 ms 48.403 ms
4 tge0-1-0-1.core2.chgo.il.rcn.net (207.172.19.237) 109.543 ms 81.606 ms 63.161 ms
5 bdle2.border1.eqnx.il.rcn.net (207.172.15.196) 98.202 ms
bdle3.border1.eqnx.il.rcn.net (207.172.15.212) 53.252 ms
bdle2.border1.eqnx.il.rcn.net (207.172.15.196) 64.165 ms
6 mpr1.ord7.us (206.223.119.86) 65.614 ms 58.212 ms 170.576 ms
7 * xe-1-3-0.cr1.ord2.us.above.net (64.125.30.142) 53.478 ms 62.272 ms
8 xe-0-2-0.cr1.dfw2.us.above.net (64.125.30.61) 87.058 ms 89.530 ms 89.651 ms
9 xe-0-0-0.cr2.dfw2.us.above.net (64.125.30.74) 98.107 ms 81.437 ms 83.932 ms
10 xe-7-2-1.er2.dfw2.us.above.net (64.125.30.97) 65.542 ms 63.407 ms 78.403 ms
11 64.124.146.2.allocated.above.net (64.124.146.2) 76.633 ms 84.993 ms 66.478 ms
12 * * *
13 vip.www-dfw.secondlife.com (216.82.2.17) 106.195 ms 79.945 ms 80.785 ms
$

This one is even MORE interesting ...

$ traceroute sim8509.agni.lindenlab.com
traceroute to sim8509.agni.lindenlab.com (216.82.39.68), 64 hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 1.250 ms 0.142 ms 0.120 ms
2 10.17.136.1 (10.17.136.1) 29.515 ms 8.099 ms 8.603 ms
3 vl7.aggr1.lnh.md.rcn.net (208.59.202.193) 8.493 ms 12.562 ms 20.433 ms
4 tge0-0-0-0.core2.lnh.md.rcn.net (207.172.15.3) 10.111 ms 10.136 ms 22.369 ms
5 tge0-1-0-1.core2.chgo.il.rcn.net (207.172.19.237) 48.510 ms 38.050 ms 35.939 ms
6 bdle2.border1.eqnx.il.rcn.net (207.172.15.196) 47.839 ms
bdle3.border1.eqnx.il.rcn.net (207.172.15.212) 56.272 ms
bdle2.border1.eqnx.il.rcn.net (207.172.15.196) 38.626 ms
7 mpr1.ord7.us (206.223.119.86) 33.042 ms 70.776 ms 45.830 ms
8 64.125.22.209 (64.125.22.209) 57.532 ms 31.344 ms 34.139 ms
9 xe-0-2-0.cr1.dfw2.us.above.net (64.125.30.61) 59.319 ms 60.282 ms 61.537 ms
10 xe-2-1-0.cr1.iah1.us.above.net (64.125.30.57) 75.895 ms 66.579 ms 75.702 ms
11 xe-1-0-0.cr2.iah1.us.above.net (64.125.30.70) 70.915 ms 70.926 ms 70.721 ms
12 xe-0-1-0.mpr4.phx2.us.above.net (64.125.28.73) 87.605 ms 89.013 ms 94.817 ms
13 xe-0-0-0.mpr3.phx2.us.above.net (64.125.27.41) 88.111 ms 88.548 ms 89.556 ms
14 64.124.161.254.allocated.above.net (64.124.161.254) 93.425 ms 95.176 ms 95.046 ms
15 * * *
16 * * *
17 * * *
18 * * * ...

 

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 4286 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...