Source
r/EliteDangerous•
DearIntertubes

AT&T fiber and connection issues?

Help

Was wondering if anyone playing from the U.S. has had issues with AT&T fiber and being unable to play the game.

I've recently switched to to AT&T fiber and have since been unable to play at all. Getting disconnected within 5 minutes or less, with 100% reproducible results. I've gone through all the usual steps, rebooting router, port forwarding on/off, vpn on/off, running packet / speed / ping tests, all drivers up to date, etc. without success or insight into what may be causing the issue.

I can't even say for certain if it IS an issue with my new ISP, but that's the only thing that has changed recently on my end and I've never had a reproducible technical problem since the closed beta days.

I've got an active ticket going for the issue and am going back and forth with CS trying to diagnose it, but I thought I might bring it here to see if someone else had experienced something similar.

Thanks CMDRs!

Posted Apr 5, 2020, 4:02 PM UTC

05
StuartGTMODGTᴜᴋ 🚀🌌 Watch The Expanse•

Paging u/Frontier_Support

2
zzzornbringer•

have you tried enabling upnp in the game and in your router? this circumvents the port fowarding. if you don't use it, you need to select a port ingame and manually forward that port on your router.

2
DearIntertubesOPV. A. Otter•

To my knowledge AT&T uVerse considers UPNP a "security risk" and does not allow it.

I have set up port forwarding both in game and in my router. Having PF active or not hasn't made any impact on the issue, unfortunately.

Thanks for the suggestion though!

1
frontier_supportFrontier Support•

Sorry to hear you're having issues with connecting to the servers, please send our support team a ticket and they can look into this for you further. https://support.frontier.co.uk/

-CMDR Magellan

2
DearIntertubesOPV. A. Otter•

Thanks! I've already got one up and running, we've been going back and forth with possible solutions, but so far no luck. I thought I'd post something here to see if anyone else had seen this issue and had a quick solution at hand in order to hopefully avoid taking up more of the support teams time! :)

1