I know a thread has already been created for this, but I was wondering if any solutions have been made.
This message keeps coming up everytime I try to connect to the Cerberus Network:
"Communications with the Mass Effect 2 Server was interrupted or has timed out. Please try again later"
I have not been able to connect to the Cerberus Network at all since I bought the game today.
I don't think this is an equipment issue since I've connected my gamertag to my accounts and received the Terminus/Collector's DLC. I just can't seem to connect to the Cerberus Network. Can anyone kindly point out a solution to this problem? I would really like to access all that other great DLC!!
Cerberus Network Constantly Unable to Connect
Débuté par
A_Shepherd
, avril 28 2010 09:05
#1
Posté 28 avril 2010 - 09:05
#2
Posté 29 avril 2010 - 01:06
I was encountering this same issue earlier too, same error message and everything.
However, after adjusting the correct time under my 360 System Settings, it started working just fine (it was originally 5 minutes ahead).
However, after adjusting the correct time under my 360 System Settings, it started working just fine (it was originally 5 minutes ahead).
#3
Guest_Darth Midville_*
Posté 10 mai 2010 - 06:30
Guest_Darth Midville_*
I've seen this happen now and then, probably because my internet connection gets laggy.
Why doesn't the game have a "remember name and password" setting so I don't have to type it in every time?
This sort of thing is standard for internet connected programs of any sort. Grrrrrrr.
Why doesn't the game have a "remember name and password" setting so I don't have to type it in every time?
This sort of thing is standard for internet connected programs of any sort. Grrrrrrr.
Modifié par Darth Midville, 10 mai 2010 - 06:30 .
#4
Posté 11 mai 2010 - 06:17
Whole Particle wrote...
I was encountering this same issue earlier too, same error message and everything.
However, after adjusting the correct time under my 360 System Settings, it started working just fine (it was originally 5 minutes ahead).
Thanks, I just fixed this issue on my system with your method. Stupidest reason for a failure to connect to a server ever.
I'm sorry you can't connect your clock is wrong...





Retour en haut






