Pages: 1 2 :: [one page] |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |

hudders
Black Serpent Technologies The-Culture
28
|
Posted - 2016.03.08 02:59:07 -
[1] - Quote
Ever since the "fault finding" downtime occurred about a week or so ago my client socket closes if I do not constantly take action in eve. I mean, I get up to get a granola bar and come back to my computer, and I'm socket closed.
I cannot station spin, I cannot sit on a gate and gate camp. I constantly worry about DCing in fleets if we aren't actively moving. Running a second account is now impossible. Whichever account is "less active" will socket close within 5 minutes. One character is warping while the other is in station or space, that character socket closes..
Prior to this downtime I never once experienced a socket closure unless I AFK'd for 5+ hours in station with my screen locked. Even then it was rare.
I am not the only player experiencing this issue, half my corp mates are reporting socket closure problems since that downtime. My internet is the same, stable 100mpbs, ethernet connection it has always been. No other game or internet based program is having ANY connection issues.
I'm sure I'm not the only one with this issue, so if anybody has a fix they know of or if CCP wants to comment with anything other than "it's not on us." Please post it up. I want this fixed, because it's making this game unplayable. |

RasTrent
Black Serpent Technologies The-Culture
14
|
Posted - 2016.03.08 03:00:23 -
[2] - Quote
hello, yes, me too. |

PassiveMenis
School of Applied Knowledge Caldari State
0
|
Posted - 2016.03.08 03:03:00 -
[3] - Quote
Me too.. so annoying.. fix it |

Troy Mileghere
Black Serpent Technologies The-Culture
3
|
Posted - 2016.03.08 03:05:00 -
[4] - Quote
its always my main that dc and my alt is just fine |

RasTrent
Black Serpent Technologies The-Culture
14
|
Posted - 2016.03.08 03:24:54 -
[5] - Quote
Local Time: 22:24 Eastern US - Socket Closed. |

hudders
Black Serpent Technologies The-Culture
28
|
Posted - 2016.03.08 03:42:39 -
[6] - Quote
Local Time: 19:41 Pacific Us - Socket Closed |

hudders
Black Serpent Technologies The-Culture
28
|
Posted - 2016.03.08 03:54:11 -
[7] - Quote
Local Time 19:53 Pacific US - Socket closed
Time to go play another game for a while. |

Salah ad-Din al-Jawahiri
New Order Logistics CODE.
413
|
Posted - 2016.03.08 04:18:48 -
[8] - Quote
It can be caused by a whole lot of different things. For instance, I used to get socketed out constantly when playing with two accounts after switching to a GPON network. I started playing with different settings at random, and it turned out that configuring DMZ for my computer's IP on the router fixed the problem. I'm no tech guy and can't explain why, but it worked. |

Daerrol
Death By Design Did he say Jump
295
|
Posted - 2016.03.08 04:30:01 -
[9] - Quote
I switched from wireless to socket and it worked wonders on reducing socket closed. Still get it but very very rare |

Nevyn Auscent
Broke Sauce
3032
|
Posted - 2016.03.08 04:45:32 -
[10] - Quote
Generally socket closed is a problem with the general internet, and nothing to do with CCP's servers at all. Lrn2internet. |
|

Ibutho Inkosi
Irubo Kovu
240
|
Posted - 2016.03.08 08:05:53 -
[11] - Quote
Dime to a donut says this subject has another thread, and this thread shall be closed.
As long as the tale of the hunt is told by the hunter, and not the lion, it will favor the hunter.
|

Mr Mieyli
Hedion University Amarr Empire
268
|
Posted - 2016.03.08 08:40:30 -
[12] - Quote
Nevyn Auscent wrote:Generally socket closed is a problem with the general internet, and nothing to do with CCP's servers at all. Lrn2internet.
Who decides when the socket is dead and should be closed? Why doesn't the client know to ping the server once in a while to keep the socket open? This is the only game I've played where I've seen this error, not saying it doesn't happen in other games but the must have a better way to handover your connection so it doesn't drop completely.
A case for more AoE in EvE
|

