| Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 30 40 50 .. 52 :: one page |
| Author |
Thread Statistics | Show CCP posts - 8 post(s) |

Miles Apart
|
Posted - 2009.03.06 22:17:00 -
[601]
Sorry to disappoint you ping-posting people, but packet loss, even 100% does not necessarily signify a problem.
I have a *rock solid* connection to Eve that never CTDs or anything. Just out of interest, I ran PingPlotter and got the following:
Target Name: N/A IP: 87.237.38.200 Date/Time: 06/03/2009 21:23:05 to 06/03/2009 21:26:36
Hop Sent Err PL% Min Max Avg Host Name / [IP] 1 85 0 0.0 0 21 0 . [192.168.2.1] 2 85 0 0.0 31 2005 88 ge0-1.lns2-c12.telh.planet.net.uk [62.25.196.137] 3 85 3 3.5 31 199 38 ge2-1.pbr-1.telh.as5388.net [62.25.196.130] 4 85 5 5.9 32 424 81 pos1-0.ber-1.the.as5388.net [195.92.55.160] 5 85 4 4.7 32 207 40 linx1.telecityredbus.net [195.66.226.82] 6 85 3 3.5 32 225 45 [85.90.226.209] 7 85 3 3.5 33 273 44 531-dist65-02.lon3.telecity.net [217.20.44.222] 8 84 84 100.0 0 0 0 [-] 9 85 0 0.0 32 242 41 [87.237.38.200]
As you can see, I am getting 100% loss from the 8th hop, the same that is supposedly causing problems.
So I wouldnt get too carried away with what you see from traceroute/PingPlotter....
|

Allen Ramses
Caldari Typo Corp
|
Posted - 2009.03.07 00:07:00 -
[602]
Edited by: Allen Ramses on 07/03/2009 00:08:57
Originally by: Miles Apart As you can see, I am getting 100% loss from the 8th hop, the same that is supposedly causing problems.
So I wouldnt get too carried away with what you see from traceroute/PingPlotter....
Please don't use a router configured not to respond to ICMP as an argument to taking a very congested router (25% - 60% ICMP loss) with a grain of salt.
EDIT: What I am saying is a router ignoring ICMP is one thing, a router unable to process ICMP is something completely different. ____________________ CCP: Catering to the cowards of a cold, harsh universe since November, 2006. |

Endovior
Gallente Taggart Transdimensional Virtue of Selfishness
|
Posted - 2009.03.07 13:18:00 -
[603]
Don't know if this will help... but I've been having this issue, and just fixed it, by switching my network over to OpenDNS. Just offhand, I'd assume that this is because OpenDNS routes around the crappier servers... that's half the point of OpenDNS, after all.
Your mileage may vary, of course; but it's another thing to try, for all those who've 'tried everything'.
|

Grall Sek
Caldari CREO Technologies
|
Posted - 2009.03.07 20:58:00 -
[604]
Doesnt do any good to me, still getting disconnects |

Allen Ramses
Caldari Typo Corp
|
Posted - 2009.03.07 22:03:00 -
[605]
OpenDNS is exactly what the name implies. An Open Domain Name Service. Since domain resolution is only IP name assignment, it should not affect the route in any way.
Sorry, but this is snake oil. If you are no longer getting disconnects, this is not why. ____________________ CCP: Catering to the cowards of a cold, harsh universe since November, 2006. |

Agent Unknown
Caldari
|
Posted - 2009.03.08 00:00:00 -
[606]
Originally by: Allen Ramses
Originally by: Agent Unknown Look at the lag spike from 13-17....~15 ms to almost 100 in one hop? That doesn't seem right. Looks like a backbone issue to me...
~15ms to almost 100 in one hop? That doesn't seem right. Looks like the route is taking an unexpected detour from New York to London. It's not like that kind of dist... Oh, wait.
Eh heh...you know, I didn't see that there  ----------------------------------- "What can go wrong, will go wrong." |

