| Pages: 1 2 [3] 4 5 6 7 8 9 10 :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 3 post(s) |
Panametrics
The Terrifying League Of Dog Fort
Eternal Evocations
0
   |
Posted - 2012.04.12 03:37:00 -
[61] - Quote
Just happened to me 3 times tonight, and a few other times in the passed few days. Had no issues before.
The eve website also does not work for this period of time while I cant reconnect(1-2 mins)
All my other internets are working fine :D
Edit: I'm in Canada |
Velaren
Freelance Economics Astrological resources
Tactical Narcotics Team
0
|
Posted - 2012.04.12 03:48:00 -
[62] - Quote
Fallo Gallentine wrote:Same here.
IINET, ADSL2+, Australia, 150m from exchange ;-)
Everything has been perfect until a few weeks ago, a bit hard to pinpoint the exact date, which is why I too had originally thought it was related to the launcher and/or client.
It is not a localised connection issue, as all other interactive interwebs applications are still connected (mumble, rdp, ssh, etc), only eve client restarts and I did verify quickly that the modem link has not dropped out for weeks. Have not further monitored connectivity as yet because of this reason, but it may be an upstream connection between iinet and ccp.
I have run LogServer.exe before client start and whilst client disconnected randomly, and saved the workspace. What do we do with this little gem?
Regds
Fallo
i'm going to quote a reply from GM about what to do with those files:
C) Finding the crashdump ( if one is created )
Press Windows Key + R and paste the following line into the Run window.
%USERPROFILE%\Local Settings\Application Data\CCP\EVE\ if you use Windows XP %LOCALAPPDATA%\CCP\EVE\ if you use Windows Vista or Windows 7
Find the .dmp file with the most recent time stamp. Files called #error*.txt are useless.
D). Also if you haven't already sent us your Dxdiag files run the DirectX diagnostics tool:
1. Press 'Start' and select 'run'. Type dxdiag and hit enter. When you do this, a window will pop up.
2. Click the "Save All Information" button that's located in its lower right corner.
When you've gathered all the files compress them all into a .zip or .rar file ( depending on which compression program you use ) Then attach the compressed file to either this e-mail reply ( sent to the e-mail you associated with your EVE account ) or by using the attachment box by logging in to "My Petitions" on our homepage ( http://support.eve-online.com/Pages/Petitions/MyPetitions.aspx ) open the petition there. An attachment box is presented after opening the petition.
|
nulab jones
Assisted Genocide
Unprovoked Aggression
1
|
Posted - 2012.04.12 06:09:00 -
[63] - Quote
Tried battleping today form the main PC, not a single DC
Laptop that is not running battleping has crashed about 5 times.
Maybe the changes to the route info that mort suggested will help.
Fingers crossed |
Stella Sing-Love
Australasian Expeditionary Forces
Apocalypse Now.
0
|
Posted - 2012.04.12 08:32:00 -
[64] - Quote
I still get drop outs from time to time. The graph pretty much looks just like DooDoo Gum's - high packet loss and about 100ms latency added to what it was previously. I'll have a ping plotter session saved in a couple of hours. |
Mollernak
Oberon Incorporated
RAZOR Alliance
4
|
Posted - 2012.04.12 09:15:00 -
[65] - Quote
It actually got a bit better for me the other week for a few days, but it's back to being basically unplayable for my wife and I atm
Followed the recommendations in the response to the my petition on my other account (including flashing all my network devices routers/modem/etc).
Running PingPlotter constantly atm, with it generating email alerts for each scenario that would result in a disconnection, got about 50 of those in the last 24 hours.
In New Zealand, and pretty much ready to hang up the hats of our 7 accounts. |
Bending Unit 22
The Asteroid is Depleted
Sentinels of Sukanan Alliance
2
|
Posted - 2012.04.12 12:17:00 -
[66] - Quote
My route has changed around the time of the bounce today... it is now
Quote:
Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms gordon [192.168.1.254]
2 16 ms 16 ms 17 ms nexthop.nsw.iinet.net.au [203.215.17.248]
3 17 ms 17 ms 16 ms te1-1.syd-ult-bdr1.iinet.net.au [203.215.16.22]
4 17 ms 17 ms 17 ms xe-1-1-0-0.syd-ult-core1.iinet.net.au [203.215.20.30]
5 18 ms 17 ms 17 ms 26629.siko06.cu.reach.com [134.159.126.45]
6 17 ms 18 ms 17 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1]
7 157 ms 157 ms 156 ms i-0-2-0-0.1wlt-core01.bx.reach.com [202.84.140.21]
8 202 ms 202 ms 202 ms i-1-2.eqla01.bi.reach.com [202.84.251.174]
9 232 ms 221 ms 215 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
10 396 ms 402 ms 349 ms 204.245.39.38
11 306 ms 306 ms 307 ms srv248-e.ccp.cc [87.237.36.248]
12 306 ms 306 ms 305 ms srv200-g.ccp.cc [87.237.38.200]
Trace complete.
7 less hops, and around 100ms improvement in ping. The main diff though? Previously I was averaging 10-15% packet loss to the final destination, the new one seems to be about 1.5%
No hiccups so far. Fingers crossed. |
Matuk Grymwal
Bite Me inc
Exhale.
2
|
Posted - 2012.04.12 13:39:00 -
[67] - Quote
So I've had ping plotter running all (AU) evening, so from before DT to 3 hours after. Since DT I've seen one block of about 30s of packet loss (which is generally long enough to disconnect eve). However completely green otherwise. Certainly better. |
DooDoo Gum
Center for Advanced Studies
Gallente Federation
17
|
Posted - 2012.04.12 21:51:00 -
[68] - Quote
Excitedly log in to give EVE another go...
All seems to be going well, even get a nice drop in latency which runs steady for a while....
30 mins in, dropped connection...
http://i.imgur.com/kGARU.jpg
Getting REALLY pi**ed off now ! |
Linolea Austrene
Hidden Agenda
Deep Space Engineering
0
|
Posted - 2012.04.12 22:42:00 -
[69] - Quote
Had very few disconnects from the EVE client for the year that I have been playing. All of a sudden since the 12 April patch I disconnected 3 times in a couple hours. Aus player here. |
Lucus Ranger
Solar Wind
Test Friends Please Ignore
0
|
Posted - 2012.04.12 23:47:00 -
[70] - Quote
Same problem as everyone else. It keeps logging/crashing me to desktop. It's pretty random I've noticed; also I can have both my accounts online and only one will crash while the other is fine... Been like this for a while now. |
|
|
DooDoo Gum
Center for Advanced Studies
Gallente Federation
17
|
Posted - 2012.04.13 00:31:00 -
[71] - Quote
Lucus Ranger wrote:Same problem as everyone else. It keeps logging/crashing me to desktop. It's pretty random I've noticed; also I can have both my accounts online and only one will crash while the other is fine... Been like this for a while now.
Yeah, i have all accounts that are logged in disconnect simultaneously |
nulab jones
Assisted Genocide
Unprovoked Aggression
1
|
Posted - 2012.04.13 01:59:00 -
[72] - Quote
Issue is still not fixed, i just turned battle ping off to test it and sure enough all dced within 20 mins.
Back to pingplotter we go |
Byerly Plodalong
Pator Tech School
Minmatar Republic
0
|
Posted - 2012.04.13 05:32:00 -
[73] - Quote
Same problem as everyone else from iiNet in Australia. I'm a new player but this thread gives me hope that my relationship with Eve will not be short lived! |
Linolea Austrene
Hidden Agenda
Deep Space Engineering
0
|
Posted - 2012.04.13 10:12:00 -
[74] - Quote
This was the situation during normal operation:
Quote:Pinging 87.237.38.200 with 32 bytes of data:
Reply from 87.237.38.200: bytes=32 time=291ms TTL=116
Reply from 87.237.38.200: bytes=32 time=291ms TTL=116
Reply from 87.237.38.200: bytes=32 time=291ms TTL=116
Reply from 87.237.38.200: bytes=32 time=291ms TTL=116
Ping statistics for 87.237.38.200: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: Minimum = 291ms, Maximum = 291ms, Average = 291ms
tracert 87.237.38.200
Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 14 ms 14 ms 14 ms nexthop.wa.iinet.net.au [203.215.5.243]
3 14 ms 14 ms 13 ms te7-2.per-qv1-bdr1.iinet.net.au [203.215.4.20]
4 62 ms 62 ms 62 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20]
5 61 ms 63 ms 62 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.137]
6 65 ms 64 ms 62 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18]
7 64 ms 88 ms 65 ms xe-0-1-0-0.syd-ult-core1.iinet.net.au [203.215.20.102]
8 63 ms 60 ms 60 ms 26629.siko06.cu.reach.com [134.159.126.45]
9 65 ms 65 ms 65 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1]
10 202 ms 202 ms 202 ms i-0-0-0-0.1wlt-core01.bx.reach.com [202.84.141.146]
11 249 ms 250 ms 249 ms i-3-4.eqla01.bi.reach.com [202.84.251.154]
12 288 ms 272 ms 298 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
13 291 ms 291 ms 299 ms 204.245.39.42
14 291 ms 291 ms 291 ms srv245-e.ccp.cc [87.237.36.245]
15 291 ms 291 ms 291 ms srv248-e.ccp.cc [87.237.36.248]
16 292 ms 291 ms 292 ms srv200-g.ccp.cc [87.237.38.200]
Trace complete.
Then I was dumped from the client and pinged with the following result:
Quote:ping 87.237.38.200
Pinging 87.237.38.200 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 87.237.38.200: bytes=32 time=292ms TTL=116
Ping statistics for 87.237.38.200: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds: Minimum = 292ms, Maximum = 292ms, Average = 292ms
And later dumped again and attempted tracert immediately and was greeted with:
Quote:Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.2.1
2 13 ms 13 ms 13 ms nexthop.wa.iinet.net.au [203.215.5.243]
3 14 ms 14 ms 14 ms te7-2.per-qv1-bdr1.iinet.net.au [203.215.4.20]
4 62 ms 62 ms 62 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20]
5 62 ms 62 ms 62 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.137]
6 61 ms 62 ms 62 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18]
7 106 ms 64 ms 64 ms xe-0-1-0-0.syd-ult-core1.iinet.net.au [203.215.20.102]
8 60 ms 60 ms 60 ms 26629.siko06.cu.reach.com [134.159.126.45]
9 65 ms 65 ms 65 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1]
10 203 ms 202 ms 202 ms i-0-0-0-0.1wlt-core01.bx.reach.com [202.84.141.146]
11 250 ms 249 ms 249 ms i-3-4.eqla01.bi.reach.com [202.84.251.154]
12 274 ms 275 ms 273 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
13 * * 299 ms 204.245.39.42
14 296 ms 477 ms 399 ms srv245-e.ccp.cc [87.237.36.245]
15 296 ms 296 ms 300 ms srv248-e.ccp.cc [87.237.36.248]
16 296 ms 296 ms 296 ms srv200-g.ccp.cc [87.237.38.200]
Trace complete.
Hope this helps identify the problem. Issue wit the onnection to 204.245.39.42? |
Leads Dent
Dark Fusion Industries
Limitless Inc.
0
|
Posted - 2012.04.13 18:07:00 -
[75] - Quote
Adding my name to the list. Australia too.
Happened twice tonight and has been happening over the past week or so.
Did this traceroute about 40 mins after the second crash so not sure if it will help but in any case.
Tracing route to srv200-g.ccp.cc [87.237.38.200]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms bob.iad [10.1.1.1]
2 18 ms 18 ms 19 ms nexthop.wa.iinet.net.au [203.215.5.243]
3 18 ms 19 ms 21 ms te7-2.per-qv1-bdr2.iinet.net.au [203.215.4.38]
4 66 ms 68 ms 66 ms po1-100.per-qv1-bdr1.iinet.net.au [203.215.20.13
0]
5 66 ms 67 ms 66 ms te4-4.ade-pipe-bdr2.iinet.net.au [203.215.20.20]
6 70 ms 71 ms 71 ms po4-100.ade-pipe-bdr1.iinet.net.au [203.215.20.1
37]
7 70 ms 71 ms 70 ms te6-4.mel-pipe-bdr1.iinet.net.au [203.215.20.18]
8 66 ms 68 ms 68 ms te6-1-100.mel-pipe-bdr2.iinet.net.au [203.215.20
.139]
9 73 ms 77 ms 73 ms xe-0-1-0-0.syd-mas-core1.iinet.net.au [203.215.2
0.106]
10 156 ms 72 ms 71 ms ae0.syd-ult-core1.iinet.net.au [203.215.20.110]
11 72 ms 71 ms 71 ms 26629.siko06.cu.reach.com [134.159.126.45]
12 75 ms 76 ms 74 ms i-0-7-1-0.sydo-core02.bi.reach.com [202.84.223.1
]
13 214 ms 212 ms 211 ms i-0-0-0-0.1wlt-core01.bx.reach.com [202.84.141.1
46]
14 278 ms 405 ms 411 ms i-1-2.eqla01.bi.reach.com [202.84.251.174]
15 243 ms 244 ms 243 ms gblx-peer.eqla01.pr.reach.com [134.159.63.202]
16 405 ms 295 ms 295 ms 204.245.39.42
17 304 ms 301 ms 303 ms srv245-e.ccp.cc [87.237.36.245]
18 303 ms 302 ms 303 ms srv248-e.ccp.cc [87.237.36.248]
19 297 ms 297 ms 300 ms srv200-g.ccp.cc [87.237.38.200]
Trace complete. |
Linolea Austrene
Hidden Agenda
Deep Space Engineering
0
|
Posted - 2012.04.13 22:57:00 -
[76] - Quote
Reading through the thread it appears that whatever was changed on Thursday (EVE time) which was Friday morning when I patched, seems coincidently to have resulted in a few Aussie players posting that they have this issue. I applied the last patch Friday morning and the disconnects started happening at a rate of at least 1-2 per hour.
Is CCP going to revert/fix the Thursday change or we Aussies just going to have to fork out for third party software to make EVE work?
|
Glijaron
The Oasis Group
Combat Mining and Logistics
0
|
Posted - 2012.04.13 23:12:00 -
[77] - Quote
There was an issue with parsing this post's BBCode |
Bending Unit 22
The Asteroid is Depleted
Sentinels of Sukanan Alliance
2
|
Posted - 2012.04.14 00:33:00 -
[78] - Quote
Well, I can report I'm still solid as a rock since the change the other day, not a single drop.
Didn't post this to gloat, just to point out that it defintely looks more like a network issue, not a client one, in IMO.
I've also looked at my new route compared to the route everyone else seems to be taking and they are different... in the last 3 hops, the following are common to everyone that's posted a traceroute:
srv245-e.ccp.cc [87.237.36.245]
srv248-e.ccp.cc [87.237.36.248]
srv200-g.ccp.cc [87.237.38.200]
those are usually, but not always, proceeded by this node
[204.245.39.42]
With my new route, the last hops are
srv248-e.ccp.cc [87.237.36.248]
srv200-g.ccp.cc [87.237.38.200]
it no longer hits
srv245-e.ccp.cc [87.237.36.245]
and the preceeding node is also different, being
[204.245.39.38]
This might be a logically leap too far, but based on the above, it would seem traffic going via srv245-e.ccp.cc [87.237.36.245] or the nodes that route to it is where the fault may lie. |
Linolea Austrene
Hidden Agenda
Deep Space Engineering
0
|
Posted - 2012.04.14 01:23:00 -
[79] - Quote
Unfortunately 204.245.39.42 seems to be the one causing my issues, and I suspect issues for other Aussie players above. I wish to know whether the change implemented by CCP Mort is encouraging our packets to go through this dodgy server. Sorry I am not techie enough to know the correct terminology, but from several tracert's I have run, they all seem to hang at that point longer than all the other jumps. As mentioned before, I almost never had unexplained drops in a year of playing, and now they are happening regularly to the point of making EVE unplayable. |
Glijaron
The Oasis Group
Combat Mining and Logistics
0
|
Posted - 2012.04.14 01:27:00 -
[80] - Quote
This IP 204.245.39.42 also shows up in a thread from 2010 and it's Global Crossing as far as I can tell.
Thread Here
Obviously that router needs fine tuning with a sledge  |
|
|
Aethraen Azizora
EVE University
Ivy League
0
|
Posted - 2012.04.14 04:09:00 -
[81] - Quote
On Wed/Thu (Aus time) it was all good again -- no disconnects. I did a PingPlotter dump and saw I was being routed a different way, via the PaloAlto/Newark/London.as6453.net servers. No 204.245.39.42, as there had been before. There were a heap more hops and some low levels of packet loss, but the client seemed to handle it OK.
After downtime on Thu and into Friday, the disconnects started again. I fired up PingPlotter and saw the routing had changed back and I was once again going through 204.245.39.42 just before hitting the three CCP servers. And during the disconnects I was seeing 100% packet loss across all four.
I installed BattlePing and chose 'London' as the server to use. I've had no disconnects while using it.
Primary is Global Crossing.
Global Crossing is primary. |
Kimberly Fairchild
Golden Eagle Federation
0
|
Posted - 2012.04.14 06:20:00 -
[82] - Quote
Singaporean Pilot here, experiencing a large spike in drop-outs ever since the April 12th patch. |
Beliandra
Republic University
Minmatar Republic
0
|
Posted - 2012.04.14 06:25:00 -
[83] - Quote
Bending Unit 22 wrote:With my new route, the last hops are
srv248-e.ccp.cc [87.237.36.248]
srv200-g.ccp.cc [87.237.38.200]
it no longer hits
srv245-e.ccp.cc [87.237.36.245]
and the preceeding node is also different, being
[204.245.39.38]
This might be a logically leap too far, but based on the above, it would seem traffic going via srv245-e.ccp.cc [87.237.36.245] or the nodes that route to it is where the fault may lie.
My experience matches the Bending Unit.
My last hops are the same..
11 296 ms 294 ms 296 ms 204.245.39.38
12 295 ms 298 ms 297 ms srv248-e.ccp.cc [87.237.36.248]
13 296 ms 295 ms 299 ms srv200-g.ccp.cc [87.237.38.200]
And since the routing change, I have not had a single drop, after having had 1-2 every hour without fail for the previous week+, when I did have srv245-e.ccp.cc [87.237.36.245] on my route.
Additionally, the new route is shorter and faster, 13 hops compared to 19 when it was going via as6453.net. and under 300ms (from Sydney) compared to approximately 330 previously. |
Matuk Grymwal
Bite Me inc
Exhale.
2
|
Posted - 2012.04.14 09:28:00 -
[84] - Quote
I'm seeing the same behaviour after the first tweaks were made a couple of days ago. I.e. it's a lot better as I rarely get packet loss but I still get the occasional extended period of packet loss which is long enough to disconnect the client. |
hedonicus
The Raj Corporation
0
|
Posted - 2012.04.14 11:35:00 -
[85] - Quote
http://s19.postimage.org/5fxt0vmc3/srv200_g_ccp_cc.gif
same as everyone else . unplayable.
|
nulab jones
Assisted Genocide
Unprovoked Aggression
1
|
Posted - 2012.04.14 11:46:00 -
[86] - Quote
Another DT complete and 5 accounts dced within 5 mins of loggin in.
No screenshot of ping plotter this time but exactly them same as the previous ones |
xxwaynoxx
The Silhouette Group
2
|
Posted - 2012.04.14 12:25:00 -
[87] - Quote
ok, 4 days later and the people who arent ignoring us have forgotten us?
you have an IP that is causing problems, why are we still hitting problems?
Are we supposed to pay someone else to solve Eveonline's problems? ie Battleping?
If so, let us know. I would have thought that there were enough of us rusting around to to have someone comment more than every 4 days..........
oh, btw, I get this **** from another net provider in Aus - TPG - find some way for us MULTIPLE INCOME SOURCE single Eve enoyers to keep going..... |
Leads Dent
Dark Fusion Industries
Limitless Inc.
0
|
Posted - 2012.04.14 13:13:00 -
[88] - Quote
Still dropping out today.
After first drop out I ran with ping -t going.
This is what it was like on second drop out.
Reply from 87.237.38.200: bytes=32 time=296ms TTL=116
Reply from 87.237.38.200: bytes=32 time=299ms TTL=116
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 87.237.38.200: bytes=32 time=297ms TTL=116
Reply from 87.237.38.200: bytes=32 time=297ms TTL=116
During this time I could not contact eveonline.com however was still connecting to other websites fine.
And again.
Reply from 87.237.38.200: bytes=32 time=297ms TTL=116
Reply from 87.237.38.200: bytes=32 time=298ms TTL=116
Request timed out.
Request timed out.
Request timed out.
Reply from 87.237.38.200: bytes=32 time=298ms TTL=116
Reply from 87.237.38.200: bytes=32 time=297ms TTL=116
This time I lagged but it did not crash the client.
|
MasterDebater
No Crabs Allowed
1
|
Posted - 2012.04.14 20:36:00 -
[89] - Quote
xxwaynoxx wrote:ok, 4 days later and the people who arent ignoring us have forgotten us?
you have an IP that is causing problems, why are we still hitting problems?
Are we supposed to pay someone else to solve Eveonline's problems? ie Battleping?
If so, let us know. I would have thought that there were enough of us rusting around to to have someone comment more than every 4 days..........
oh, btw, I get this **** from another net provider in Aus - TPG - find some way for us MULTIPLE INCOME SOURCE single Eve enoyers to keep going.....
The first reply was shortly after I started PMing CCP employees directly. It's hard to tell if they are legitimately working on it or just trying to sate us until we unsub and forget about this. As I cannot seem to replicate the issue any longer due to actual issues with my ISP that have started up, I didn't feel comfortable doing it myself. However, if you want a response you should contact the people who need to respond.
Worst case scenario they ban you from paying for a game you can't play. |
Glijaron
The Oasis Group
Combat Mining and Logistics
0
|
Posted - 2012.04.14 23:11:00 -
[90] - Quote
Aethraen Azizora wrote:I installed BattlePing and chose 'London' as the server to use. I've had no disconnects while using it..
Have done the same and it works great, no discos at all while using Battleping. The thing is, after the trial I'm kind of stuck because I really don't want to pay for something else to make EvE work correctly. Maybe only $5 a month but meh, it's all about the principle of the matter.
If CCP rectified/looked into it in the past, why can't they respond now and let us know their working on it?
Anything is better than nothing imo. 6 days til Battleping trial runs out.
|
|
|
|
|
| |
|
| Pages: 1 2 [3] 4 5 6 7 8 9 10 :: one page |
| First page | Previous page | Next page | Last page |