March rabbit
Federal Defense Union
1706
|
Posted - 2016.03.08 09:56:28 -
[13] - Quote
Mr Mieyli wrote:Nevyn Auscent wrote:Generally socket closed is a problem with the general internet, and nothing to do with CCP's servers at all. Lrn2internet. Who decides when the socket is dead and should be closed? Why doesn't the client know to ping the server once in a while to keep the socket open? This is the only game I've played where I've seen this error, not saying it doesn't happen in other games but the must have a better way to handover your connection so it doesn't drop completely. Need to say that i'm curious about it too.... Played other internet games (Counter-Strike for example) and have never seen such problem. At the same time in Eve "socket closed"....
The Mittani: "the inappropriate drunked joke"
|

gfldex
753
|
Posted - 2016.03.08 10:07:33 -
[14] - Quote
Pleace create traceroute to TQ and file a bug report. Posting anything on this very forum wont solve any problems.
If you take all the sand out of the box, only the cat poo will remain.
|

Duke Killem
Center for Advanced Studies Gallente Federation
0
|
Posted - 2016.03.08 11:31:43 -
[15] - Quote
March rabbit wrote:Mr Mieyli wrote:Nevyn Auscent wrote:Generally socket closed is a problem with the general internet, and nothing to do with CCP's servers at all. Lrn2internet. Who decides when the socket is dead and should be closed? Why doesn't the client know to ping the server once in a while to keep the socket open? This is the only game I've played where I've seen this error, not saying it doesn't happen in other games but the must have a better way to handover your connection so it doesn't drop completely. Need to say that i'm curious about it too.... Played other internet games (Counter-Strike for example) and have never seen such problem. At the same time in Eve "socket closed"....
That's because you can lag on FPS servers with a higher ping rate, you'll warp across the screen and make if hard for people to hit you. I think with Eve they don't allow this type of high lag.
I go through periods of the dreaded socket closed issue and it really pisses me off, I've used a traceroute to see when hops I make before hitting CCP and some of those hops lag, I have noticed that with my ISP (VM in UK) that when they cycle me a new IP every so often can either help and I wont have socket closed or hinder and I get it most days! Go figure! |

Mr Mieyli
Hedion University Amarr Empire
268
|
Posted - 2016.03.08 11:40:32 -
[16] - Quote
Really? FPS games are more tolerable of a high ping? Eves servers are some of the slowest(tick-rate) around, if your ping is less than 1000ms then you're not going to miss a tick. I don't believe that CCP are incapable of doing anything about this issue.
A case for more AoE in EvE
|

Bumblefck
Kerensky Initiatives
11121
|
Posted - 2016.03.08 11:46:52 -
[17] - Quote
Try using a VPN to connect to the internet before logging into the game. Whenever I get socket closed errors, I always fire up the ol' VPN client and connect to another server somewhere and that always seems to fix the errors. After a couple of days, I try the regular connection to see if it's still shutting the connection down.
Got a HoleySheet1 corpse? I'll buy it for 200m!
Bumble's Space Log
|

Duke Killem
Center for Advanced Studies Gallente Federation
0
|
Posted - 2016.03.08 12:06:36 -
[18] - Quote
Bumblefck wrote:Try using a VPN to connect to the internet before logging into the game. Whenever I get socket closed errors, I always fire up the ol' VPN client and connect to another server somewhere and that always seems to fix the errors. After a couple of days, I try the regular connection to see if it's still shutting the connection down.
Also this... I live in the UK and when getting a spate of socket closed errors I use my VPN to connect to another server in London! |

Duke Killem
Center for Advanced Studies Gallente Federation
0
|
Posted - 2016.03.08 12:18:44 -
[19] - Quote
Mr Mieyli wrote:Really? FPS games are more tolerable of a high ping? Eves servers are some of the slowest(tick-rate) around, if your ping is less than 1000ms then you're not going to miss a tick. I don't believe that CCP are incapable of doing anything about this issue.
And if you miss a few of those ticks you get the socket closed issue... Unless the server admin on an FPS game has set a high limit you can warp around as much as you want! |

