I had to go through technical support to deal with an issue with my login and dlc issues ,which was resolved. However, I am having a problem with the cerberus network on my end. Everytime I startup mass effect 2, it times out and I have to login to cerberus everytime (whereas before it would login automatically everytime I started up). Is there a way to fix this issue?
I bought the game when the collectors editiion came out on Steam, if that helps any. Also it doesn't effect anything game related in-game other than the startup sequence to the main screen where you have to login cerberus.
Logging into Cerberus everytime I start up game
Débuté par
alchron
, mai 23 2011 05:47
#1
Posté 23 mai 2011 - 05:47
#2
Posté 23 mai 2011 - 07:15
I am also having this issue, Every time I start up the game I am having to re-enter my e-mail address and password to log into the Cerberus Network, I am assuming that as I am not the only one having the problem and that as soon as I enter my login info again it has no problem then it isn't an issue with my router, or ISP.
#3
Posté 24 mai 2011 - 01:22
There have been a number of reports about this for a month or so, I'm afraid no one seems to have pinned down a cause. (Considering it started suddenly, I'm guessing a change occurred on EA's end anyhow, not ours.)
#4
Posté 24 mai 2011 - 01:57
Same problem here. Maybe with enough reports of the problem someone will look into it.
#5
Posté 24 mai 2011 - 01:57
I don't have my console here and it's been ages since I first loaded the game, but isn't logging onto Cerberus Network optional? I remember checking a box to log on automatically, you should be able to tell it not to.
#6
Posté 24 mai 2011 - 04:34
I read one report on how someone managed to solve the problem.
1) Reset coalesced.ini back to its original if you have modified your game.
2) Re-apply the 1.02 patch
3) Connect.
4) Any future modding to the coalesced.ini should be done 1 mod at a time, in order to pinpoint the possible cause.
I cant verify if this fix works, as I dont have the login problem. Whether its because I run on XP, or because server resources on AUstralian servers arent as stretched as Nth America and Europe, I cannot say.
1) Reset coalesced.ini back to its original if you have modified your game.
2) Re-apply the 1.02 patch
3) Connect.
4) Any future modding to the coalesced.ini should be done 1 mod at a time, in order to pinpoint the possible cause.
I cant verify if this fix works, as I dont have the login problem. Whether its because I run on XP, or because server resources on AUstralian servers arent as stretched as Nth America and Europe, I cannot say.
#7
Posté 24 mai 2011 - 05:07
So how do you submit the problem to ea then? Maybe we are just gonna have to hope there are enough people with this same problem.
#8
Posté 24 mai 2011 - 05:17
Go to EA's web page, click on support.
#9
Posté 24 mai 2011 - 09:09
same problem... even reinstalled the 1.02 patch and still have it. Wouldn't be so bad if you could tab to each field and hit enter to submit instead of having to click everything... really slows the process down.
#10
Posté 24 mai 2011 - 10:57
same problem,
#11
Posté 24 mai 2011 - 05:25
Looks like they changed something about whatever kind of cookie ME2 stores for its connection. I restored the original coalesced.ini, re-applied patch 1.02, applied one mod at a time, but none of these steps resolved this issue. I've also tried to install ME2 from scratch on a new machine, applying all patches and DLC's and not modding anything, but it keeps refusing to connect. Well, on the other side, when all DLC's have been registered, I don't need Cerberus network anymore, so when it says it can't connect I just ignore it.
#12
Posté 24 mai 2011 - 05:43
Well, I did email EA about the issue, and they are looking into it, so time will tell. They said that they did some changes to my account and to try it again, which it still did the same thing as before.
#13
Posté 25 mai 2011 - 03:15
honestly i think the problem is more on EA's side then ours, this problem is just too widespread to be anything else. which sucks because you know EA isnt going to bother looking for a fix.
#14
Posté 25 mai 2011 - 03:41
They can't say that I/we didn't try.
#15
Posté 25 mai 2011 - 06:37
I'm having the same issue too. It's freaking annoying.
#16
Posté 25 mai 2011 - 10:57
So far with my questions on EA's side, they are "trying" to change stuff in my account to get it working, which sadly is not working in the least bit. I think the are stalling with me/us on this issue.
#17
Posté 25 mai 2011 - 11:23
Same problem
#18
Posté 26 mai 2011 - 12:27
Same problem here... I recently started playing ME2 again to get a completionist savegame ready for ME3, and it always kicks me out of the system, even while playing.
I played for about two hours before I went back to the main menu and saw that the game kicked me out. DLC Content was accessible however, I constantly used the Mattock Rifle, the Arc Projector and the M5 Pistol...
I played for about two hours before I went back to the main menu and saw that the game kicked me out. DLC Content was accessible however, I constantly used the Mattock Rifle, the Arc Projector and the M5 Pistol...
#19
Posté 26 mai 2011 - 12:39
So I'm not the only one experiencing this?
To explain, I only had to enter the details every once in awhile, maybe every 2 months or so, if that.
But now, it seems I'm having to do it weekly.
Sometimes even daily if it's a bad patch.
To explain, I only had to enter the details every once in awhile, maybe every 2 months or so, if that.
But now, it seems I'm having to do it weekly.
Sometimes even daily if it's a bad patch.
#20
Posté 26 mai 2011 - 03:36
For me reinstalling the 1.02 patch fixed the issue.
I had previously stopped auto login so I reinstalled the patch, logged in, then reset it to auto login, and now it works as it used to.
For others that it doesn't work, I am sorry, but reinstalling the patch does work on some.
I had previously stopped auto login so I reinstalled the patch, logged in, then reset it to auto login, and now it works as it used to.
For others that it doesn't work, I am sorry, but reinstalling the patch does work on some.
#21
Posté 26 mai 2011 - 04:40
There is an even simpler solution. For those that are running Windows 7 or Windows Vista, open a run box, type services.msc and press enter. This will open up the Services Configuration. Scroll down until you come to a line labled Windows Firewall. Right click on it, and select properties, click the stop button. Next in the selection box next to startup type, select Disabled and click Apply.
This will totally shut off the Windows Firewall, and one will no longer have trouble connecting to Cerberus Network, and will no longer have trouble connecting to the Dragon Age Servers.
I too had this trouble, until I realized it was the Windows 7 firewall that was causing me problems. The Windows 7 or Windows Vista firewall is not needed if you are behind a hardware firewall that is in a router or broadband modem. I'm starting to wonder now, if the Windows firewall hasn't been what's been messing with and causing fequent connection drops with the Realtek Lan on my motherboard.
The Windows 7 and Windows Vista firewalls are royal pieces of junk to the point, I'm going to recommend disabling them, if you are behind a hardware firewall built in to your broadband modem or router.
This will totally shut off the Windows Firewall, and one will no longer have trouble connecting to Cerberus Network, and will no longer have trouble connecting to the Dragon Age Servers.
I too had this trouble, until I realized it was the Windows 7 firewall that was causing me problems. The Windows 7 or Windows Vista firewall is not needed if you are behind a hardware firewall that is in a router or broadband modem. I'm starting to wonder now, if the Windows firewall hasn't been what's been messing with and causing fequent connection drops with the Realtek Lan on my motherboard.
The Windows 7 and Windows Vista firewalls are royal pieces of junk to the point, I'm going to recommend disabling them, if you are behind a hardware firewall built in to your broadband modem or router.
#22
Posté 26 mai 2011 - 05:02
That would explain why it doesnt seem to affect XP users who rely on 3rd party apps for their firewall.
Could another Win7/Vista user give this a try to confirm or deny before we start telling others that this is the way around it?
Could another Win7/Vista user give this a try to confirm or deny before we start telling others that this is the way around it?
#23
Posté 26 mai 2011 - 07:48
Disabling the Win7 Firewall didn't help me I'm afraid.
#24
Posté 26 mai 2011 - 05:32
likewise... disabling the firewall didn't help, same thing with the 1.02 patch.
#25
Posté 26 mai 2011 - 06:28
never had that problem until I installed arrival. never had my game crush either before that dlc. it may be coincidence. or it may be related. but when I uninstalled it a while ago, problems stopped and now that its installed again - problems have reappeared.





Retour en haut