Johan Civire
|
Posted - 2009.03.08 05:49:00 -
[607]
I dont have problems however i dont use any router between internet and local. I have only random memmory overload. More like leak mem. However when i put vertual mem on no problems. Some day i will hunt you! |

Lanu
0utbreak
|
Posted - 2009.03.08 19:30:00 -
[608]
Edited by: Lanu on 08/03/2009 19:30:12 Looks like the route my traffic to the tranquility server uses changed.
Old route with socket closed issues= 2 12 ms 13 ms 13 ms lo1.dr6.d12.xs4all.net [194.109.5.213] 3 12 ms 8 ms 7 ms 0.ge-3-0-0.xr4.1d12.xs4all.net [194.109.7.137] 4 8 ms 9 ms 8 ms 0.so-6-0-0.xr1.tc2.xs4all.net [194.109.5.10] 5 72 ms 201 ms 209 ms TenGE13-2.br02.ams01.pccwbtn.net [195.69.145.37] 6 15 ms * 16 ms telecity.ge9-9.br02.ldn01.pccwbtn.net [63.218.13.222] 7 16 ms 15 ms 15 ms mailtx.2zxr.com [217.20.44.10] 8 * * * Request timed out. 9 15 ms 14 ms 15 ms 87.237.38.200
new route without socket closed issues = 2 8 ms 8 ms 8 ms lo1.dr6.d12.xs4all.net [194.109.5.213] 3 8 ms 53 ms 10 ms 0.ge-3-0-0.xr4.1d12.xs4all.net [194.109.7.137] 4 9 ms 9 ms 8 ms 0.so-6-0-0.xr1.tc2.xs4all.net [194.109.5.10] 5 14 ms 15 ms 15 ms ams-001.interoute.net [195.69.144.81] 6 20 ms 20 ms 20 ms ae1-0.lon-001-score-1-re0.interoute.net [84.233.190.58] 7 21 ms * 21 ms 89.202.226.26 8 38 ms 207 ms 34 ms 531-dist65-02.lon3.telecity.net [217.20.44.222] 9 * * * Request timed out. 10 22 ms 20 ms 20 ms 87.237.38.200
One of the 'problem routers' at hop 6 of the old route (telecity.ge9-9.br02.ldn01.pccwbtn.net [63.218.13.222]) is no longer on the route with my new route. So hopefully this solved the issue (or at least.. my issue).
|