Helios Anduath
Signal Cartel EvE-Scout Enclave
98
|
Posted - 2016.03.08 13:08:41 -
[20] - Quote
OK, sockets closed - the bane of every one's life when it happens. Socket closed happen when the game detects that the connection between you and TQ is unreliable - this help center article gives more details on the reasons for socket closed. Other programs may continue to work fine because their traffic may not be traversing a problematic route or because the application is more tolerant to network issues.
Usually a socket closed is a result of a networking blip between you and CCP's servers. This could be in your network, your ISP's network, any intermediate networks that your traffic passes through or even in CCP's network. When the latter occurs, it tends to disconnect lots of people at once and is picked up by their monitoring apps - this is part of the reason that the default GM response is "your ISP, not us". For quite a few of the people I have been helping with this recently, the issue has either been their local wifi, ISP issues or they have been affected by the number of broken sub-sea cables in the Australia/Asia/Pacific area.
So, how do you solve an ongoing socket closed problem? well the first step is to find out where the issue is and who is responsible for it. So if you are having an issue, please post where in the world you are, who your ISP is, what type of connection yours is and how you connect to your local router (wifi or wired).
An "easy" way to get some idea of where a problem may be is to grab a program called Pingplotter and set it going with a trace to client.eveonline.com while you play. When you get a socket closed, grab a screenshot of the pingplotter window and have a look at where the packetloss is and/or post it (I will gladly have a look at any posted pingplotters and help analyse them). Pingplotter is a good first step but it is notguaranteed to pick up every issue.
Another diagnostic is to play through a VPN. This can be a good short-term work around or a longer term solution on a really poor connection. If you don't get socket closed errors while connected to a VPN but do without it is indicative that there is a network problem somewhere. Using the VPN changes the route that your traffic takes to get to the cluster and the route that your traffic takes to the VPN server effectively becomes more reliable for the traffic you send up the VPN because of how they work. VPNs are not without their own issues though - they can increase your latency and decrease your bandwidth.
If pingplotter doesn't show anything and a couple of different VPNs don't help, then it is definitely worth reporting it to CCP along with all the diagnostic info you have gathered. If you get fobbed off with "it's your ISP" point them at the pingplotter showing no issues and escalate it.
hudders wrote:Ever since the "fault finding" downtime occurred about a week or so ago
The move to the new servers on the 29th seems to have caused some people's routing to the cluster to change to what seem to be less reliable routes. Also, on the 29th a large number of subsea cables near Singapore were damaged by seismic activity, causing some connectivity issues for people in that part of the world and causing their traffic to take different routes, adding load to infrastructure in other parts of the world.
Duke Killem wrote:I go through periods of the dreaded socket closed issue and it really pisses me off, I've used a traceroute to see when hops I make before hitting CCP and some of those hops lag, I have noticed that with my ISP (VM in UK) that when they cycle me a new IP every so often can either help and I wont have socket closed or hinder and I get it most days! Go figure!
Post a pingplotter when you get a disconnect. I am on VM and rarely have any issues however VM are known for overloading their local infrastructure at times and the Superhubs can have interesting wifi issues.
Finally, a word on analysing Pingplotters:
|
|

ST0NER SMURF
Vrix Nation CODE.
229
|
Posted - 2016.03.09 11:36:28 -
[21] - Quote
i have had it alot aswel, meanwhile np at all with any other games
goes better now though
__________________________________________________________________-á
GÖ½ When your pod gets blown to bits GÖ¬GÖ½ And you lose your implant fits GÖ¬\Gÿ+/ Don't worry GÖ¬ GÖ½ GÖ¬ GÖ½GÖ½ GÖ¬ GÖ½ GÖ¬ Be Happy \Gÿ+/
|

Dan Seavey Allier
Seavy Acquisitions Seeds of Sedition
81
|
Posted - 2016.03.09 13:14:59 -
[22] - Quote
Thank you, Helios Anduath for that comprehensive explanatory post.
Thanks for taking the time to lay out, and linking the resources to help troubleshoot.
Dan
Honey Never Sleeps.
|

