272 réponses à ce sujet

[liong88]

thank for the command of Jenyar its work for me.

[navlasop]

Was gonna play ME2 again and timed out all the time, no login screen for EA/Cerebrus.

And then i read this:



ZGab25 wrote...



Hello, I've same problem.



I search about command of Jenyar and I found these in complement :



netsh interface tcp set global autotuninglevel=disabled

netsh interface tcp set global rss=disabled

netsh interface tcp set global congestionprovider=none

netsh interface tcp set global ecncapability=disabled



Maybe the use of all of them helps someone.



FIXED FOR ME!! Thanks you!

[patrickreay]

Jenyar wrote...

Hi all. For me it was also related to an obscure internet speed tweak that seems to disable EA's sites. Here's the solution I found (works for Vista and Win 7):

1) Click start, go to 'All Programs', then 'Accessories', look for 'Command Prompt'.

2) Right-click on Command Prompt, click on 'Run As Administrator', if you get a security prompt, just choose continue or allow.

3) in command prompt, type, "netsh int tcp set global ecncapability=disabled".

4) Exit Command prompt, and your game should be working.

This applies to any EA game that attempts to connect to an EA profile online. I'm very curious WHY it has this effect.

Hope it helps!

this worked for me.thanks!

[The Outlaw]

 TL;DR version

Unblock outbound ports
15316
15311
15306
15321

in addition to 


TCP 42100 
TCP Port Range 15200-15300
TCP Port Range 9945-9994
TCP 80

I assume they are TCP, with my particular firewall it unlocks TCP and UDP when the port is entered.


Long version;

I was having this problem and fought with it for hours. I finally decided to start sifting through firewall logs and found the problem that I was having. They do NOT list all the required ports to be opened. I was showing outbound traffic blocked for ports 15316, 15306 and 15311 blocked to an IP address registered to EA. After allowing those outbound ports I am now able to connect to the network and the DLC has been verified and is playable. There is still other traffic being blocked to an EA IP address but it does not appear that it is causing any problems that I can tell at this time. I hope this helps.

*edit* When I went back to get into the game later it would not log in, I will add ports as I find them, if I can find a definitive port range I will edit or add another post with that in the future.

Modifié par The Outlaw, 25 mars 2011 - 02:21 .

[manguebit]

I was able to log in to cerberus network, but It would time out every time I run the game. So I had to retype my EA account everytime started the game. Here's the fix:

Go to your documents \\ BioWare \\ Mass Effect 2 folder.
Delete every folder there, EXCEPT the Save folder.
Run the Launcher again and reconfigure your game.
Run the game. Log in to cerberus network. It should stick now.

EDIT: Ok it solved temporaly, I jut got time out problems again...

Modifié par manguebit, 17 avril 2011 - 05:29 .

[tomana7]

I see the same, console connect timeout error,  with both STEAM and D2D versions of ME2

I think it's a conspiracy ... hehe

Modifié par tomana7, 28 avril 2011 - 06:59 .

[SimplePlan2k8]

I'm having the problem too when I load the game.
If I log back in, no problems at all, but it's just every single time I load it. Any ideas?

[Aapheus]

SimplePlan2k8 wrote...

I'm having the problem too when I load the game.
If I log back in, no problems at all, but it's just every single time I load it. Any ideas?

That's what's happening to me, too.  At this point, I wonder if it really even matters anymore.

In any event, I just turned off auto login and will manually login at startup from now on.

[SimplePlan2k8]

