Can't connect to EA server
#1
Posté 27 juin 2012 - 08:54
After awhile I wanted to authenticate my DLC (I have the N7 collectors edition). Still can't connect to servers. My internet works fine. I restart the game, origins, computer and even my modem and router. Still it can't connect.
Then I go in game and see that my other DLC is there (Gun, armor, Kei-9, hoodie etc.) but still not From Ashes.
Now kinda bummed since I don't want to continue that playthrough without From Ashes and I can't open my other save game to see the Extended Cut since I can't connect to the server.
I've tried restarting everything, firewall settings and am at a loss right now. And before somebody suggests it: I don't want to edit my save game to remove From Ashes.
#2
Posté 28 juin 2012 - 09:35
#3
Posté 04 juillet 2012 - 11:39
#4
Posté 04 juillet 2012 - 05:22
Go to C > Windows > System32 > drivers > ETC, and find the file named ‘hosts’. Open it with notepad and delete all the lines with ea.com in it. Save and Play!
#5
Posté 05 juillet 2012 - 07:04
Vortigernrex wrote...
A common problem with no real solution. Desperately looking for an answer myself - just bought the DLC and downloaded extended cut, but can't authenticate them. Never have been able to connect to the EA server myself. Support usually tells you to reinstall the game, but with a slow internet connection, this means days of downloading again. DRM makes me feel like Jack in a Cerberus research facility . . . I just want to blow stuff up!
Finally found a fix that worked for me.
Go to C > Windows >
System32 > drivers > ETC, and find the file named ‘hosts’. Open
it with notepad and delete all the lines with ea.com in it. Save and
Play!
It's only a common problem for people who install cracks. The game itself does not modify this file.
#6
Posté 05 juillet 2012 - 11:31
#7
Posté 05 juillet 2012 - 03:17
Vortigernrex wrote...
No ME cracks on my system
How about other EA games?
Vortigernrex wrote...
apparently this had something to do with the old EA account upgrading to
the new Origin account.
That would be very strange. Why would a game need to block itself?
#8
Posté 05 juillet 2012 - 09:00
This week has just been the worst. Even on SP, constant dropouts/loss of connection.
And before you say Caratinoid. I DON"T have any cracks or otherwise installed. Never felt the need for them. The only way the hosts file gets amended is by ppl either manually changing it usually to loopback when they have cracked software installed, or by that illegal software directly modifying the hosts file. It more or less a defunct file now in windows with very few legal programs using it.
Certainly, none of my existing EA (DA/COD/ME) modify it.
Queen_of_Chaos, out of interest what O/S do you have. Mine is Win 7 64-bit. I'm pretty certain that it's the patch they released, as nothing else has changed on my system.
#9
Posté 05 juillet 2012 - 11:00
#10
Posté 06 juillet 2012 - 05:02
Carlina wrote...
And before you say Caratinoid. I DON"T have any cracks or otherwise installed.
I don't make a habit of blaming it on cracks and I am well aware of connection problems in mass effect. I have spend half day with network monitoring software just to get mine running (my router was the problem).
Carlina wrote...
The only way the hosts file
gets amended is by ppl either manually changing it usually to loopback
when they have cracked software installed, or by that illegal software
directly modifying the hosts file. It more or less a defunct file now
in windows with very few legal programs using it. Certainly, none of my existing EA (DA/COD/ME) modify it.
This.
#11
Posté 09 juillet 2012 - 11:18
whatever. they don't give a crap about it or it would have been fixed.
Modifié par XTR3M3, 09 juillet 2012 - 11:23 .
#12
Posté 10 juillet 2012 - 04:11
#13
Posté 10 juillet 2012 - 08:07
#14
Posté 10 juillet 2012 - 08:56
.458 wrote...
Make sure UDP ports 5659 and 6000 are open. Also, when an executable is updated, sometimes security settings are put back to insecure. Might try running as administrator or temporarily turning off security...don't ever turn it off long, but long enough to test.
Facepalm:pinched:
I know you meant well but first of all these are wrong ports because you only need UDP 3659 and second it has nothing to do with not being able to connect or get disconnected to/from ea servers and only fixes lobby join/filling problem.
Don't bother to post your source I've seen it and it's wrong.
Modifié par Caratinoid, 10 juillet 2012 - 08:58 .
#15
Posté 10 juillet 2012 - 11:19
Caratinoid wrote...
.458 wrote...
Make sure UDP ports 5659 and 6000 are open. Also, when an executable is updated, sometimes security settings are put back to insecure. Might try running as administrator or temporarily turning off security...don't ever turn it off long, but long enough to test.
Facepalm:pinched:
I know you meant well but first of all these are wrong ports because you only need UDP 3659 and second it has nothing to do with not being able to connect or get disconnected to/from ea servers and only fixes lobby join/filling problem.
Don't bother to post your source I've seen it and it's wrong.
Well, there is origin which is different from the game, but I used netstat and have seen those ports in use, as well as posts from EA/BW. So...go ahead and block those then open 3659.
#16
Posté 11 juillet 2012 - 04:46
.458 wrote...
Caratinoid wrote...
.458 wrote...
Make sure UDP ports 5659 and 6000 are open. Also, when an executable is updated, sometimes security settings are put back to insecure. Might try running as administrator or temporarily turning off security...don't ever turn it off long, but long enough to test.
Facepalm:pinched:
I know you meant well but first of all these are wrong ports because you only need UDP 3659 and second it has nothing to do with not being able to connect or get disconnected to/from ea servers and only fixes lobby join/filling problem.
Don't bother to post your source I've seen it and it's wrong.
Well, there is origin which is different from the game, but I used netstat and have seen those ports in use, as well as posts from EA/BW. So...go ahead and block those then open 3659.
Post from bioware is actually correct but some people keep posting wrong numbers for some reason.
If you see certain port in netstat it doesn't mean that origin is using it.
You don't need to block anything you need to forward this port to your pc.
Believe what you want but I NEVER get disconnects and can ALWAYS invite friends in my lobby something not everyone can say unfortunately. You maybe one of the lucky ones who didn't have to do anything to make it playable but a lot of people still have problems.
#17
Posté 11 juillet 2012 - 09:14
Caratinoid wrote...
.458 wrote...
Caratinoid wrote...
.458 wrote...
Make sure UDP ports 5659 and 6000 are open. Also, when an executable is updated, sometimes security settings are put back to insecure. Might try running as administrator or temporarily turning off security...don't ever turn it off long, but long enough to test.
Facepalm:pinched:
I know you meant well but first of all these are wrong ports because you only need UDP 3659 and second it has nothing to do with not being able to connect or get disconnected to/from ea servers and only fixes lobby join/filling problem.
Don't bother to post your source I've seen it and it's wrong.
Well, there is origin which is different from the game, but I used netstat and have seen those ports in use, as well as posts from EA/BW. So...go ahead and block those then open 3659.
Post from bioware is actually correct but some people keep posting wrong numbers for some reason.
If you see certain port in netstat it doesn't mean that origin is using it.
You don't need to block anything you need to forward this port to your pc.
Believe what you want but I NEVER get disconnects and can ALWAYS invite friends in my lobby something not everyone can say unfortunately. You maybe one of the lucky ones who didn't have to do anything to make it playable but a lot of people still have problems.
netstat has options to show the executable associated with the activity. It is very useful to see what specific applications are doing. Just have to use the option. Personally, I'm not connected through a proxy or router, I go direct to the internet, so my ports are "virgin".
Modifié par .458, 11 juillet 2012 - 09:14 .
#18
Posté 12 juillet 2012 - 03:24
.458 wrote...
Caratinoid wrote...
.458 wrote...
Caratinoid wrote...
.458 wrote...
Make sure UDP ports 5659 and 6000 are open. Also, when an executable is updated, sometimes security settings are put back to insecure. Might try running as administrator or temporarily turning off security...don't ever turn it off long, but long enough to test.
Facepalm:pinched:
I know you meant well but first of all these are wrong ports because you only need UDP 3659 and second it has nothing to do with not being able to connect or get disconnected to/from ea servers and only fixes lobby join/filling problem.
Don't bother to post your source I've seen it and it's wrong.
Well, there is origin which is different from the game, but I used netstat and have seen those ports in use, as well as posts from EA/BW. So...go ahead and block those then open 3659.
Post from bioware is actually correct but some people keep posting wrong numbers for some reason.
If you see certain port in netstat it doesn't mean that origin is using it.
You don't need to block anything you need to forward this port to your pc.
Believe what you want but I NEVER get disconnects and can ALWAYS invite friends in my lobby something not everyone can say unfortunately. You maybe one of the lucky ones who didn't have to do anything to make it playable but a lot of people still have problems.
netstat has options to show the executable associated with the activity. It is very useful to see what specific applications are doing. Just have to use the option. Personally, I'm not connected through a proxy or router, I go direct to the internet, so my ports are "virgin".
So do you see 5659 and 6000 used by origin or mass effect? Because origin and mass effect don't use them or send any data from/to on my system (checked it by capturing all data on my network). I am behind a router and have UPNP off and the only port I forwarded was the one I mentioned above.
Also here is the official post from Chris:
http://social.biowar...71235/1#9271235
and he does mention port 3659 NOT 5659. Or don't you guys see the difference between those numbers? So who do you think is right? Him or some random people on the internet? All other unofficial posts should be reported for spreading false information and deleted as fast as possible. He also mentions 6000 so it has nothing to do with origin (because he is speaking about mass effect not origin) but in my experiance it's not used anymore.
Modifié par Caratinoid, 12 juillet 2012 - 05:51 .
#19
Posté 12 juillet 2012 - 07:32
So do you see 5659 and 6000 used by origin or mass effect? Because origin and mass effect don't use them or send any data from/to on my system (checked it by capturing all data on my network). I am behind a router and have UPNP off and the only port I forwarded was the one I mentioned above.
Caratinoid,
This is a quote from a service ticket email I got back from EA tech support about problems connecting to ME3 via Origin.
Also, ensure the proper ports are opened. The UDP Ports that need to be enabled inbound & outbound to play multi-player:
UDP Ports: 5659, 6000
Using a restricted connection (such as NAT 3) can cause problems hosting a game. You will be able to create a lobby, but no one will be able to join it via quick match since Match Making will identify you as a “bad host”. However, if you invite your friend directly, you will be able to join without any problem. You should be able to join other games without any problem.
so who is right here and maybe Bioware/EA need to clarify exactly what ppl should be doing because we are getting different information.
Modifié par Carlina, 12 juillet 2012 - 07:36 .
#20
Posté 12 juillet 2012 - 07:54
Carlina wrote...
So do you see 5659 and 6000 used by origin or mass effect? Because origin and mass effect don't use them or send any data from/to on my system (checked it by capturing all data on my network). I am behind a router and have UPNP off and the only port I forwarded was the one I mentioned above.
Caratinoid,
This is a quote from a service ticket email I got back from EA tech support about problems connecting to ME3 via Origin.Also, ensure the proper ports are opened. The UDP Ports that need to be enabled inbound & outbound to play multi-player:
UDP Ports: 5659, 6000
Using a restricted connection (such as NAT 3) can cause problems hosting a game. You will be able to create a lobby, but no one will be able to join it via quick match since Match Making will identify you as a “bad host”. However, if you invite your friend directly, you will be able to join without any problem. You should be able to join other games without any problem.
so who is right here and maybe Bioware/EA need to clarify exactly what ppl should be doing because we are getting different information.
Thank you, very interesting info you have here. So now I see where the wrong numbers are coming from. Unless they distributed different builds or something I say someone at ea made I typing error.
#21
Posté 12 juillet 2012 - 08:01
EDIT:
Does anyone see 5659 and 6000 used by origin or mass effect on their system? .458?
Modifié par Caratinoid, 12 juillet 2012 - 08:15 .
#22
Posté 12 juillet 2012 - 08:05
EDIT:
Something has to be done about it<_<.
I think I am gonna make un angry thread this weekend and spread the truth.
Modifié par Caratinoid, 12 juillet 2012 - 08:19 .
#23
Posté 12 juillet 2012 - 08:19
Having said that. I just upgraded computer with clean Windows 7 64-bit install, ME3 and went into the game without doing all the patching. It still didn't connect properly. Origin version is 8.6.0.357.
Just out of interest Caratinoid, Assume you are on Windows, just go to C:\\Users\\xxx\\AppData\\Roaming\\Origin. In a dir called Cloud Saves do you have any files. Because I suddenly have one called "Blacklist". It wasn't there before Origin connected.
#24
Posté 12 juillet 2012 - 08:27
Carlina wrote...
I too have UK CE version of the game and it worked perfectly until the EC and 1.3 patch.
Having said that. I just upgraded computer with clean Windows 7 64-bit install, ME3 and went into the game without doing all the patching. It still didn't connect properly. Origin version is 8.6.0.357.
Just out of interest Caratinoid, Assume you are on Windows, just go to C:UsersxxxAppDataRoamingOrigin. In a dir called Cloud Saves do you have any files. Because I suddenly have one called "Blacklist". It wasn't there before Origin connected.
Yeach it's there. Windows 7 64-bit here too. Actually after installing EC the first time and starting the game i got "can't connect to server stuff" messages (yes plural) but after restarting it was ok again. Didn't have problems since then.
Modifié par Caratinoid, 12 juillet 2012 - 08:35 .
#25
Posté 12 juillet 2012 - 08:37
Should imagine these server addresses change but mine are currently:
Origin.exe ec2-107-22-237-84.compute-1.amazonaws.com
ec2-50-16-232-162.compute-1.amazonaws.com
MassEffect3.exe 383933-gosprapp396.ea.com
Interestingly, when I delete the "Blacklist" file the game goes straight into MP, connects no problem to a game and is fine. However, it soon reappears. EA seemed to have gone very quiet on the subject.
The only thing I have done is edit a few ME2 and ME3 save files for appearance tweaks and alter the plot table so as not to replay entire game just for minor change.
All my software is kosha. I was in a match maybe 3 weeks ago now and I suspected that they may have been cheating but came straight out.
EDIT: Also just now a further dir appeared in \\...\\Appdata\\Roaming called PACE Anti-Piracy. Imagine they are licensing files but I have heard they can cause issues.
Modifié par Carlina, 12 juillet 2012 - 08:39 .





Retour en haut