Helios Anduath
Signal Cartel EvE-Scout Enclave
105
|
Posted - 2016.03.09 15:25:38 -
[23] - Quote
Dan Seavey Allier wrote:Thank you, Helios Anduath for that comprehensive explanatory post.
Thanks for taking the time to lay out, and linking the resources to help troubleshoot.
No problem - I will gladly look if you are having an issue and needs some help troubleshooting. |

Helios Anduath
Signal Cartel EvE-Scout Enclave
105
|
Posted - 2016.03.09 15:41:01 -
[24] - Quote
ST0NER SMURF wrote:i have had it alot aswel, meanwhile np at all with any other games
goes better now though
Other games working are not really an indicator of it being a problem at CCP's end, especially if you are outside of Europe. The reason being that with other games you tend to connect to more local servers so don't have potentially problematic international transit to deal with. Eve does seem to be a bit more susceptible to packet loss than some other games but on the flip side, it is more accepting of higher latency.
|

Mishra San
249
|
Posted - 2016.03.09 19:36:34 -
[25] - Quote
Ibutho Inkosi wrote:Dime to a donut says this subject has another thread, and this thread shall be closed.
mmMm, Donuts..
Steve Ronuken for CSM XI!
sending virtual hug, virtual hug sent!
|

Ibutho Inkosi
Irubo Kovu
242
|
Posted - 2016.03.10 00:11:28 -
[26] - Quote
Mishra San wrote:Ibutho Inkosi wrote:Dime to a donut says this subject has another thread, and this thread shall be closed. mmMm, Donuts.. Yeah...I guess I lost THAT bet. Sprinkles or no sprinkles?
As long as the tale of the hunt is told by the hunter, and not the lion, it will favor the hunter.
|

Helios Anduath
Signal Cartel EvE-Scout Enclave
107
|
Posted - 2016.03.10 01:18:44 -
[27] - Quote
Ibutho Inkosi wrote:Yeah...I guess I lost THAT bet. Sprinkles or no sprinkles?
Only half wrong - there is another active thread on this in the Issues, Workarounds and Localizations sub.
|

Dolthar Achasse
Discrete Astrographic Reconnaissance Technologies
10
|
Posted - 2016.03.10 08:26:11 -
[28] - Quote
noticed that if you stand still in a pos you get socket closures more often, but overall its there. |

Ni Neith
Hedion University Amarr Empire
15
|
Posted - 2016.03.10 08:35:06 -
[29] - Quote
Yesterday I went beyond mad after I lost a ship and a capsule to some nullsec dwellers at the gate to a 'socket closed'. I have been dodging and tricking them like hell and it is not the way like I should have died. But now I am on their kill list and even if I get my ship partially reimbursed this killmail is something that will never go away. And this made me apeshit crazy. And NO, it is NOT my internet if 3 members of a fleet in different parts of the world get socked closed at the same time!!!! |

Helios Anduath
Signal Cartel EvE-Scout Enclave
109
|
Posted - 2016.03.10 13:13:14 -
[30] - Quote
Ni Neith wrote: And NO, it is NOT my internet if 3 members of a fleet in different parts of the world get socked closed at the same time!!!!
It may not be your home network or your ISP's network that had an issue (or rather, there could be a minor issue that on its own does cause a problem) but it could be that you all ended up following a common route closer to the cluster and that had an issue resulting in a socket closed.
But without any diagnostics from you and your fleet members, we will never know...
Also, if you got as mad as you sound over a ship loss, please calm down and take a step back. |
|

Ni Neith
Hedion University Amarr Empire
16
|
Posted - 2016.03.10 13:40:39 -
[31] - Quote
Helios Anduath wrote: Also, if you got as mad as you sound over a ship loss, please calm down and take a step back.
No I wont, because instead of fixing this important issue CCP is introducing stupid minigames they call science! |

