{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by xms:
6/11/2026 12:08:59 PM
7
Proof "weasel" is NOT a user error
I've been receiving "weasel" on steam for a year now. Switching over to Epic Games fixed this issue until this last update. After purchasing the DLC's on Epic due to them being ridiculously cheap, I have been receiving "weasel", despite being able to play the game normally for months after receiving weasel on a different platform (same connection, same pc, same everything.)
WHAT HAS BEEN TRIED:
- Mobile Hotspot
- Windows Reinstall
- Game Reinstall
- Firewall turned off
- Antivirus turned off
- DMZ on & off (both tested)
- UpNp off & on (both tested)
- Ports 3074 & 3097 forwarded
I used wireshark to watch my connection to Bungie servers, (172.97.56.126 port 7501 and 205.209.19.168 port 30001) my connection stays stable for about 120 seconds with healthy TCP window sizes and only very small and fully recovered retransmissions. The disconnect is sent by BUNGIE servers sending a FIN to close the session. It is not the client (user) timing out or a packet loss drop, it is simply the server closing our connection for whatever reason.
I will drop my logs here for any bungie employee that isn't an automated response to have a look at.
1) Very healthy connection to the server, no packet loss or drops:
5024 99.005975 205.209.19.168 -> me 30001->50120 [ACK] Win=525056
5027 99.043567 me -> 172.97.56.126 [TCP Retransmission] 50105->7501 [PSH,ACK] Len=98
5033 99.188566 172.97.56.126 -> me 7501->50105 [ACK] Win=262400 SLE=27543 SRE=27641 <-- we didn't like the packet but we retransmitted successfully
5058 99.618017 205.209.19.168 -> me 30001->50120 [PSH,ACK] Len=73
5061 99.669251 me -> 205.209.19.168 50120->30001 [ACK] Win=262656
2) Then Bungie server closes the session. It sends a final burst of data and immediately after sends a FIN. No time out, nothing. The server refused the healthy connection.
6187 120.444531 172.97.56.126 -> me 7501->50105 [PSH,ACK] Len=112 Win=262144
6188 120.444770 172.97.56.126 -> me 7501->50105 [PSH,ACK] Len=114
6190 120.445167 172.97.56.126 -> me 7501->50105 [PSH,ACK] Len=440
6192 120.467343 172.97.56.126 -> me 7501->50105 [PSH,ACK] Len=44
6193 120.467343 172.97.56.126 -> me 7501->50105 [PSH,ACK] Len=44
6194 120.467343 172.97.56.126 -> me 7501->50105 [PSH,ACK] Len=44
6195 120.467343 172.97.56.126 -> me 7501->50105 [PSH,ACK] Len=44
6196 120.467359 me -> 172.97.56.126 50105->7501 [ACK] <--- me, the client ack's the data, accepting it
6197 120.467935 172.97.56.126 -> me 7501->50105 [FIN,ACK] <-- HERE IS WHERE THE SERVER CLOSES THE CONNECTION
3) Client side closes the connection after (obviously) because the server closed it first.
6236 121.278448 me -> 205.209.19.168 50120->30001 [FIN,ACK] <--- (client side closes the connection after the server does)
6253 121.517761 205.209.19.168 -> me 30001->50120 [FIN,ACK]
6278 123.248477 me -> 172.97.56.126 50105->7501 [FIN,ACK]
-
I am on day four of this issue still plaguing Destiny 2. I have been looking into this issue since the first day it hit me, and I've tried everything I could to remedy the problem. Bungie's steps, Google's steps, AI Language Models' steps. I've resorted to asking every person I could with an IT background to say, "I dunno what's going on man, it must be something with their backend." Bungie, THIS IS YOU. We have said this over and over again, screamed it at the top of our lungs with the only way we have a line to you. All you have given us is automated responses and an acknowledgement that your game has had an 'uptick' in error codes recently. Respectfully, get your stuff together, Bungie. This is unacceptable to have people suffering game bans, in-game loot losses, and even in my case where I simply CANNOT play the damn game itself - AT ALL. I get disconnected before I can even control my character. The furthest I've gotten to date since these errors is the ship flying through space on a loading screen. Hurry up.
-
2 RepliesHello there, Thank you for reaching out to us. We've received a rise in reports of general server issues since the recent update, and are currently investigating. As you mentioned this has been occurring for over a year, we'd recommend trying out our [url=https://help.bungie.net/hc/en-us/articles/360049496531-Network-Troubleshooting-Guide]Basic Network Troubleshooting[/url] and [url=https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types]Advanced Network Troubleshooting[/url] guides. We'd also recommend checking out the [url=https://help.bungie.net/hc/en-us/articles/360048717852-Error-Code-WEASEL]Error code: WEASEL help article[/url] if you haven't already.
-
this needs to be investigated the same way the lego story is :D someone call Ben about this :)
-
W wireshark xd it proves they are tying to push us away from destiny to mharton
-
try upgrading to the latest windows 11 i was having the same issue as you then i upgraded from windows 10 to the latest update of windows 11 after doing like 30 steps of troubleshooting and the problem is completely gone for me. I see you did a windows reinstall but maybe it wasnt the most up to date version idk
-
FIX WEASEL BUNGIE
-
Bungie please fix.. I can't play since the update. Defeated by weasel :(
