8 réponses à ce sujet

[IsakStormcaller]

I bought my game on Steam its the Digital Deluxe Edition.  My laptop is more than able to handle the game and indeed it used to work perfectly.  However after a bit of a hiatus of not playing and a temporary move to the Netherlands from the UK, i thought i would start again however when i got to the main menu it gives me an error saying ' Connection to EA servers has timed out' and won't let me okay it or anything.  Windows task manager says it isn't reponding.  If it would help i can get the exact configuration of my laptop but don't see how it could help.

[Fenseven]

 I just bought the game for the 360 and can not connect to the EA servers either.  Wasn't this problem fixed months ago?

[blkjag]

having the same problem.. cannot connect to ea or cebl network

[Mouthworsh]

Yeah for me this seems to be pretty recent, damned annoying though...

[WarpNine]

I've had a version of this problem ever since I installed Mass Effect2 using Steam. Each time I start the game, it hangs for about a minute while it attempts to connect to the Cerberus network - which nearly always fails. (I've only ever seen the automatic log in work two or three times in the hundreds of times I started the game). I then have to hit "OK" and then the "connect" button to re-enter my userid and password for EA on-line - which then always works perfectly to connect me to the Cerberus Network. I posted something about this months ago, but no one else seemed to be having the same problem. This is not related to any real connectivity problem on my system, since other games like Team Fortress and Dragon Age always connect perfectly - first try - and even Mass Effect2 always connects successfully after I re-type the userid and password again each time I play. If this problem is related to the Steam "wrapper" that is running in the background while you're playing it under Steam - that is not obvious at all.

[somejah]

Your incorrect, it is a computer connectivity problem mainly, heres how to fix it:



1. Go to Start Menu and open up Computer, once there, open up your hard drive. which currently has windows installed on it. (For most people, that will be C:)

2. If Windows was installed on the hard drive you selected, you will see a folder named Windows, open that up.

3. Now look for the System32 folder, open that up. Now look for the drivers folder and open that. Then at last, the etc folder. The directory should now be something like C:Windows/System32/drivers/etc

4. Inside you will see the hosts file. Open up Notepad which is located in accesories (right click and select Run as Administator if on Vista or Win7)

5. Go to File on Notebook and select Open, now go to the same place shown at No.3. Make sure you have Notepad set to look for all files, you can change this by clicking on the arrow next to Text Documents (*.txt) in the bottom right corner and making that All.

6. Once in that Directory, now you can open up the hosts file with Notepad, once you have done this you now need to delete every line in that file which has the word EA in it and also starts with 127.

7. Save the file and then quit notepad and everything else that I have told you to open in this guide.

You should now be able to use Cerberus.

Happy gaming!



-somejah-

[WarpNine]

Thanks for the suggestion, but given that there is nothing in my hosts file except a definition for "localhost" and the logon to the EA on-line account (Cerberus Network) ALWAYS works if I re-enter the userid and password manually - this doesn't sound like the cause of this problem. If the hosts file entries were messing things up, it should fail consistently - not just for the first time automatic logon attempt.



I'll try tracing the connection with WireShark, and see if that sheads any light on why the automatic login usually fails... Today it actually worked one of the times I started the game, which has been a very rare event indeed!

[somejah]

Ah, I didn't read your post properly then it seems, I thought the issue was that it never logged in and always gave the timed out message.

[WarpNine]

I'll see if I can trace the logon attempts with WireShark later today, to see what that may show. Thanks again for your help!