| Pages: 1 [2] 3 :: one page |
| Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Fivo Asia
   |
Posted - 2007.04.20 14:00:00 -
[31]
If CCP is still watching the thread, I'm getting the same problem this morning and traceroute is showing the problem far outside America:
traceroute to 87.237.38.200 (87.237.38.200), 30 hops max, 38 byte packets
1 10.142.20.1 (10.142.20.1) 30.827 ms 10.892 ms 9.880 ms
2 cv1xhbrc01-gex0919.sd.sd.cox.net (68.6.10.130) 12.275 ms 11.225 ms 8.234 ms
3 elcnsysc02-gex0903.sd.sd.cox.net (68.6.8.132) 8.780 ms 7.519 ms 10.143 ms
4 fed1dsrj01-ge600.0.rd.sd.cox.net (68.6.8.2) 8.268 ms 16.657 ms 18.753 ms
5 langbbr01-as0.r2.la.cox.net (68.1.0.230) 24.597 ms 15.155 ms 13.643 ms
6 ge1-3.fr3.lax.llnw.net (69.28.144.141) 14.502 ms 16.216 ms 17.934 ms
7 ve6.fr4.lax.llnw.net (69.28.171.206) 19.325 ms 14.080 ms 31.128 ms
8 ge1-3.fr3.sjc.llnw.net (69.28.171.118) 30.193 ms 24.440 ms 27.706 ms
9 ve5.fr4.sjc.llnw.net (69.28.171.210) 25.017 ms 24.017 ms 23.937 ms
10 ge1-1.fr3.ord.llnw.net (69.28.171.65) 69.471 ms 67.718 ms 69.692 ms
11 tge11-3.fr3.lga.llnw.net (69.28.171.194) 100.644 ms 101.259 ms 105.244 ms
12 ge1-2.fr3.lon.llnw.net (69.28.171.126) 178.929 ms 173.373 ms 168.340 ms
13 ccp.ve201.fr3.lon.llnw.net (87.248.208.150) 170.043 ms 175.733 ms 168.179 ms
14 * * *
15 * * *
16 * * *
17 * *
That's the Netherlands where I am see the stalling occur, at least to the traditional 87.237.38.200 IP we've connected to in the past.
|
Melek Thervold
|
Posted - 2007.04.20 17:17:00 -
[32]
Still not working.
I called Cox, and after a lengthy attempt to get things to work, they concluded that there are no problems on their end.
From the sound of it, CCP claims the same thing.
Unfortunately, I have no other ISP options where I live (other then dial-up), and since nobody wants to take the responsibility to fix whatever broke, I guess that's goodbye to Eve then.
|
bonerboner
|
Posted - 2007.04.20 22:16:00 -
[33]
 Originally by: 0lorin
