{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by IdaLefty:
2/14/2019 1:59:21 AM
1
Can't Connect to Destiny 2 via LAN/Wired
I have been constantly getting errors recently when trying to connect to Destiny 2 via a wired connection. Most of the time it is Nightingale and periodically it is Oyster. All other online games, such as Apex Legends, work just fine with my wired connection, but it won't work with Destiny 2.
I have power cycled, turned off / unplugged like Destiny Help articles have indicated and even deleted and re-installed Destiny. I even setup my router for port forwarding and assigned a static IP address for my PS4. Router has latest firmware. Nothing seems to work.
However, when I switch to WiFi, it works just fine. If it was a hardware issue, I would assume other games would have an issue when wired, but other games connect to online via LAN without an issue.
[b]UPDATE: [/b]It was Disney Circle (parental control device) that was my issue. I forgot my PS4 would register as a different device when wired and didn't have it assigned to my unrestricted profile... Ug!!
English
#Help
-
4 RepliesHello, Thanks for the report. Destiny online isn't like other online games. It needs a stable connection and forms connections in unique ways that other games don't use. If you are only having an issue when wired then it's likely one of three things. First: your wired connection may have different settings then the wifi connection, such as ports or NAT type. Second: you could have a failing Ethernet Cable and you should replace the cable, I've seen new cables just out of the package with issues even. Third: your system may have a hardware problem with the Ethernet adapter or port. You should try a new cable and check your network settings and make sure it's set up as recommended in this [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]Network Troubleshooting Guide[/url].
