{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/3/2018 7:34:04 PM
2
Constant Weasel and Saxophone
Hey everyone. It has been almost 1.5 months since i bought Destiny 2 and i still cant play it without error codes. Everyday i get more than 10 error codes while playing and not only it disconnects me from Destiny 2 it also disconnects my whole pc's internet for a brief second. I've tried to change my Nat Type to Open and it didn't work. However for some reason i cannot change my External UPnP ingame to a stationary port. Everytime when i close and open Destiny 2 it changes to a diffrent set of numbers. Right now my internal port is 3097 and my external is 1577. Im so tired of getting suspended of competetive and disconnecting at the last boss while in a nightfall or a strike. I also never had this problem in any game.
I also played the game on open beta and didn't have any problems at all. Most common error code i get is weasel into buffalo. But i get others too. What is worst is when i disconnect from a Competetive match it doesn't let me rejoin and suspends me.
-
Im having the same issue and ive also forwarded all of bungies ports. i moved from ps4 where i was having no connection issues to pc where once ever 30-40 min weasel hits
-
1 RespuestaEditado por BNGHelp6: 12/3/2018 11:47:08 PMHi. Thanks for your report. You may want to review our [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13610#PortForwarding]Port Forwarding[/url] section of our Advanced Steps for information about what Ports are needed to play Destiny 2. If you are on a wireless connection, a wired connection is recommended to play Destiny. If your internet connection is being used for anything else besides playing the game, such as watching a movie or streaming, it's recommended to quit those programs. You may want to review our guide on [url=https://www.bungie.net/en/Help/Troubleshoot?oid=13603]improving latency and packet loss[/url] to see if that might help.
