| Pages: 1 [2] 3 4 :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Storm23
   |
Posted - 2004.04.11 14:02:00 -
[31]
Puh , it's still happening and more often , anybody know if this is a problem they know about? and are trying to fix , i cant play like this , and i dont really want to unsub , but well you know..
|
Storm23
|
Posted - 2004.04.11 14:12:00 -
[32]
nm dident see nijakittens post.
|
Reckoning
|
Posted - 2004.04.11 14:28:00 -
[33]
Well i'm getting it to, I hope they get it fixed soon. I'm in the UK using Nildram as well.
I wonder how long these things take to fix. |
KIAInkZ
|
Posted - 2004.04.11 15:26:00 -
[34]
Everyone on Nildram is getting this.
I suspect it's something to do with the DOS attacks they've been getting.
I'll give it a couple of days before I give them a ring.
---
Forums/Killboard - http://www.kia-corp.co.uk |
flibble
|
Posted - 2004.04.11 15:30:00 -
[35]
Yep, I'm on Nildram & I'm getting them. I'm also getting the "grey screen" crash after being idle in a station for a while and then trying to do something.
Hope this gets sorted soon.
|
Frontfoot
|
Posted - 2004.04.11 15:51:00 -
[36]
I have just spoken to Nildram about this and they requested that I email them my tracert results whenever this happens so that they can investigate. They also asked if I could collect tracert results from other users as well so that they have more to go on. So if you are playing eve and you lose your connection can you do a tracert and post the results here...Hopefully if we can get enuf info they might be able to sort the problem out.
Thanks
|
Reckoning
|
Posted - 2004.04.11 15:56:00 -
[37]
Can you tell me how to use tracert please. I know it's a DOS command but what parameters do I need to use. Just typing tracert on it's own doesn't do anything. |
Frontfoot
|
Posted - 2004.04.11 16:08:00 -
[38]
Just the ip address of the server....which I believe is 157.157.139.10
e.g. tracert 157.157.139.10
Can you nly list tracert's from when you drop tho please, I have been finding that I get request time outs from one router immediately after a drop.
Thanks
|
Reckoning
|
Posted - 2004.04.11 17:03:00 -
[39]
OK it's just dropped again on me, here's the trace.
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 24 ms 20 ms 20 ms lon1-adsl7.nildram.net [195.112.5.1]
2 20 ms 27 ms 20 ms lon1-10.nildram.net [213.208.106.195]
3 19 ms 20 ms 21 ms lon1-6.nildram.net [195.149.20.132]
4 19 ms 20 ms 20 ms 246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109
]
5 20 ms 20 ms 20 ms pos4-0.mpr2.lhr1.uk.above.net [208.185.156.14]
6 19 ms 21 ms 20 ms ge-0-0-0-zpr2.lnt.cw.net [195.66.226.182]
7 20 ms 20 ms 21 ms bcr1.Thamesside.cw.net [166.63.210.61]
8 21 ms 21 ms 20 ms iar1-loopback.Thamesside.cw.net [166.63.210.7]
9 28 ms 29 ms 28 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6]
10 * * 23 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
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.
|
Recnac
|
Posted - 2004.04.11 17:47:00 -
[40]
Edited by: Recnac on 11/04/2004 17:52:23
I did a trace when it was working ok for comparison
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 19 ms 18 ms 19 ms lon1-adsl4.nildram.net[195.149.20.19]
3 19 ms 19 ms 19 ms lon1-9.nildram.net [213.208.106.194]
4 20 ms 19 ms 19 ms lon1-6.nildram.net [195.149.20.132]
5 18 ms 19 ms 20 ms 246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109
]
6 19 ms 19 ms 19 ms pos4-0.mpr2.lhr1.uk.above.net [208.185.156.14]
7 20 ms 21 ms 20 ms ge-0-0-0-zpr2.lnt.cw.net [195.66.226.182]
8 20 ms 20 ms 20 ms bcr3.tsd.cw.net [195.2.1.15]
9 20 ms 20 ms 20 ms iar1-loopback.Thamesside.cw.net [166.63.210.7]
10 28 ms 30 ms 32 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.21
7.6]
11 to 30 all Timouts
Trace complete.
|
Frontfoot
|
Posted - 2004.04.11 18:50:00 -
[41]
Recnac,
I have be seeing the same as you when it was working, but the few times I have dropped I then very quickly ran the tracert (I had a console window open with the command ready so that when I dropped I just hit enter in the console window) I have seen timeouts on both
iceland-telecom-ltd.Thamesside.cw.net [166.63.21
7.6]
and
246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109
]
Unfortunately I did not keep the tracert at the time :(
It also looks like reckoning experienced the timeouts on iceland-telecom-ltd.Thamesside.cw.net briefly before traffic started getting though again.
Are there any non nildram people still experiencing the regular connection drops?
|
Frontfoot
|
Posted - 2004.04.11 18:51:00 -
[42]
Recnac,
I have be seeing the same as you when it was working, but the few times I have dropped I then very quickly ran the tracert (I had a console window open with the command ready so that when I dropped I just hit enter in the console window) I have seen timeouts on both
iceland-telecom-ltd.Thamesside.cw.net [166.63.21
7.6]
and
246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109
]
Unfortunately I did not keep the tracert at the time :(
It also looks like reckoning experienced the timeouts on iceland-telecom-ltd.Thamesside.cw.net briefly before traffic started getting though again.
Are there any non nildram people still experiencing the regular connection drops?
|
Feek
|
Posted - 2004.04.11 22:30:00 -
[43]
Yeah, I've never ever been disconnected before but it happened to me quite a few times yesterday and again today. I'm with Eclipse.
K.
|
Stillborn
|
Posted - 2004.04.11 23:06:00 -
[44]
This is getting rediculous......you cant do anything really.
|
Bettermine
|
Posted - 2004.04.11 23:36:00 -
[45]
I am with One.tel, and have been experiencing these failures since Thursday. Still getting it now tonight, even with a single client running .. for no reason it will drop and you get a disconnected from server error ..
Seriously winding me up .. but even more is the complete lack of response from CCP about it ..
|
Ruthless Rynert
|
Posted - 2004.04.12 08:41:00 -
[46]
Day 3, same problems.
Maybe CCP are on holiday until tomorrow?
|
Feek
|
Posted - 2004.04.12 09:09:00 -
[47]
Same thing for me this morning, logged on for less than 20 minutes, out mining by myself with my drones and schwing. Grey screen, bounced back to the login box.
Not happy.
K.
|
Feek
|
Posted - 2004.04.12 09:20:00 -
[48]
Five minutes later, out again.
My traceroute:
C:\WINDOWS>tracert 157.157.139.10
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms my.router [192.168.0.211]
2 32 ms 21 ms 21 ms lo1-bba1.th.eclipse.net.uk [212.104.130.141]
3 22 ms 21 ms 21 ms ge5-1-core4.th.eclipse.net.uk [81.5.191.41]
4 21 ms 22 ms 21 ms 251.ge6-0.mpr2.lhr1.uk.above.net [213.161.78.89]
5 23 ms 22 ms 21 ms ge-0-0-0-zpr2.lnt.cw.net [195.66.226.182]
6 22 ms 21 ms 22 ms bcr3.tsd.cw.net [195.2.1.15]
7 30 ms 23 ms 22 ms iar1-loopback.Thamesside.cw.net [166.63.210.7]
8 22 ms 22 ms 23 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.21
7.6]
9 * * * Request timed out.
10 * * * Request timed out.
Then just timeouts. All looking pretty similar to the ones from before. It's not our ISPs causing this.
K.
|
TOXIC WASTE
|
Posted - 2004.04.12 09:47:00 -
[49]
Me too as with Nildram and game keeps crashing getting grey screen. Hope it's fixed soon(tm)
|
V2GBR
|
Posted - 2004.04.12 09:59:00 -
[50]
Were is the UNSUB buttom :(
Coz ill be using it if this carrys on.
----------
http://guc.webinventions.co.uk <-- GUC Site.
www.webinventions.co.uk <-- My eve history. |
Frontfoot
|
Posted - 2004.04.12 10:12:00 -
[51]
Feek, that tracert is normal - you are reaching the ccp firewall at that point, I was hoping to see some timeouts before you reach the thameside servers. It seems that the routers can recover very quickly and hence the tracert doesn't display any problems. You have to be very quick or the router has to be "playing up" for a few seconds in order to catch the timeouts :(
|
Frontfoot
|
Posted - 2004.04.12 10:14:00 -
[52]
People, it might also be useful for everyone who is having these problems to say which area they live in, what time the disconnect happened and which isp they are with...
|
Storm23
|
Posted - 2004.04.12 10:33:00 -
[53]
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 13 ms 13 ms 13 ms centrica1-hg3.ilford.broadband.bt.net [217.41.13
2.202]
2 13 ms 13 ms 12 ms 217.41.132.161
3 15 ms 15 ms 14 ms 217.41.132.238
4 14 ms 14 ms 14 ms 213.78.128.3
5 14 ms 14 ms 13 ms 212.67.120.74
6 13 ms 14 ms 14 ms 212.67.120.61
7 14 ms 13 ms 14 ms 90.ge1-0.er1a.lhr4.uk.above.net [213.161.69.42]
8 15 ms 14 ms 14 ms so-2-2-0.cr2.lhr4.uk.above.net [208.184.231.129]
9 17 ms 14 ms 15 ms pos7-0.mpr2.lhr1.uk.above.net [208.184.231.169]
10 14 ms 14 ms 14 ms pos1-0.pr1.lhr1.uk.above.net [208.184.231.74]
11 15 ms 15 ms 69 ms ge-2-1-0-zpr1.lnt.cw.net [195.66.224.182]
12 14 ms 15 ms 15 ms zcr2-ge-2-1-0.Londonlnt.cw.net [166.63.222.146]
13 88 ms 14 ms 13 ms 206.24.168.121
14 15 ms 14 ms 18 ms iar1-loopback.Thamesside.cw.net [166.63.210.7]
15 44 ms 25 ms 16 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.21
7.6]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19
Ok here is mine from 5mins ago , i live in essex , england and use one-tel adsl.
|
Frontfoot
|
Posted - 2004.04.12 10:46:00 -
[54]
Storm, nothing wrong with that tracert either, the connection must have recovered by then.
The ones I have had so far are:
1 <1 ms <1 ms <1 ms 192.168.0.2
2 66 ms 43 ms 55 ms lon1-adsl9-2.nildram.net [81.6.205.65]
3 17 ms 18 ms 17 ms lon1-9.nildram.net [213.208.106.194]
4 17 ms 77 ms 26 ms lon1-6.nildram.net [195.149.20.132]
5 17 ms 17 ms 51 ms 246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109]
6 30 ms 17 ms 17 ms pos4-0.mpr2.lhr1.uk.above.net [208.185.156.14]
7 * * * Request timed out.
8 * 62 ms 17 ms bcr3.tsd.cw.net [195.2.1.15]
9 17 ms 18 ms 47 ms iar1-loopback.Thamesside.cw.net [166.63.210.7]
10 23 ms 20 ms 18 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6]
11 * * * Request timed out.
1 <1 ms 1 ms <1 ms 192.168.0.2
2 22 ms 16 ms 17 ms lon1-adsl9-2.nildram.net [81.6.205.65]
3 19 ms 30 ms 17 ms lon1-9.nildram.net [213.208.106.194]
4 38 ms 22 ms 17 ms lon1-6.nildram.net [195.149.20.132]
5 78 ms 24 ms 17 ms 246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109]
6 64 ms 36 ms 16 ms pos4-0.mpr2.lhr1.uk.above.net [208.185.156.14]
7 17 ms 35 ms 17 ms ge-0-0-0-zpr2.lnt.cw.net [195.66.226.182]
8 45 ms 17 ms 25 ms bcr3.tsd.cw.net [195.2.1.15]
9 28 ms * 76 ms iar1-loopback.Thamesside.cw.net [166.63.210.7]
10 60 ms 93 ms 42 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6]
11 * * * Request timed out.
1 <1 ms 2 ms <1 ms 192.168.0.2
2 16 ms 26 ms 18 ms lon1-adsl9-2.nildram.net [81.6.205.65]
3 30 ms 21 ms 17 ms lon1-9.nildram.net [213.208.106.194]
4 16 ms 17 ms 18 ms lon1-6.nildram.net [195.149.20.132]
5 17 ms 40 ms 17 ms 246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109]
6 * 17 ms 17 ms pos4-0.mpr2.lhr1.uk.above.net [208.185.156.14]
7 20 ms 42 ms 43 ms ge-0-0-0-zpr2.lnt.cw.net [195.66.226.182]
8 17 ms 16 ms 19 ms bcr3.tsd.cw.net [195.2.1.15]
9 19 ms 18 ms 23 ms iar1-loopback.Thamesside.cw.net [166.63.210.7]
10 72 ms 37 ms 20 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6]
11 * * * Request timed out.
1 1 ms <1 ms <1 ms 192.168.0.2
2 23 ms 77 ms 38 ms lon1-adsl9-2.nildram.net [81.6.205.65]
3 62 ms 41 ms 17 ms lon1-9.nildram.net [213.208.106.194]
4 21 ms 17 ms 18 ms lon1-6.nildram.net [195.149.20.132]
5 17 ms 17 ms 17 ms 246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109]
6 45 ms 20 ms 26 ms pos4-0.mpr2.lhr1.uk.above.net [208.185.156.14]
7 * * 87 ms ge-0-0-0-zpr2.lnt.cw.net [195.66.226.182]
8 57 ms 21 ms 18 ms bcr3.tsd.cw.net [195.2.1.15]
9 18 ms 44 ms 37 ms iar1-loopback.Thamesside.cw.net [166.63.210.7]
10 335 ms 343 ms 392 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6]
11 * * * Request timed out.
The last hop is expected to time out....but the ones that time out before then I think may be where the problem lies....
|
Andrue
|
Posted - 2004.04.12 11:54:00 -
[55]
Ah ha - caught my first glitch:
Target Name: N/A
IP: 157.157.139.10
Date/Time: 12/04/2004 12:26:48 to 12/04/2004 12:29:03
1 2 ms 3 ms 2 ms 3 ms 2 ms 2 ms 2 ms 3 ms 2 ms 2 ms [192.168.0.1]
2 26 ms 26 ms 29 ms 29 ms 30 ms 16 ms 18 ms 19 ms 21 ms 21 ms lon1-adsl4.nildram.net [195.149.20.19]
3 24 ms 24 ms 26 ms 26 ms 27 ms 29 ms 30 ms 16 ms 17 ms 20 ms lon1-9.nildram.net [213.208.106.194]
4 21 ms 24 ms 24 ms 25 ms 27 ms 28 ms 30 ms 31 ms 32 ms 17 ms lon1-6.nildram.net [195.149.20.132]
5 20 ms 20 ms 22 ms 22 ms 25 ms 25 ms 26 ms 27 ms 27 ms 28 ms 246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109]
6 17 ms 19 ms 21 ms 21 ms 22 ms 23 ms 26 ms 27 ms 27 ms 28 ms pos4-0.mpr2.lhr1.uk.above.net [208.185.156.14]
7 29 ms 31 ms 17 ms 18 ms 20 ms 21 ms 22 ms 23 ms 24 ms * ge-0-0-0-zpr2.lnt.cw.net [195.66.226.182]
8 27 ms 28 ms N/A 30 ms N/A N/A N/A 20 ms 22 ms * bcr3.tsd.cw.net [195.2.1.15]
9 N/A N/A N/A N/A N/A N/A N/A N/A 20 ms * [206.24.168.97]
10 24 ms 24 ms 175 ms 28 ms 31 ms 29 ms 30 ms 30 ms 19 ms * iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6]
11 * * * * * * * * * * [-]
Hop 7 (Cable and Wireless) dropped a packet. It's interesting (though perhaps normal) that C&W routers keep changing. Presumably this is at least suggestive of load balancing. Maybe their network is a bit stressed right now?
--
(Battle hardened miner)
[Brackley, UK]
WARNING:This post may contain large doses of reality. |
Riggwelter
|
Posted - 2004.04.12 12:59:00 -
[56]
I have pingplotter running in the background and the problem seems to occur through the following hops
195.66.226.182 err 5% loss
166.63.210.61 err 7% loss
166.63.210.7 err 10% loss
166.63.217.6 err 5% loss
Unfortunatly i saved the trace as a jpeg but i have emailed it to nildram support i may get it posted on to the web at some point.
They who shout the loudest normally have the least to say. |
Recnac
|
Posted - 2004.04.12 16:03:00 -
[57]
Edited by: Recnac on 12/04/2004 16:04:58
Tracing route to 157.157.139.10 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms my.router [192.168.1.1]
2 19 ms 18 ms 19 ms lon1-adsl4.nildram.net [195.149.20.19]
3 20 ms 18 ms 19 ms lon1-9.nildram.net [213.208.106.194]
4 20 ms 19 ms 20 ms lon1-6.nildram.net [195.149.20.132]
5 20 ms 20 ms 20 ms 246.ge6-0.mpr1.lhr1.uk.above.net [213.161.78.109
]
6 19 ms 20 ms 19 ms pos4-0.mpr2.lhr1.uk.above.net [208.185.156.14]
7 26 ms 20 ms 20 ms ge-0-0-0-zpr2.lnt.cw.net [195.66.226.182]
8 25 ms 19 ms 20 ms bcr1.Thamesside.cw.net [166.63.210.61]
9 19 ms 21 ms 21 ms 206.24.172.65
10 * 25 ms 26 ms iceland-telecom-ltd.Thamesside.cw.net [166.63.217.6]
ran this when i couldnt log in after a drop and shows a * on the last iceland hop
|
Chencherra
|
Posted - 2004.04.12 16:18:00 -
[58]
Edited by: Chencherra on 12/04/2004 16:21:08
hmmm...my problem is even worse .
i can log in and select my char, but it takes a while .
and the client says authentificating or something . and last thing i see is this screen : http://bill-wilcox.piranho.com/2004.04.12.16.11.42.JPG
hm i got this screen for like 20 minutes now .
the loading-bar in the middle keeps moving .
but the space just doesnt appear .
ive got 14 day trial account .
im from germany , my ISP is telekom .
anything else works fine . any game !
must be something with server , refusing connections or something .
i hope they fix it soon .
|
Frontfoot
|
Posted - 2004.04.12 16:24:00 -
[59]
Chen, that is a minor problem...looks like a node just died...it will be lagging a bit and ppl will have problems getting back on for a little while but it will probably be back to normal for you before too long. Nothing to worry about.
|
Ragnoroc
|
Posted - 2004.04.12 16:27:00 -
[60]
I have been monitoring this for the past 36 hours.
It seems that CCP have 3 gateways to the UK, hosted in the docklands, and c&w provide the access to the linx net around london.
It seems that Nildram use uk.above.net to peer onto the linx.
Both uk.above.net and cw.net have been timing out along with gateway .1 to CCP. The load balancing used for the three gateways is not very impressive as .1 is most loaded .2 is less loaded and .3 always returns perfect ping times
Now it seems we have network overload from this afternoon as when a few dropped and logged back in it took thousands of UK users out.
CCP seem to have a serious bottleneck in thier networking to the UK and with the number growing as they are meltdown is getting more likely. At least that will lose some people as they will give up through frustration and maybe things will get back to normal. |
| |
|
| Pages: 1 [2] 3 4 :: one page |
| First page | Previous page | Next page | Last page |