Jump to content
  • 0

I am disconnecting too often


ozcan
 Share

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

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

Question

Hello.I am Kheiron from SL.

I am living this problem for years and it's really boring.I had tried many solutions from the internet but didn't work.

 

First I want to say I have a good connection and a good computer a good graphic card and an updated driver.But I am crashing whenever I go somewhere has people on it.Actually, I am not sure if it's about people or not it maybe about objects too.But I don't crash or disconnect on protected lands like Hatton I know this.

I am living in 2 different houses one for summer and one for winter.In the winter one I have worse internet connection but I never disconnect like that.Also in summer one I have a good connection speed I can play other game perfectly but not the SL.I always disconnect.

I am using same desktop computer in both houses.I am connected via LAN

 

Operating System: Windows 8.1 Pro 64-bit (6.3, Build 9600) (9600.winblue_ltsb.170613-0600)
           Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
       System Model: System Product Name
               BIOS: 0318
          Processor: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 CPUs), ~4.0GHz
             Memory: 16384MB RAM
Available OS Memory: 16318MB RAM

Card name: NVIDIA GeForce GTX 970
       Manufacturer: NVIDIA
          Chip type: GeForce GTX 970

This is my speed test results

http://beta.speedtest.net/result/6486775592

and this is the screen I get

025c5233b955f31de09eacc2eeda88b9.thumb.png.0b1514d6d401c7677fb2f277b9bfd9fc.png

 

Please find me a solution

Thanks

Link to comment
Share on other sites

8 answers to this question

Recommended Posts

  • 0
2 minutes ago, Alwin Alcott said:

i guess stability of your connection ... speed says not a lot. Can be perfect now and hopeless package loss in 2 minutes.

Open the performance statistic and see what happens (ctr-shift-1) when you near to crash.

here is the screenshot for you

d5d7302756d0c8c4121c037e605fe33e.png

Link to comment
Share on other sites

  • 0
15 minutes ago, ozcan said:

here is the screenshot for you

... packet loss 2.5 % .. SL can't handle that.

It's your connection, but where ...  the only thing you can do is restart your modem/router. If it's not caused there you perhaps can contact your ISP to investigate.

 

and not sure if you do, but go wired.

 

Edited by Alwin Alcott
  • Like 2
Link to comment
Share on other sites

  • 0

Having a good Internet connection is not the same as having a good connection to the SL servers.

The Computer info you provided is good but we need more. Use the viewer's HELP->ABOUT... to collect the info we need.

Your packet loss is high. You can look in the SecondLife.log file to see how bad. At the end of the file is a summary of the session with network information. Provided the viewer shuts down and does not crash the summary will be there.

Quote

Run time:    25533.846 seconds
Incoming:
Total bytes received:                 222132546 (69.60 kbits per second)
Total packets received:                  729331 (28.56 packets per second)
Average packet size:                        305 bytes
Total reliable packets:                  530822 (72.78%)
Total compressed packets:                154583 (21.20%)
Total compression savings:             51128700 bytes
Avg comp packet savings:                    330 ( 1.71 : 1)
Avg overall comp savings:                    70 ( 1.23 : 1)

Outgoing:
Total bytes sent:                      18454230 ( 5.78 kbits per second)
Total packets sent:                      269779 (10.57 packets per second)
Average packet size:                         68 bytes
Total reliable packets:                   14171 ( 5.25%)
Total compressed packets:                     0 ( 0.00%)
Total compression savings:                    0 bytes
Avg comp packet savings:                      0 ( 0.00 : 1)
Avg overall comp savings:                     0 ( 1.00 : 1)

SendPacket failures:                          0
Dropped packets:                            355
Resent packets:                               2
Failed reliable resends:                      0
Off-circuit rejected packets:                 0
On-circuit invalid packets:                   0

 

So, 355 of 729,331 were lost in my last session. 0.049% compared to your 2.5% or 51 times more loss than I experience. So, in actuality, your connection to the SL servers sucks. Now you need to figure out if it is your computer, its connection to your gateway/router, to your ISP, their connection to the backbone provider, the Backbone to the Linden internal network, the Linden network to the host server, or the host server.

Follow these steps: http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/

  • Like 2
Link to comment
Share on other sites

  • 0
On 26.07.2017 at 7:07 PM, Nalates Urriah said:

Having a good Internet connection is not the same as having a good connection to the SL servers.

The Computer info you provided is good but we need more. Use the viewer's HELP->ABOUT... to collect the info we need.

Your packet loss is high. You can look in the SecondLife.log file to see how bad. At the end of the file is a summary of the session with network information. Provided the viewer shuts down and does not crash the summary will be there.

So, 355 of 729,331 were lost in my last session. 0.049% compared to your 2.5% or 51 times more loss than I experience. So, in actuality, your connection to the SL servers sucks. Now you need to figure out if it is your computer, its connection to your gateway/router, to your ISP, their connection to the backbone provider, the Backbone to the Linden internal network, the Linden network to the host server, or the host server.

Follow these steps: http://blog.nalates.net/2011/10/26/troubleshoot-your-sl-connection/

This is What I Have as ABOUT screen

 

