61 réponses à ce sujet

[Bogsnot1]

Given as noone seems to be bothered filling out a correct problem report, its a bit hard to work out where the problem lies. Simply saying "Me too" gives no information to work with.
If running Vista, or Win7, the problem could well be due to ECN being enabled by default, when EA's servers are not configured to use ECN. This is a fault caused by Microsoft, rather than EA/Bioware.
Open up a command prompt, and type in the following command;
netsh int tcp set global ecncapability=disabled

There is also the possibility that due to the new DLC being released, the servers are under greater strain than normal as everyone and their dog wants to play again, thus leading to timeouts. If disabling ECN doesnt work, try logging on at an ungodly hour of the morning when most normal people would be in bed sleeping.

[CalJones]

It's happening for me and I'm on XP, so that's not the problem. Auto login worked fine originally - then I went away from the game for a while (to play other things) and just returned to play Arrival. Now I have to log in every time. It's annoying, but it will log in once I enter my details.

[Torrasque]

It's still happening to me, as is the DA:O issue that's similar and 'fixed'. It's getting kind of annoying here. Volunteer CMs who don't work on weekends is not an excuse to not monitor forums and deal with our issues. I have to wonder, if they keep this level of customer service up SWTOR won't last long.

[Vreltek]

For me the connection problems also started with the Arrival DLC. Before this the Auto-Login always worked perfectly for me (and I was just doing another play-through in anticipation of ME3). After installing Arrival the Auto-Login doesn't work anymore. :-(

Please Bioware fix this, because it's extremely annoying!

[nomansa]

I have the same problem (Win 7 x64 SP1, 6GB). Auto-login worked correctly until two week ago when I started getting the failure message everytime the game is started (regardless of time of the day). Manual login immediately afterwards always works.

[termokanden]

Yeah it's a recent problem. Extremely annoying.

There is also the possibility that due to the new DLC being released, the servers are under greater strain than normal as everyone and their dog wants to play again, thus leading to timeouts.

If it's a timeout, there's no reason it should happen immediately. But it could still be a server thing yes. Perhaps it's immediately dropping connections.

[Kloreep]

Auto-login worked for me just now. Does everyone with this problem have Arrival? (I don't.)

[Dan011]

I have the same problem (Win 7 x64 SP1, 8GB). Auto-login worked correctly until very recently (cannot be specific about date, sorry) when I started getting the failure message everytime the game is started.

Manual login immediately afterwards always works. Have recently installed arrival but cannot say for sure that it did not occur before as well.

[Dan011]

Out of interest, (and this is my first time on this tech support board so apologies if this is naive), but wouldn't you expect an official response by now - this thread is 19 days old and that seems a bit too long to go without official help.

I don't know if this amount of people reporting the problem is considered "small" and therefore low priority, but it seems to my uneducated eyes that this looks to be a server problem or a recent update problem, rather than the client PC. I have not changed anything on my PC for a while and do not auto update from Microsoft the moment an update is released, although I do admit I cannot be 100% sure that I haven't had an update since the problem started as I don't have an exact date for that

[Kub666]

Dan011 wrote...
Out of interest, (and this is my first time on this tech support board so apologies if this is naive), but wouldn't you expect an official response by now - this thread is 19 days old and that seems a bit too long to go without official help.

No, you shouldn't expect quick response. They have sold the game to you already, and there are no more DLCs planned, so why should they care?

Here's what I found on Steam forums though:

"I had this problem with connecting to Dragon Age servers (not
recognizing my login properly) so I contacted EA support a few days ago.
They said they are experiencing problems with their login servers and
their engineers are working on a fix. I assume it applies to ME servers as well."

So they are aware, they just suck at communicating it to us.

[DumbHawk]

Unlike most of you with this problem when the connection time out screen pops up i can't get out of it.
I've tried using task manager to exit/end the game and then playing it again, I've only gotten past this once and that was the 2nd time i started the game up.

I have a Win7 64bit and I allowed ME2 access. :[ I really wanna play this game, I had just reached the giant armored mech before the game crashed and this happened

[Torrasque]

DumbHawk, I was having that problem too, but now at least I can get out of that screen and on to the manual log-in. The area you need to click is rather small, just psychotically click around for a bit and see if that works.

On another note, this really pissing me off and my hopes for SWTOR not failing in a month are getting weaker.