| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Frontfoot
   |
Posted - 2004.04.10 15:06:00 -
[1]
I am in the same boat - I am losing connection every 30 mins. I do not think this is an isp issue as my router says I have not lost my connection at all and I had a download going in background that did not drop. I also run multiple accounts and most of the time only one or 2 of them lose connection to the server - altho sometimes they all do. On the help channel there are lots of people who were talking about the same problem.
This has only been happening today tho - was ok prior to today..
|
Frontfoot
|
Posted - 2004.04.10 15:54:00 -
[2]
I am on Nildram too - but I don't think that is the problem for the same reasons you say (and becuase only some of my accounts drop)
<waves to Andrue in the help channel>
Just Ice.
|
Frontfoot
|
Posted - 2004.04.10 15:55:00 -
[3]
One of my friends has same problem too and he is using BT adsl...
|
Frontfoot
|
Posted - 2004.04.10 22:23:00 -
[4]
I thought it had recovered too...I managed over 2 hours without a disconnection but then bang....2 of my accounts dropped so I do not think it is fixed yet :(
|
Frontfoot
|
Posted - 2004.04.11 15:51:00 -
[5]
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
|
Frontfoot
|
Posted - 2004.04.11 16:08:00 -
[6]
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
|
Frontfoot
|
Posted - 2004.04.11 18:50:00 -
[7]
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 -
[8]
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.12 10:12:00 -
[9]
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 -
[10]
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...
|
Frontfoot
|
Posted - 2004.04.12 10:46:00 -
[11]
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....
|
Frontfoot
|
Posted - 2004.04.12 16:24:00 -
[12]
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.
|
Frontfoot
|
Posted - 2004.04.12 22:12:00 -
[13]
The lag was caused by a node dying today....shortly afterwards (an hour later or so) things picked up again...thankfully that does not happen that often and is only a minor annoyance.
|
| |
|