Helios Anduath
Signal Cartel EvE-Scout Enclave
109
|
Posted - 2016.03.10 15:05:15 -
[32] - Quote
Ni Neith wrote:No I wont, because instead of fixing this important issue CCP is introducing stupid minigames they call science!
And how, prey tell, would you like CCP to fix an issue that is most likely out of their control and you are not providing any diagnostics?
Sockets closeds triggered by something on CCP's side usually result in lots of people being disconnected at once and they are usually transient issues with their ISP that get resolved quickly. These are picked up by their monitoring and CCP are good at acknowledging them and informing people that something has happened on the eve-status twitter.
Most of the time with more localised/smaller numbers of people disconnecting at once, it is something between them and CCP. For a single, one-off event affecting a few people, it could be anything from a route failing over at an intermediate network (either planned or as a result of a failure), a cable getting moved while someone is poking in a rack causing packet loss, or any number of other transient effects that cause a momentatry blip and then pass. These are not something that can be fixed - they happen, that is the nature of the internet and is even more pronounced when you are using services in another country due to the number of intermediate networks you pass through. Getting upset over a one-off discconet really isn't helpful and if it really does annoy you that much, maybe online gaming isn't for you?
For individuals having issues at differnt times, from the people I have been helping at least, we are generally finding that there is either noticeable packet loss on a pingplotter or connecting through a VPN stabilises things. This shows it is not an issue on CCP's end but something somewhere on one of the many networks that your traffic passes through on it's merry way from you to CCP.
Could there be an underliying issue for some people at CCP's end? possibly but as long as people keep blaming every socket closed on CCP and fail to carry out any diagnostics it will not be found as there are so many false reports to sift through. In most cases it really is NOT a problem at CCP's end.
Now, if you want some help or to help work out what happened, please post a tracert to client.eveonline.com at a minimum or if the socket closeds keep happening, a screenshot of pingplotter to client.eveonline.com during a disconnect event. |

Ni Neith
Hedion University Amarr Empire
17
|
Posted - 2016.03.10 17:04:33 -
[33] - Quote
Helios Anduath wrote:These are not something that can be fixed - they happen, that is the nature of the internet and is even more pronounced when you are using services in another country due to the number of intermediate networks you pass through. Getting upset over a one-off discconet really isn't helpful and if it really does annoy you that much, maybe online gaming isn't for you?
Can or can't be fixed? Anyway. I know this is bs since I am playing eve for 2 years now. Never was there such a high rate of drops like in the last few month. |

Helios Anduath
Signal Cartel EvE-Scout Enclave
109
|
Posted - 2016.03.10 18:35:19 -
[34] - Quote
Ni Neith wrote:Can or can't be fixed? Anyway. I know this is bs since I am playing eve for 2 years now. Never was there such a high rate of drops like in the last few month.
Can't - my bad.
You can call BS as much as you want - it does not change the fundamental way that the Internet and networking in general function. Socket closeds happen because of packet loss, there are no two ways about it. Packet loss is a result of network issues.
A wireshark traffic capture from someone having recuring issues earlier was showing TCP retransmissions (so no acknowledgement received, showing that packets have been lost somewhere) right before a socket closed. If you don't know networking, you can generally think of it in terms of a 4-layer abstracted model. Eve runs up at the application layer. TCP stuff happens at the transport layer, this is below the application layer and handled by the network stack in your OS.
In contrast to your "knowledge", I can tell you that the only time I have had socket closeds is when my ISP had issues. Other than that, my playtime has not been affected by socket closeds at all. I can also tell you that a number of other people who were having socket closed problems was due to issues under their control - for example, one guy had a wifi problem that developed recently because of a change in local RF noise and a wifi adapter starting to die.
If stuff has started to happen in the last few months, have you looked at what local issues exist (e.g. have you actually done any diagnostics on your setup and connection to determine if you have some local hardware that is going dodgy or whether your ISP is having issues)? On a more global scale, some of the routers on the East Coast of the US have been having utilisation problems, there have been cable faults in the Australia and Asian Pacific regions. The data centre move on the 29th resulted in routes changing for people as CCP have added more peering so this is why some people have started having issues since then.
You still haven't posted a tracert or any other diags, or even said what if any diagnostics you have done. This tells me that you don't actually want to try to fix your issue is and instead just want to complain and unreasonably apportion blame without doing your homework.
|