ShigekiShota
|
Posted - 2009.03.09 03:35:00 -
[609]
Instead of random socket close at times, i got audio error as well =(
|

Zylithi
Caldari Interstellar Association of Alcohol Consumption Terrebellum
|
Posted - 2009.03.09 14:01:00 -
[610]
Edited by: Zylithi on 09/03/2009 14:02:51 1 30 ms 2 ms 2 ms 192.168.2.1 2 78 ms 97 ms 99 ms speedtouch.lan [192.168.1.254] 3 123 ms 135 ms 133 ms lo-100.erx04.tor.packetflow.ca [206.248.154.103]
4 109 ms 92 ms 120 ms 2130.ae0.bdr01.tor.packetflow.ca [69.196.136.97]
5 97 ms 135 ms 77 ms 65.39.198.249 6 87 ms 75 ms 121 ms oc48-po3-0.mtl-bvh-cor-1.peer1.net [216.187.114. 198] 7 139 ms 133 ms 120 ms 10ge.xe-0-0-0.mtl-bvh-cor-1.peer1.net [216.187.1 15.85] 8 80 ms 75 ms 102 ms oc192.xe-4-0-0.nyc-telx-dis-1.peer1.net [216.187 .115.54] 9 274 ms 233 ms 213 ms oc48-so2-0-0.ldn-teleh-dis-1.peer1.net [216.187. 115.226] 10 205 ms 333 ms 244 ms linx1.telecityredbus.net [195.66.226.82] 11 227 ms 226 ms 203 ms 85.90.226.209 12 189 ms 206 ms 239 ms 531-dist65-02.lon3.telecity.net [217.20.44.222]
13 * * * Request timed out. 14 232 ms 225 ms 190 ms 87.237.39.199
Trace complete.
Day 37 of the nefarious Socket Closed message.
Called my ISP, and after further investigation, they think the issue is with Bell Canadas rediculous throttling practice (Bell Canada is more or less a peering provider in canada, as my ISP buys bandwidth from them. There's no other competing company that provides DSL that doesn't go through Bell.) Confirmed this while running a speed test. Bell is throttling my connection down to 30 KB/sec when eve is running, causing over 90% packetloss on EVERYTHING. What this means, is probably 40% of potential canadian users are now entirely blocked from playing eve.
Perhaps they will be releasing a competing product soon! They already did it with the bell video store.
Fighters 5 finished today. However, it doesn't matter.
For those of you who say "gawd just switch ISP, noob" yeah... only DSL is available in my area.
|

Lanu
0utbreak
|
Posted - 2009.03.09 16:20:00 -
[611]
That really sucks for you Zylithi .
Seems that a lot of the people with the socket closed issue are in fact having network issues beyond their control. Lots of ISP/routing trouble.
|

Zylithi
Caldari Interstellar Association of Alcohol Consumption Terrebellum
|
Posted - 2009.03.09 21:11:00 -
[612]
Edited by: Zylithi on 09/03/2009 21:11:09 Alright, I made a post on the TekSavvy forums, which is one of the larger ISPs losing business because of Bell's throttling practices. Already had several replies... hopefully, we can take "politely ask" bell to stop throttling a game!
http://www.dslreports.com/forum/teksavvy
A little off topic, but I would ALSO advise ANY user of DSL service in Canada to head over to this forum.
|

6Bagheera9
Slacker Industries The Boat Violencing Initiative
|
Posted - 2009.03.11 16:59:00 -
[613]
RAGE!!!
|

Taguchi Hiroko
0utbreak KrautbreaK
|
Posted - 2009.03.11 20:36:00 -
[614]
Was better after yesterday's patch, but this evening it started again. Getting socket closed 3-4 times in an hour, very annoying. ------------------------------------------------------------------------------------
|

Bozwick
Gallente PROGENITOR CORPORATION
|
Posted - 2009.03.11 21:04:00 -
[615]
I havent been able to log in at all in almost a week due to "the connection to the server was closed". I've been playing for 3 years but why pay if you can't play?
|

Amarretto Christ
Amarr Scarlet Clover
|
Posted - 2009.03.12 01:01:00 -
[616]
Edited by: Amarretto Christ on 12/03/2009 01:03:57 None of the "fixes" worked for me so I am canceling my subscription until I see CCP's attempt to rectify and cure. That is the only way a business will get the point people, cancel enough subscriptions and they'll be begging us to come back. $4.99 a month is what I'd pay for what I am getting right now, so take note CCP, if you want me back fix our game or lower your price for packeteers.

By the way this problem is a few months old, and we have seen two half-assed suggestions from CCP. Would you keep sending a check to someone that practically laughs in your face? I am no sap, the rest of you may be, but I have pride.
|

Grall Sek
Caldari CREO Technologies
|
Posted - 2009.03.12 01:59:00 -
[617]
Very true Amarreto. I tried everything and nothing solves the problem. My pingplotter gives only 1 hop with 20% packet loss, i dont think thats enough to make enough damage to make my game unplayable. Its no ones fault here but yours CCP and now that we tried everything dont you think its time for you to fix it |

Kayl Breinhar
GoonFleet GoonSwarm
|
Posted - 2009.03.12 09:05:00 -
[618]
This just happened again. It was "fixed" for me for several days, and just happened again, conveniently right after my petition was closed.
|

Kyguard
Knockaround Guys Inc.
|
Posted - 2009.03.12 20:39:00 -
[619]
This is happening again. I cannot stay on for a period of longer than 5 minutes. One account goes down, then the other 5 minutes later. -
|

Zylithi
Caldari Interstellar Association of Alcohol Consumption Terrebellum
|
Posted - 2009.03.12 22:20:00 -
[620]
Unable to play due to an issue that has been outstanding for one year.
I've HAD it, who wants my stuff? I'm going to go play WoW.
|

xSantoSx
Steel Battalion Circle-Of-Two
|
Posted - 2009.03.12 22:29:00 -
[621]
same problem here ever since the patch
|

u8cappy
|
Posted - 2009.03.12 22:35:00 -
[622]
Iv only been playing for just over a month, but since this new patch came out i am rarely able to stay on for more than 10 minutes, if i dont get kicked it just hangs for a few minutes and crap jumps around to catch up... NEVER had a problem untill the patch came out.
|

CHAOS100
Widowmakers
|
Posted - 2009.03.12 22:40:00 -
[623]
I logged in today and probed a wormhole and entered it. Then client went unresponsive and 'socket closed'. Then I logged back in and managed to recover my probes, then I tried to warp back to the entrance, and then, socket closed. Then I logged in for the 3rd time to warp gate to the gate and jumped out of the wormhole. Then I decided I had enough connection pvp and ctrl-q'd.
Must be my ISP's fault of course. --------------
|

Kiaranselee
|
Posted - 2009.03.12 23:02:00 -
[624]
Also, since apo patch game got extremly laggy. even when alone in the solar system. and NO, it has nothing to do with my connection, tested that and my whole corp has the same issues.
|

Mustacho
|
Posted - 2009.03.12 23:17:00 -
[625]
This is happening to me as well, sometimes I get kicked off again in less than 20 seconds, the game is unplayable right now.
|

Jilal Mubaru
Gallente Spawns of Thanatos
|
Posted - 2009.03.12 23:52:00 -
[626]
Edited by: Jilal Mubaru on 12/03/2009 23:53:51 I'd have to agree with previous posts, the problem appears to be Telecity routers in London, not local ISP traffic shaping etc.
Either due to congestion (patch download anyone??), or other configuration problems.
In my case, between hops 7-8 (normal latency is ~140ms from toronto->eve). Tested from my work network, which takes a different path, with 0 issues and normal latency. Luckily I can VPN to work to get around the problem personally.
Hopefully CCP will drop telecity as a BGP peer for at least the short term, which would in theory solve peoples current issues. Im sure CCP employs a network engineer that would easily be able to see the problem if they look close enough.
C:\Documents and Settings\XXXXXX>tracert eve-online.com
Tracing route to eve-online.com [87.237.39.199] over a maximum of 30 hops:
1 9 ms 1 ms 2 ms 192.168.1.1 2 9 ms 12 ms 9 ms 10.229.100.1 3 8 ms 25 ms 7 ms 69.63.243.162 4 16 ms 19 ms 8 ms 69.63.249.62 5 23 ms 28 ms 23 ms 66.185.83.62 6 22 ms 23 ms 23 ms ge10-14.br02.ash01.pccwbtn.net [63.218.94.117] 7 115 ms * 114 ms telecity.ge9-9.br02.ldn01.pccwbtn.net [63.218.13 .222] 8 278 ms 281 ms 279 ms 532-dist65-01.lon3.telecity.net [217.20.44.226]
9 264 ms 258 ms 243 ms ipt-ccp-games-1-as35834.lon3.telecity.net [217.2 0.44.138] 10 282 ms 279 ms 275 ms 87.237.39.199
Trace complete.
|

Halphas
Solar Wings Industry
|
Posted - 2009.03.13 09:28:00 -
[627]
A little update.
Pingplotter shows nothing expect some 80% packet loss near the end. Few weeks ago it was 100%.
The problem is still here. I can run 1 account almost withouth any problem, as far as I don't go afk. With 2 clients on the same computer, I have constant socket loss...
So nothing you, consider this post as a free bump...
|

Kayl Breinhar
GoonFleet GoonSwarm
|
Posted - 2009.03.13 09:50:00 -
[628]
CCP, get CCP Atlanta to help you on this. Obviously when you try to diagnose the problem, you're not going through the troubled routers. Get Atlanta to run a series of "official" ping series and find the problem.
Also, this was pretty much "fixed" for me, at least, before the patch. Are you certain all the new information the new content requires isn't piping more water through a pipe that barely could accommodate the original amount? You added a lot more information that each system and thus each client has to keep track of.
For all we know when jumping into a system there could be x amount of wormholes in it that we'll never use, all of them creating more information that increases the total amount of information that needs to be sent, received, and then processed repeatedly at both ends, leading to a situation where individualized sockets could be dropped and I post a :words: thread like this here.
This is endangering subscribers, it is endangering personal assets which total in the billions in funny money, and in case you're not apprised of certain people within the Goonswarm hierarchy, Grayton is one of our lead logistics guys - this unresolved issue that you seem to not want to acknowledge anymore since it's not technically "your problem" (since it's outside the main servers) is endangering whole alliances.
But, given our size, we have redundancy. When people like Grayton complain that he can't hold a steady connection for five minutes, there are other people with inexplicably more solid connections who shrug and make up the slack. But what about the smaller corps and alliances who have one person to do their alliance-level logistics who can't stay online long enough to make sure their towers stay fueled or lose a jump freighter because to them THEIR screen looked clear for 3-4 minutes before the client decided to tell him it had dropped?
Please fix this. Or at the very least tell us we haven't been doing your own job for you in vain for the past 21 pages with pingplotter and self-styled e-forensics. I honestly don't think a single post to say "we really appreciate your cooperation and help on this, we're working on it, and this is what we think the problem is and how we're gonna try and go about fixing it" is a tall order.
Even a fraction of that would be welcomed, and we're not getting anything, which leads people like me to make conclusions that you've concluded the problem isn't yours to solve as it falls outside your "jurisdiction" and/or the number of the afflicted far outweighs the number unaffected, and people like me and everyone else in this thread are merely victims that can be attrited until the problem resolves itself that way.
|

C0wgirl
Gallente Pothouse Cartel IDLE EMPIRE
|
Posted - 2009.03.13 18:23:00 -
[629]
O have been getting this for ages now. Here's my tracert info. Can anyone help translate it to see if it's the same place which is the problem as everyone else, or whether it's my ISP? I'm with Be internet. (I believe the req timed out local to Be are because they filter ping commands to a lower priority.)
Tracing route to 87.237.38.200 over a maximum of 30 hops
1 68 ms 98 ms 99 ms bebox.config [192.168.1.254] 2 * * * Request timed out. 3 * * 27 ms 10.1.2.5 4 * * * Request timed out. 5 133 ms 124 ms 123 ms linx.telecityredbus.net [195.66.224.82] 6 144 ms * * 85.90.226.205 7 151 ms 154 ms 162 ms 532-dist65-01.lon3.telecity.net [217.20.44.226]
8 139 ms 152 ms 129 ms ipt-ccp-games-1-as35834.lon3.telecity.net [217.20.44.138] 9 133 ms 143 ms 163 ms 87.237.38.200
1 25 ms 95 ms 97 ms bebox.config [192.168.1.254] 2 * * * Request timed out. 3 153 ms 132 ms 148 ms 10.1.2.5 4 * * * Request timed out. 5 152 ms 140 ms 134 ms linx.telecityredbus.net [195.66.224.82] 6 116 ms 109 ms 111 ms 85.90.226.205 7 143 ms 146 ms 149 ms 532-dist65-01.lon3.telecity.net [217.20.44.226]
8 117 ms 101 ms 98 ms ipt-ccp-games-1-as35834.lon3.telecity.net [217.20.44.138] 9 163 ms 159 ms 154 ms 87.237.38.200
CG
|

deathlords
|
Posted - 2009.03.13 19:35:00 -
[630]
I've seen some disconnections in Eve and I'm running it under Wine in Linux. The socket is all "hunky-dory" and then BOOM, disconnect. Nothing to do with packet loss.
I could run Wireshark and capture traffic until the disconnect, if that would help.
|
| |
|
| Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 30 40 50 .. 52 :: one page |
| First page | Previous page | Next page | Last page |