I have to login to activate DLC (I've still got a few to buy) and there will be some more updates nearer the ME3 launch but yeah, seems kinda pointless now

[CharlesA]

I was getting the same error when ME2 was starting up. I could log in fine after oking the error. It annoyed me since DAO worked fine.

Anyway, following the instructions from Ayabash fixed it for me.
http://social.biowar...07983/4#2626506

[SimplePlan2k8]

That worked temporarily then it stopped again... Anyone got any ideas :/

[CesUtd]

I also need help with this. Both Dragon age: origins and Mass Effect 2 are doing this but Dragon Age 2 is fine. I ended up finishing Mass Effect 2 logged out. I tried the suggestions above and it works only for a little bit then it is back to this again. I never had problems until about a month ago. I am not sure what changed. I have the same anti-virus, operating system and hardware. I going to change my hardware in the coming weeks. Hopefully it solves the problem.

[PostNoBills]

I am having the same problems.

• Automatic Cerberus login at game start times out.
• Manual login works fine.
• When exiting and restarting the game after only a short interval, automatic login will work.

I have no idea what is causing this, but it didn't start happening until AFTER I installed Dragon Age 2.  It was also after the new ME2 DLC pack, which I installed at about the same time as Dragon Age 2.

ME2 version:  CD
DE2 version:  Steam

[PostNoBills]

THIS WORKED FOR ME:

This fixed (or at least, appears so far to fix) the problem "automatic login times out, but manual login works".

• Right click on the Mass Effect 2 shortcut on your desktop.
• Select "Properties".
• Select "Compatibility"
• Under "Privilege Level" (near the bottom) select "Run this program as an administrator".
• Click "OK".

Not sure if it will work for you, but it worked for me.

UPDATE:  It stopped working, lol.  

Modifié par PostNoBills, 15 mai 2011 - 11:50 .

[Slyverty]

running this
http://www.speedguid...TcpIp_patch.cmd
(from an older post ) worked for me

Running win7 64

Modifié par Slyverty, 19 mai 2011 - 05:14 .

[SimplePlan2k8]

What OS is everyone running, I've heard it's mainly affecting Win7 64bit?

[Bogsnot1]

Until recently, the timeout issue was native to Vista/Win7 only, with XP users being immune to it. Vista/& users could get around it by opening up a command prompt, and typing this in;
netsh int tcp set global ecncapability=disabled

This was because EA servers were not configured to use ECN, which Vista/Win7 was configured to use by default. Its a long story about Microsoft and truncated tcp/ip packets, with other operating systems like unix/linus/bsd used normal tcp/ip packets and thus didnt need ECN.

Since around the time Arrival was released, this error has returned. It might be because of renewed popularity of ME2 as well as DA2 has caused a lot of traffic to appear on EA's authentication servers, leaving some people unabe to connect, it could be that ECN has been enabled in EA's servers and you have to reverse the above command by typing in the following;
netsh int tcp set global ecncapability=enabled

One thing we do know, is manual connection seems to work, whereas auto-login tends to fail.

[Angry_Moose]

Had this problem. Solved it by re-applying the 1.02 update manually, going in and changing the auto login settings, and resetting the coalesced.ini to default. Only make changes one at a time, you can find the ones that cause problems.

[CesUtd]

SimplePlan2k8 wrote...

What OS is everyone running, I've heard it's mainly affecting Win7 64bit?

I running windows 7 Ultimate 64bit. It was fine a month ago but not anymore. Only manual works now.

[Montana]

Same problem here.
Win7 x64

[bstrothe]

64-bit may be a common factor, I have the same issue of auto-log fails but manual works, and I run XP Pro 64-bit.

[Zeevico]

I recently started getting this issue but I don't know why.

ME2 keeps trying to autologin but fails. Before it was autologging in fine though.

Win 7, 64.

Modifié par Zeevico, 20 mai 2011 - 06:22 .

[SolidSolidino]

it seems to be a problem focusing only on ME2, cause the Dragon Age server works fine.

Surely Bioware will fix this problem soon as possible.

[Bogsnot1]

Angry_Moose wrote...
Had this problem. Solved it by re-applying the 1.02 update manually, going in and changing the auto login settings, and resetting the coalesced.ini to default. Only make changes one at a time, you can find the ones that cause problems.

Has anyone else actually tried this to confirm if it works for others, or are you just going to sit and whinge about not benig able to auto-login?

Also, Bioware wont fix it, because you are all complaining on the unofficial support forums. If you expect anything to be done, lodge a ticket with EA support. Once they get an appropriate amount of negative responses in regards to this problem, they might start putting resources towards a fix.

[Jarlaxlecq]

blkjag wrote...

Jenyar wrote...

Hi all. For me it was also related to an obscure internet speed tweak that seems to disable EA's sites. Here's the solution I found (works for Vista and Win 7):

1) Click start, go to 'All Programs', then 'Accessories', look for 'Command Prompt'.

2) Right-click on Command Prompt, click on 'Run As Administrator', if you get a security prompt, just choose continue or allow.

3) in command prompt, type, "netsh int tcp set global ecncapability=disabled".

4) Exit Command prompt, and your game should be working.

This applies to any EA game that attempts to connect to an EA profile online. I'm very curious WHY it has this effect.

Hope it helps!

thank you.. i did this, and it work I am finally able to log into the network - after a month searching and scouring the forum to fix this.. This is poor technical and customer support by Bio and EA

Oh Thank god, finally a solution that works.. TYTYTYTYTYTYTY