Ni Neith
Hedion University Amarr Empire
19
|
Posted - 2016.03.10 19:30:43 -
[35] - Quote
Helios Anduath wrote: In contrast to your "knowledge", I can tell you that the only time I have had socket closeds is when my ISP had issues. Other than that, my playtime has not been affected by socket closeds at all. I can also tell you that a number of other people who were having socket closed problems was due to issues under their control - for example, one guy had a wifi problem that developed recently because of a change in local RF noise and a wifi adapter starting to die.
Like I said. Usually 2 or more people are socked closed in a fleet simultaniously. Different countries, even different continets. I don't see how it is my ISPs fault. Or WIFI or whatever on my side. |

Helios Anduath
Signal Cartel EvE-Scout Enclave
109
|
Posted - 2016.03.10 19:38:41 -
[36] - Quote
Ni Neith wrote:Like I said. Usually 2 or more people are socked closed in a fleet simultaniously. Different countries, even different continets. I don't see how it is my ISPs fault. Or WIFI or whatever on my side.
You may be on different continents but you could quite easily share the same final routing as each other as you are comming to one common endpoint.
I will ask again incase you missed my previous requests for it - please post a screenshot of a tracert to client.eveonline.com at the bare minimum, or do you not want help? |

Zander Kumamato
The Chaos Void
48
|
Posted - 2016.03.10 20:06:45 -
[37] - Quote
logging in this morning received socket closed four times in a row a couple seconds after character selection and station loads, eventually it stays connected a little while until get socket closed; repeat with the instant socket closeds after logging in over and over. Have verified cache, etc. All tracert today looks similar as below.
Microsoft Windows [Version 10.0.10586] (c) 2015 Microsoft Corporation. All rights reserved.
C:\Users\unholyrender>tracert client.eveonline.com
Tracing route to client.eveonline.com [87.237.34.202] over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms complex.unholyrender.master.grid [192.168.9.1] 2 14 ms 10 ms 10 ms cpe-72-177-0-1.austin.res.rr.com [72.177.0.1] 3 36 ms 32 ms 31 ms tge0-0-12.ausutxla02h.texas.rr.com [66.68.5.101] 4 11 ms 12 ms 17 ms agg50.ausxtxir02r.texas.rr.com [24.175.43.183] 5 21 ms 14 ms 23 ms agg39.hstqtxl301r.texas.rr.com [24.175.41.54] 6 20 ms 16 ms 13 ms bu-ether16.hstqtx0209w-bcr00.tbone.rr.com [66.109.6.108] 7 25 ms 31 ms 41 ms bu-ether12.dllstx976iw-bcr00.tbone.rr.com [66.109.6.39] 8 17 ms 19 ms 17 ms 0.ae1.pr1.dfw10.tbone.rr.com [107.14.17.234] 9 21 ms 24 ms 19 ms 66.109.9.91 10 17 ms 20 ms 27 ms ae7.cr2.dfw2.us.zip.zayo.com [64.125.20.233] 11 126 ms 132 ms 131 ms ae27.cs2.dfw2.us.eth.zayo.com [64.125.30.182] 12 134 ms 133 ms 137 ms ae5.cs2.iah1.us.eth.zayo.com [64.125.28.102] 13 130 ms 137 ms 131 ms ae3.cs2.dca2.us.eth.zayo.com [64.125.29.44] 14 143 ms 131 ms 148 ms ae0.cs1.dca2.us.eth.zayo.com [64.125.29.228] 15 129 ms 161 ms 134 ms ae5.cs1.lhr15.uk.eth.zayo.com [64.125.29.130] 16 134 ms 133 ms 131 ms ae27.mpr3.lhr3.uk.zip.zayo.com [64.125.30.235] 17 132 ms 134 ms 134 ms ae5.mpr1.lhr23.uk.zip.zayo.com [64.125.20.97] 18 129 ms 123 ms 129 ms 79.141.38.134.IPYX-126929-ZYO.zip.zayo.com [79.141.38.134] 19 124 ms 127 ms 131 ms srv202-c.ccp.cc [87.237.34.202]
Trace complete.
It'll likely work perfectly again tomorrow for another year. Such is "The Internet".
|