Originally by: LORD IZE
i hope we get reimbursed for time lost here.
We are not responsible for ISP issues and therefore will not be reinbursing lost time.
everyone in this thread appears to be using COX for an ISP, it's best you get in contact with them. currently i'm aware of no server issues.
Of course you are not, you barely take responsibility for your own incompetence so you will certainly blame it on others. Since the problem directly corresponded with your down time I am sure it is Cox's fault and not your own. And if you want to avoid reimbursing us at least learn to spell the word.
p.s. it is just after down time again and the problem is back, good job CCP.
While I understand this may be a difficult issue to troubleshoot and both parties might not be able to tell if it is or isn't on their end. The problem DID just happen to start with the downtime which leads me to believe it wasn't my beloved COX :) . I'm on vacation so I haven't had the chance to talk to anyone at work and see what's going on with that.
|
Ser Luther
|
Posted - 2007.04.20 22:23:00 -
[34]
Im in the Santa Barbara area and am on Cox HSI. Im having the same problems as everyone else but yesterday and the day before i was able to connect once for a little while before being disconnected and then getting the handshake error again. In my honest opinion this sounds like its a COX issue considering that its only happening to a fairly localized area. Bottom line is that something changed reciently and caused this problem, now its time for someone to own up and fix it.
|
bonerboner
|
Posted - 2007.04.20 23:04:00 -
[35]
Originally by: Ser Luther
Im in the Santa Barbara area and am on Cox HSI. Im having the same problems as everyone else but yesterday and the day before i was able to connect once for a little while before being disconnected and then getting the handshake error again. In my honest opinion this sounds like its a COX issue considering that its only happening to a fairly localized area. Bottom line is that something changed reciently and caused this problem, now its time for someone to own up and fix it.
The fact that it's just affecting COX subscribers does not necessarily mean the fault lies with the ISP. I'm not saying it isn't, but there's so many things that can happen on backbones that would cause something just like this it's really hard to say. The fact that the massive latency is starting many hops out and as someone said earlier... in the Netherlands I'm finding it harder and harder to believe it is in fact our ISP.
|
Misfitsa
|
Posted - 2007.04.21 02:00:00 -
[36]
I was able to log on for a few hours last night before I lost connection mid-mission and lost my Dominix. Can't connect yet again tonight. This is getting really annoying. |
Nulfis
Merch Industrial
|
Posted - 2007.04.21 02:17:00 -
[37]
I haven't been able to log in since early thursday morning, I've now lapsed on my skill training and I won't be able to try a different connection until monday. I keep checking this thread hoping for a fix, but alas, I search in vain.
|
Jorick
|
Posted - 2007.04.21 03:20:00 -
[38]
Edited by: Jorick on 21/04/2007 03:17:04
Add another person in the San Diego area with Cox that's having problems logging in. Thing is I'm also having problems connecting to several web sites, including this one and my corp site(First time it's actually loaded the reply window after trying for nearly two days now), as well which makes me think the problem is not CCP's fault.
|
Saitek Evo
Trade Consortium
|
Posted - 2007.04.21 07:13:00 -
[39]
Edited by: Saitek Evo on 21/04/2007 07:11:09
interesting problem on my part, i also live in san diego area, only my problem is unique, one of my characters has this problem, my other does not... does this have anything to do w/certain regions? my amarr character that is in 0.0, cannot log in because of this, my caldari character in empire has no problems... the plot thickens...
i have 2 friends here also that play, however, one is on roadrunner and he has no problems, and the other is on another isp that is run by a contractor working for the marine base [miramar], he also has no problems, this (to me) means definately something having to do between cox and ccp. someone give ccp cox's phone number, they should talk...
|
Amirsar
|
Posted - 2007.04.21 23:15:00 -
[40]
Is CCP ever going to do anything about this, if not I guess it will be time for me to cancel my 4 accounts. I am sick of being unable to log in or having to fight to log in for 10 mins.
|
LaMagra Shinx
|
Posted - 2007.04.22 12:57:00 -
[41]
Cox user in Kansas here. Haven't got any error message but probably because I just don't wait long enough. I try to log in and it just says "Authenticating" forever. Was able to login yesterday afternoon sometime, but now I can't again.
|
raghalina
A.W.M
|
Posted - 2007.04.22 14:35:00 -
[42]
Kansas / Cox also. I deleted my cache and it worked fine for a few logins,
|
Saitek Evo
Trade Consortium
|
Posted - 2007.04.23 03:42:00 -
[43]
yeah, i was able to log in this morning long enough to change skills, changed to a 2 hour skill, and sure as $h!t, as soon as i needed to change skills, i cant log on anymore, and i still can't log in.
|
Saitek Evo
Trade Consortium
|
Posted - 2007.04.23 03:50:00 -
[44]
ok, i was just able to log in, it seems the problem is intermittant. (i hate those gripes, impossible to duplicate until you need to get on.)
|
Falcun
Gallente
North Eastern Swat
Pandemic Legion
|
Posted - 2007.04.23 05:14:00 -
[45]
Weird stuff. San Deigo area and Cox user...been having a lot of timeout issues while logging in to EVE. Usually have to try several times before it lets me in. Anybody else who're having these problems, could they try to access newgrounds.com and see what happens? I've been getting timeouts on that site as well, and it started at around the same time as my EVE problems...
|
Lassivarien
The Older Gamers
R0ADKILL
|
Posted - 2007.04.23 17:49:00 -
[46]
Edited by: Lassivarien on 23/04/2007 17:52:42
I'm still having the issue connecting but have found that if I rename/delete my capture directory that I can get on with one client from that directory. That is to say I used to run 2 clients from the same directory but now when doing it I can only connect from one client and the 2nd won't connect. So after splitting it so that each client uses a different directory I can connect only after creating a new capture directory each time. If I try to connect a second time without deleting the capture directory it starts failing again.
edit: submitted bug report with the info so hopefully this helps, due to the fact that deleting the capture folder makes it so I can connect it makes me believe it's on the ccp server side.
|
Shrin Kale
Minmatar
PAGOM
The Crimson Federation
|
Posted - 2007.04.24 00:29:00 -
[47]
Well I can't login again. I had the problem a few days back when it started happening with everyone, but then it worked over the weekend perfectly fine. But now it is acting up again. Hopefully Cox or CCP can fix this issue.
|
Cyndarx
|
Posted - 2007.04.24 05:58:00 -
[48]
This could be a total "jiggle the handle" type fix, but I had been timing out for about 20 minutes. Rebooting my router and then flushing my DNS cache (drop to the command prompt, then type ipconfig /flushdns) seemed to fix the problem.
|
Kellen Pikara
Merch Industrial
We Are Nice Guys
|
Posted - 2007.04.24 06:30:00 -
[49]
I can barely access the eve-online website right now, let alone log into the game. This problem is not going away. I played for several hours today without a problem until about an hour ago. I too am a Cox customer in California, and I too have been told it's not their equipment. EvE has been like this since Friday. So, what am I supposed to do about packets that go die in a band of routers 69.29.171.*? I don't even know who to talk to. Multiple people in my corp and among our allies are experiencing the same thing.
|
Cyndarx
|
Posted - 2007.04.24 06:37:00 -
[50]
Little more on this as I'm still having issues. Its not stale DNS info, earlier success was just a coincidence. Established connections are fine. I had two clients open, one jumping around in a hauler, the second idling in a system chatting with corp mates. I jumped to a new system with the hauler, hung and after 5 minutes disconnected. Trying to reconnect yielded the timeout error. The second client I was chatting on was fine and responsive until I tried to dock on a station, then that client hung and disconnected to. 20 minutes later, things were back up and running again.
|
Silenciel
CthulhuFhtagn
|
Posted - 2007.04.24 07:09:00 -
[51]
Same problems since monday 23th 20H GMT (but it has worked fine at 18H GMT). Logging from France (Club-internet) and tracert is correct.
Strange.
I haven't try Cyndarx tips but i have restated my router and clear cache with no success.
It's sucks, my skill is done now...
Silence in Ciel |
Nuko Pyris
|
Posted - 2007.04.24 08:52:00 -
[52]
Same here guys. Cept i live in Kansas. Cox says everything is fine. I run tracerts everytime it happens. Nothing out of the ordinary. 130ms. I tried DSL as well. Doest not make a difference. I canceled just 20 mins ago. I dont have any other issues with any other games, except for EVE. Hope they get it fixed. Ill be back.
|
Zensu Kai
|
Posted - 2007.04.24 11:11:00 -
[53]
What we need is a semi-open proxy in Europe that is situated outside the north america switches, and to allow test individuals who use cox in north america to use it.
Either a proxy, or an ssh tunnel/vpn type deal. Then, we'll have further evidence if it lies with cox or if it lies with the backbone that CCP uses in europe.
|
Kel GalInt
|
Posted - 2007.04.29 02:01:00 -
[54]
I'm having the same problem, but I'm not a cox subscriber.
I'm only having the issue while attempting to log into the singularity server.
I was initially able to login to the character screen and select a character. I would then hang trying to enter the game with whatever character I picked. Now I can't even get to the character selection screen.
I receive the "Connection Timeout - The server did not respond to the client's secure-handshake request within a reasonable amount of time" message.
My regular eve client directory which I use to connect to the production server doesn't have a problem. (Same machine)
I blew away the cache directory and still same problem.
|
WhitePhantom
Gallente
The Scope
|
Posted - 2007.04.29 02:11:00 -
[55]
How can CCP control internet providers and connection nodes outside of their control?
The only node they a can control themselfs, is the line into their servers, because they can solve the problems themselfs. People saying you feel like your beta testing, because you are having a connection problem is sort of funny.
Most likely these problems come from that maintance that took place at a Level 3 node, which again was outside of their control, what else can they do beside have multiple service providers to their servers?
If your having a problem and you can trace it to a particular location, inform your service provider, the path you take is under their control. They can take the next step on your behalf, if they don't keep asking till it happens.
|
Laramon Questor
Minmatar
Knights of the Silver Dawn
|
Posted - 2007.04.29 16:57:00 -
[56]
I can't connect either. I'm in Seattle on dialup, loading every webpage just fine. Less than 10% of the time I can get the server status, and when it says "x players online" I might get to authenticating. One time I got to start downloading bulk data before it said connection to host reset. Now I have the error about it taking too long to respond.
If tracert didn't die after it hit my ISP to any ip address, I'd send one, but I think the latency of dialup is too high for tracert. I could be wrong.
Even after failure, there can be redemption.
|
Curcundil
|
Posted - 2007.06.08 10:28:00 -
[57]
Originally by: Kel GalInt
I'm having the same problem, but I'm not a cox subscriber.
I'm only having the issue while attempting to log into the singularity server.
I was initially able to login to the character screen and select a character. I would then hang trying to enter the game with whatever character I picked. Now I can't even get to the character selection screen.
I receive the "Connection Timeout - The server did not respond to the client's secure-handshake request within a reasonable amount of time" message.
My regular eve client directory which I use to connect to the production server doesn't have a problem. (Same machine)
I blew away the cache directory and still same problem.
I have exactly the same prob but im from portugal!!!
The game was working fine, i turned off my comp then turn it on again and it did not work!
Exactly the same thing as kel galint on what it says it is!
Hope it can be fixed fast!!!
Peace!
|
Strife Phoenix
Acerbus Vindictum
|
Posted - 2007.06.08 10:56:00 -
[58]
I don't think that this is a CCP issue, if it were a lot more people would be in here ranting regardless of location.
It might not be COX that have the actual problems but there are most certainly routing issues between COX users (probably others as well) and CCP and it is most definately up to your ISP to investigate such issues with their peers, perhaps together with the ISP that CCP use?
A post without any trace logs is useless, and you will need them when you speak to your ISP as well. If possible try using another ISP just to compare results (maybe your neighbour use a different provider?).
_
Win BIG ISK with BIG Lottery
|
Desthrua
|
Posted - 2007.07.18 06:21:00 -
[59]
Connection Timeout - The server did not respond to the client's secure-handshake request within a reasonable amount of time
I have been getting this in the past hour. I can not log into eve with either characters
|
SynackFin
|
Posted - 2007.07.18 06:22:00 -
[60]
datapoint: I'm in south central US connecting via ComCast cable and get this same error.
sad panda
|
| |
|
| Pages: 1 [2] 3 :: one page |
| First page | Previous page | Next page | Last page |