12 réponses à ce sujet

[Garres]

Several people have encountered the problem that DA:O isn't detecting our internet connections; we get the "You are currently not connected" message and can't login. EA has been no help despite numerous requests, so I've been troubleshooting on my own.
In my case, I think something is blocking my ports. I've done everything I could to open them:
--created firewall exceptions for all the .exe files in my DA:O folder
--turned off my firewall entirely (including Windows Firewall)
--forwarded ports 80, 8000, and 8001 on my router
--skipped the router and plugged straight into my modem
--called my ISP to find out whether they're blocking the ports (they say they aren't)
So, it seems like the culprit might be my cable modem, since it's the only thing left between my computer and the 'net. I'm using a Scientific American WebSTAR DPX2100. The modem has no router functionality, so I don't think it's a DHCP or NAT issue... but I'm not a networking guy and could be wrong. Documentation is pretty sparse.
What really baffles is that DA:O (evidently) has a port problem but Character Creator *doesn't*. I can log on just fine from within Character Creator. Does Character Creator run on different ports, or use them differently somehow?

[8limbscientist]

I cant connect either. maybe bioware and ea should fix the servers! or just as good, patch the game for an improved connection process, this is retarded.

[_Mist]

If you are on Vista or Windows 7 (I'm on Windows 7 x64) someone found the solution on another board.



Run a command prompt as administrator (you may have to browse to CMD.exe in your \\Windows\\System32 directory and right click the file to run as Admin.)



Run this command to turn off ECN capability, whatever that is! I tried Dragon Age after running the command, no reboot required and it connected right up to the internet.



netsh int tcp set global ecncapability=disabled

[fluxcage]

I'm on Vista x64. Had the "you're not connected" problem like many others. The "netsh..." command didn't help (it has helped others). Tried many of the things that the OP tried, with no luck. Finally re-read the EA support topic on running in Vista. This worked for me:

1. Right-click the game's desktop shortcut icon and choose Properties.

2. In the Properties Panel, click the Compatibility tab.

3. In the Privilege level section place a check in the Run this Program as an Administrator checkbox.

4. Click Apply to save your changes.

5. Try the software again.

[fluxcage]

Somehow submitted before I meant to submit. Was it the tab key I accidentally hit that did it? Anyway, one thing to add...



Before the above fix (copied from EA site; I chose XP SP2 compatibility) it took 5 minutes (timed, not estimated) between clicking the shortcut and game ready to play. Now it takes a few tens of seconds. Must have been trying to unsuccessfully to connect and taking 5 minutes to time out.

[Garres]

@fluxcage: Yeah, I tried both the "netsh" command (i.e., disabling ECN) and enabling "Run this Program as an Administrator" on DAOrigins.exe properties. Alas, nothing.

[Garres]

@fluxcage: Actually, that's interesting -- I have exactly the same problem, where it takes forever to go from double-clicking DAOrigins.exe to seeing the game's start screen. Hopefully if EA fixes my networking problem they'll simultaneous fix my load time issue as well.

[djgunn]

I've tried every single fix I've read about, every single fix I can fathom, I've even called tech support, where I was told "not our problem." So, they took my money for a collector's edition, and won't deliver on it.



I really don't know how to fix the issues I'm having.

[eRobbe]

same here djgunn

[schizochick]

tried these nothing...

[Nimrodra]

i had the same problem, i used cmd.exe as an administrator, restarted the computer and it worked perfectly

i dont know if it helped but if you got a router then in the manual its written to open ports 8001,8002 and 80 so maybe you should do that as weel

[Kachemak]

Thank you _Mist for the hint on disabling the ECN capability. After 5 hours of trying everything I could find on the web or think of on my own, I stumbled on this thread and that simple command fixed the issue for me.



By the way, ECN is Equipment Congestion Notification as explained briefly at http://www.kitz.co.u...taTCPtweaks.htm . I don't know why something that appears rarely used and is meant to assist with WAN routing caused so much grief...but it did, and I think I'll just live without my machine's ECN capability =).

[boingo-dao]

So far, it looks like this is being used:

-->159.153.235.3, TCP port 18081
-->159.153.244.83, TCP port 9987

I'm sure there are more ports, but that did the trick the first time.

Gee, wouldn't it be grand if that were posted, or even marginally similar to what the manual says is necessary? 
I mean really... thanks for telling me TCP port 80 needs to be open... I never would have guessed that...<_<

Modifié par boingo-dao, 06 janvier 2010 - 03:27 .