Ni Neith
Hedion University Amarr Empire
19
|
Posted - 2016.03.10 20:22:38 -
[38] - Quote
Helios Anduath wrote:Ni Neith wrote:Like I said. Usually 2 or more people are socked closed in a fleet simultaniously. Different countries, even different continets. I don't see how it is my ISPs fault. Or WIFI or whatever on my side. You may be on different continents but you could quite easily share the same final routing as each other as you are comming to one common endpoint. I will ask again incase you missed my previous requests for it - please post a screenshot of a tracert to client.eveonline.com at the bare minimum, or do you not want help?
Here you go. |

Helios Anduath
Signal Cartel EvE-Scout Enclave
109
|
Posted - 2016.03.10 20:28:03 -
[39] - Quote
Zander Kumamato wrote:logging in this morning received socket closed four times in a row a couple seconds after character selection and station loads, eventually it stays connected a little while until get socket closed; repeat with the instant socket closeds after logging in over and over. Have verified cache, etc. All tracert today looks similar as below.
What does a pingplotter to client.eveonline.com show during one of the disconnects? Pingplotter repeatedly pings each hop in your route and can show if thereis packet loss and where it is |

Helios Anduath
Signal Cartel EvE-Scout Enclave
109
|
Posted - 2016.03.10 20:36:13 -
[40] - Quote
OK, that is different to the potentially problematic route that some people are using from the other thread. CCP peer with over 23 different providers so there are a lot of potential inbound routes.
If you run a pingplotter to client.eveonline.com for a while, that will show if there is any packet loss along the route. If you get a socket closed during the capture, all the better.
Playing through a VPN is a good test as it can stabilise things by sending you over a different route.
If pingplotter really doesn't show anything and a few different VPNs don't help, then it is something to open a petition about.
|
|

hudders
Black Serpent Technologies The-Culture
29
|
Posted - 2016.03.14 03:02:27 -
[41] - Quote
Okay riddle me this. If it is unreliable connection issues answer the following questions.
Why does it only happen when I am in a state of inactivity? I never DC while actively fighting, moving warping, etc.
Why does it only happen to one account and not all of them? They don't socket close together. Same computer, same ISP. How is one account more reliably connected than the other?
And finally, if CCP making a server change can negatively affect how our ISPs connect, why are they not able to make a change to positively affect it? Why not change the way this system "pings" our connection so that we socket close less. Realistically CCP cannot expect all their players with this issue to do complex troubleshooting on their own.
I am paying for a service, it shouldn't require me to spend hours troubleshooting my otherwise fine connection. If the issue cannot be resolved on their end, I will simply end service for a game that I can no longer play. I am sure there are many many players that will follow a similar path. "It's not our fault, check your ISP" isn't a good response. Especially when it's a new problem and my ISP hasn't changed, but CCP servers have. |