Second Life 5.0.6.326589 (Second Life Release edu)
Release Notes

You are at 116.6, 115.6, 1.9 in Hatton located at sim9204.agni.lindenlab.com (216.82.42.140:13025)
SLURL: http://maps.secondlife.com/secondlife/Hatton/117/116/2
(global coordinates 262,261.0, 252,276.0, 1.9)
Second Life RC BlueSteel 17.07.11.327548
Release Notes

CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (4008 MHz)
Memory: 16318 MB
OS Version: Microsoft Windows 8.1 64-bit  (Build 9600)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 970/PCIe/SSE2

Windows Graphics Driver Version: 22.21.0013.8494
OpenGL Version: 4.5.0 NVIDIA 384.94

Window size: 1920x1017
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 1000kbit/s
LOD factor: 1.125
Render quality: 2 / 7
Advanced Lighting Model: Disabled
Texture memory: 512MB
VFS (cache) creation time: January 09 2017 02:24:03

J2C Decoder Version: KDU v7.2
Audio Driver Version: FMOD Ex 4.44.31
LLCEFLib/CEF Version: 1.5.3-(CEF-WIN-3.2526.1347-32)
LibVLC Version: 2.2.4
Voice Server Version: Vivox 4.7.0005.25982

Packets Lost: 59/1,294 (4.6%)
July 28 2017 07:49:51

 

Those are  the results on cmd prompt(I cannot understand anything by looking this so I copied it ) ;

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Kheiron>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\Users\Kheiron>tracert 216.82.45.183

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

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     3 ms     2 ms     3 ms  host-195-142-218-1.reverse.superonline.net [195.
142.218.1]
  3     4 ms     4 ms     2 ms  10.36.120.105
  4    19 ms    18 ms    18 ms  10.36.6.150
  5    17 ms    14 ms    15 ms  10.38.218.69
  6    19 ms    16 ms    14 ms  10.38.219.34
  7    17 ms    14 ms    15 ms  10.38.218.242
  8    16 ms    15 ms    17 ms  10.36.8.126
  9    15 ms    14 ms    14 ms  10.36.6.21
 10    51 ms    50 ms    52 ms  ix-ae-11-0.tcore1.IT5-Istanbul.as6453.net [5.23.
0.41]
 11    53 ms    51 ms    51 ms  if-ae-8-2.tcore1.FNM-Frankfurt.as6453.net [195.2
19.156.21]
 12    51 ms    51 ms    51 ms  if-ae-7-2.tcore1.FR0-Frankfurt.as6453.net [195.2
19.50.1]
 13     *        *        *     Request timed out.
 14     *        *      201 ms  ae-1-11.bear1.Phoenix1.Level3.net [4.69.210.157]

 15   204 ms   202 ms   202 ms  LINDEN-RESE.bar1.Phoenix1.Level3.net [4.53.104.1
4]
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

C:\Users\Kheiron>

 

 

I followed the steps and those are what I have 

 

Link to comment
Share on other sites

  • 0

The pertinent pares are:

Packets Lost: 59/1,294 (4.6%)

 12    51 ms    51 ms    51 ms  if-ae-7-2.tcore1.FR0-Frankfurt.as6453.net [195.2
19.50.1]
 13     *        *        *     Request timed out. Here is the break...
 14     *        *      201 ms  ae-1-11.bear1.Phoenix1.Level3.net [4.69.210.157]

The 4.6% packet loss is higher than the SL system can work with. Thus the disconnection.

There is a problem between the Frankfurt and Phoenix routers. So, the problem is most likely the backbone provider. To get that fixed, send the same information you pasted in the post to your ISP and place in a trouble ticket with Linden Lab. Your ISP and the Lab working from both ends will find and fix the problem.

If you want to add weight to your complaint include 3 or 4 TraceRT's with time and date in your complaint/tickets. Spread them over 3 or 4 hours or even a couple days. This will show it is an ongoing problem,

Good luck.

Edited by Nalates Urriah
Spelling
  • Like 1
Link to comment
Share on other sites

  • 0
2 hours ago, Nalates Urriah said:

The pertinent pares are:

Packets Lost: 59/1,294 (4.6%)

 12    51 ms    51 ms    51 ms  if-ae-7-2.tcore1.FR0-Frankfurt.as6453.net [195.2
19.50.1]
 13     *        *        *     Request timed out. Here is the break...
 14     *        *      201 ms  ae-1-11.bear1.Phoenix1.Level3.net [4.69.210.157]

The 4.6% packet loss is higher than the SL system can work with. Thus the disconnection.

There is a problem between the Frankfurt and Phoenix routers. So, the problem is most likely the backbone provider. To get that fixed, send the same information you pasted in the post to your ISP and place in a trouble ticket with Linden Lab. Your ISP and the Lab working from both ends will find and fix the problem.

If you want to add weight to your complaint include 3 or 4 TraceRT's with time and date in your complaint/tickets. Spread them over 3 or 4 hours or even a couple days. This will show it is an ongoing problem,

Good luck.

I called them and they came to my home and changed the router. I don't have a disconnect problem anymore till they gone and its been 2 hours

  • Like 3
Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 2461 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...