Bump...
Still no fix, and I still get the following message when trying to get to EA support on this issue. Steam just tells me to go to the game developer support.
"This webpage is not available
The webpage at http://customersuppo...p_next_page=ask might be temporarily down or it may have moved permanently to a new web address.
Error 101 (net::ERR_CONNECTION_RESET): Unknown error."
Unable to Connect to Cerberus Network
Débuté par
Davr0
, mars 23 2010 09:56
Retour en haut
#52
Posté 08 février 2011 - 02:56
Bogsnot1
-
- Members
- 7 997 messages
Open up a command prompt,and type this in:
netsh int tcp set global ecncapability=disabled
Win7 has ECN enabled by default, whereas EA servers use a version of AQN that does yet support ECN functionality.
netsh int tcp set global ecncapability=disabled
Win7 has ECN enabled by default, whereas EA servers use a version of AQN that does yet support ECN functionality.
#53
Posté 08 février 2011 - 12:16
Callak
-
- Members
- 8 messages
Thanks Bogsnot! I'm using Vista 64, but that did it!
#54
Posté 08 février 2011 - 12:29
Bogsnot1
-
- Members
- 7 997 messages
Glad I could help. The help came from another thread with Win7 problems, I just had to do some digging to find out which one. Now shush and go kill something. You need to let out some frustrations 
#55
Posté 23 mars 2011 - 09:11
redSTALKER56
-
- Members
- 1 messages
MY CODE IS ALL WAYS WRONG.........
and i bought the game new
and i bought the game new
#56
Posté 24 mars 2011 - 12:18
Bogsnot1
-
- Members
- 7 997 messages
What code is always wrong? Game registration? Cerberus Network?
Have you looked at it carefully to make sure you arent entering a 0 instead of O, or vice versa? B and 8, or Q and O often get confused as well.
Have you looked at it carefully to make sure you arent entering a 0 instead of O, or vice versa? B and 8, or Q and O often get confused as well.
#57
Posté 15 novembre 2011 - 06:20
Kagehi
-
- Members
- 1 messages
Umm.. A much *bigger* question is why the bloody heck does the game, Steam version or otherwise, have a problem connecting to another server, if anything is defined as 127.0.0.1? By default that "should be" localhost. In a certain percentage of cases, this is what people are going to use, to connect, by name, to their own DBs, and other resources. What is it doing, starting up a local server, then getting fowled because it tries to talk to it, and instead gets routed to the localhost, which doesn't have any server on it?
I don't understand why this would happen. It is completely absurd behavior, and I am fairly sure that I probably edited the host file "back" because something else broke, because it didn't contain the localhost entry.... Hope they provide a patch to Steam for this absurdity at some point.
I don't understand why this would happen. It is completely absurd behavior, and I am fairly sure that I probably edited the host file "back" because something else broke, because it didn't contain the localhost entry.... Hope they provide a patch to Steam for this absurdity at some point.
#58
Posté 15 novembre 2011 - 08:35
Bogsnot1
-
- Members
- 7 997 messages
Why?
Could it be because Microsoft decided that Win7/Vista needed to have ECN enabled by default, when most networks dont require it. XP doesnt have ECN enabled by default, and thus doesnt suffer in this instance. See my comment at the top of the page on how to disable it.
It could also be due to people running third party TCP/IP "optimisers" which play havoc with network settings, and can also cause connectivity problems.
There is also the possibility that people have the bad luck of trying to connect right after a new game or huge DLC has been released, and thus the servers just suffer from timeouts due to excessive traffic.
As for anything being defined as 127.0.0.1, that has nothing to do with ME2, Bioware or EA. ME2 does not add anything to your hosts.ini file, so its either Steam, or something in your system causing that.
Could it be because Microsoft decided that Win7/Vista needed to have ECN enabled by default, when most networks dont require it. XP doesnt have ECN enabled by default, and thus doesnt suffer in this instance. See my comment at the top of the page on how to disable it.
It could also be due to people running third party TCP/IP "optimisers" which play havoc with network settings, and can also cause connectivity problems.
There is also the possibility that people have the bad luck of trying to connect right after a new game or huge DLC has been released, and thus the servers just suffer from timeouts due to excessive traffic.
As for anything being defined as 127.0.0.1, that has nothing to do with ME2, Bioware or EA. ME2 does not add anything to your hosts.ini file, so its either Steam, or something in your system causing that.