Helios Anduath
Signal Cartel EvE-Scout Enclave
120
|
Posted - 2016.03.14 10:18:07 -
[42] - Quote
hudders wrote:Okay riddle me this. If it is unreliable connection issues answer the following questions.
Why does it only happen when I am in a state of inactivity? I never DC while actively fighting, moving warping, etc.
Why does it only happen to one account and not all of them? They don't socket close together. Same computer, same ISP. How is one account more reliably connected than the other?
Each account has it's own connection so depending on when it tries to talk to the server while idle, one client could hit an issue that passes by the next time a client tries to communicate.
Now, the fun thing, over in the other thread on this, someone is having an idle client disconnecting issue - the kicker, it only happens when he is connected to the wired port of his home router. If he connected by Wifi, his 3G hotspot or uses a VPN on the wired connection, he has no problems at all. Packet captures show a spike in TCP retransmissions and duplicate ACKs right before the socket closed (TCP retransmissions happen in the operating system's network stack, below Eve, and are a sign that some packets have not made it to the destination for some reason).
Networks can be fickle things and diagnosing them can be a complete PITA.
hudders wrote:And finally, if CCP making a server change can negatively affect how our ISPs connect, why are they not able to make a change to positively affect it? Why not change the way this system "pings" our connection so that we socket close less. Realistically CCP cannot expect all their players with this issue to do complex troubleshooting on their own.
I am paying for a service, it shouldn't require me to spend hours troubleshooting my otherwise fine connection. If the issue cannot be resolved on their end, I will simply end service for a game that I can no longer play. I am sure there are many many players that will follow a similar path. "It's not our fault, check your ISP" isn't a good response. Especially when it's a new problem and my ISP hasn't changed, but CCP servers have.
They are in the process of doing this. If you read the end of the dev blog, you would see that they are implementing a new dynamic BGP routing solution to look for better routes and that they recently ditched an ISP who was not up to par.
However, ultimately, CCP are not in control of what goes on outside of their network and because of the way the internet works, there will always be transient issues that cause problems. CCP "Pinging" your connection won't get around a packet loss issue.
Regarding users needing to do troubleshooting, welcome to tech and the troubleshooting you need to do to work out where an issue is here really is not complex and the basic diagnostics hardly take hours. It is also the type of troubleshooting that the user has to do as CCP can't do it for you. [/i]Most[/i] of the time, socket closed issues are a problem on the user's end or something out of CCP's control and while you may pay CCP for access to Eve, but you don't pay them to support your home network/ISP/the internet.
Now, you say that your connection is otherwise fine but I will bet that is from observation only and you have not actually done any diagnostics? This has been the case with a fair few of the people complaining about packet loss and it turned out to be a Wifi issue. The fun thing about network traffic is that a fair chunk of what you do every day can cope with packet loss and just be a little slower. Some services, by their nature, are just more sensitive to packet loss.
So, to troubleshooting your problem, any chance you can tell me what make/model your router is, how you connect to it (wifi/wired) and can you provide a screenshot of a Pingplotter to client.eveonline.com taken just after a socket closed event (you set it going and just play like normal until you get a socket closed). Another quick test you can carry out is to play through a VPN (someone has reported that the Avast VPN 7-day free trial with the Frankfurt server selected works quite well). |

Kinete Jenius
Republic Military School Minmatar Republic
114
|
Posted - 2016.03.16 00:03:04 -
[43] - Quote
hudders wrote:Okay riddle me this. If it is unreliable connection issues answer the following questions.
Why does it only happen when I am in a state of inactivity? I never DC while actively fighting, moving warping, etc.
Why does it only happen to one account and not all of them? They don't socket close together. Same computer, same ISP. How is one account more reliably connected than the other?
And finally, if CCP making a server change can negatively affect how our ISPs connect, why are they not able to make a change to positively affect it? Why not change the way this system "pings" our connection so that we socket close less. Realistically CCP cannot expect all their players with this issue to do complex troubleshooting on their own.
I am paying for a service, it shouldn't require me to spend hours troubleshooting my otherwise fine connection. If the issue cannot be resolved on their end, I will simply end service for a game that I can no longer play. I am sure there are many many players that will follow a similar path. "It's not our fault, check your ISP" isn't a good response. Especially when it's a new problem and my ISP hasn't changed, but CCP servers have. I have 12 accounts still active and I've AFKed them extensively the last few weeks. They have both sat AFK in space and in station for +6 hours at a time. I haven't had a socket reset since the big patch a while back that broke everyone's ability to connect to the server. After a couple days those socket resets stopped.
It's either your connection or something further down the line like your ISP's ISP.
As stated in other areas each account talks separately and if you lose a few packets at the wrong time for a specific client that client will socket reset while others don't. |

BrundleMeth
Caldari Provisions Caldari State
512
|
Posted - 2016.03.16 00:32:36 -
[44] - Quote
Enjoy it. These days it can be the most fun in game... |
|
|
|
Pages: 1 2 :: [one page] |