# Persistent WEASEL — PC Only — TCP 7500 Connection Closed by Remote Endpoint I'm experiencing a reproducible WEASEL error on PC that occurs approximately 30–60 seconds after connecting to Destiny 2. I have performed extensive troubleshooting and have been able to isolate the behavior to the PC connection to Destiny services. ### Reproduction * Destiny 2 loads normally. * I can reach Orbit/character selection. * I can enter the game and move around normally. * After approximately 30–60 seconds, I receive WEASEL. * The timing is extremely consistent. ### Platforms tested **Xbox console** * Works normally with no WEASEL. **Xbox app / Microsoft Store PC version** * WEASEL occurs. **Steam** * WEASEL also occurs. The Steam installation is associated with a **separate Bungie account**, so this does not appear to be an account-specific issue. ### Networks tested I tested the PC on: * My normal home Internet connection. * A completely separate cellular/mobile hotspot. **WEASEL occurs on both networks.** Therefore, the issue does not appear to be specific to my home router, ISP, or local Wi-Fi network. ### PC/network troubleshooting performed I have also tested: * PIA VPN completely exited. * Windows Firewall disabled for testing. * Teredo initially showed `disabled / offline / client is in a managed network`. * Local Group Policy confirmed all Teredo policies are **Not Configured**. * PC confirmed not domain joined, Azure AD joined, or enterprise joined. * Teredo was subsequently changed to `enterpriseclient`. * Teredo then reported: * Type: `enterpriseclient` * State: `qualified` * NAT: `restricted (port)` * WEASEL still occurs with Teredo fully qualified. * Xbox Live Networking Service was manually started. * Gaming Services Repair Tool was completed. * BattlEye (`BEService.exe`) is running normally. * Destiny 2 was repaired. * Windows Event Viewer does not show a corresponding system/network error at the exact time of the WEASEL. * AppXDeployment-Server logs also show no event corresponding to the WEASEL. ### Most important finding — TCP 7500 I monitored the Destiny TCP connection using PowerShell. Immediately before the WEASEL: `10:27:17.857 — State=Established — Local=10.168.168.171:59550 — Remote=172.97.56.6:7500` Then: `10:27:18.584 — State=CloseWait — Remote=172.97.56.6:7500` **WEASEL appeared at exactly 10:27:18.584.** Immediately afterward: `10:27:19.311 — NO CONNECTION ON PORT 7500` So the connection transitions from: **ESTABLISHED → CLOSE_WAIT → connection disappears** at essentially the exact moment WEASEL occurs. This appears consistent with the remote endpoint closing the TCP connection. ### Request for investigation At this point, I have reproduced the problem: * On two different PC storefronts. * With two different Bungie accounts. * On two completely different Internet connections. * With Teredo qualified. * With PIA disabled. * With Windows Firewall disabled. * With Gaming Services repaired. * With BattlEye running. The Xbox console works normally, while PC consistently loses the TCP 7500 connection and immediately produces WEASEL. Could Bungie please investigate the server-side connection logs for: **August 19, 2026 at approximately 10:27:18 AM Central Time** Remote endpoint observed: **172.97.56.6:7500** I would specifically appreciate having this escalated to the networking/engineering team to determine why the TCP 7500 session is being closed approximately 30–60 seconds after establishing the PC connection. I can provide screenshots of the TCP monitoring output and additional diagnostic information if needed.