Internet went out, unable to play 14 hours later

[BelgianBagel]

I live in student housing, so our Internet is run through the apartment complex. Last night around 11:30 PM EST, my apartment complex had internet problems. Not full outage, but enough to disconnect me from discord and throw my game into a state of error codes, including NIGHTINGAE,LE, WEASEL, BABOON, and CENTIPEDE.
I could not play again last night despite validating game files on Steam and even doing a full reinstall overnight. When I try to log on today, I can't make it to the character select screen due to error codes CENTIPEDE and sometimes WEASEL. I am hooked up to Ethernet, and every other aspect of my PC seems to be fine. I can browse the internet with no issues and can load up other games (tested: Rainbow 6 Siege, Helldivers 2, Palworld). Does anyone have any ideas to help me out? I am on Windows 11 for clarity.

I am able to sometimes get past the character select screen for a few minutes at a time, before I get error code BEE or ANTEATER, followed by WEASEL and promptly booted to the lightfall splash screen. I have tried unplugging my Ethernet cable and using Wifi but I get the same results. I have cleared my Steam Cache, my Temp Destiny 2 files, and now I have no idea what to do from here

[Chillin]

your internet is the problem.

[HugoTaHell]

Check your routers NAT settings, they may have gone back to default. Being in student housing, you are most likely on the Unis network, that is guaranteed to be restricted. Since D2 uses P2P, you need to have your NAT set to open, and IPV 6 enabled.

[BelgianBagel]

Originally posted by Bing_Chilling:

your internet is the problem.

yeah i figured that one out man thanks

[BelgianBagel]

Originally posted by HugoTaHell:

Check your routers NAT settings, they may have gone back to default. Being in student housing, you are most likely on the Unis network, that is guaranteed to be restricted. Since D2 uses P2P, you need to have your NAT set to open, and IPV 6 enabled.

In game, it says my NAT type is moderate. I have no issues in other games I've tested. Any idea how to change my NAT type?

[T3rAbYt3]

Error Code: WEASEL

The WEASEL error code is an all-encompassing error message that is usually an indicator that you are experiencing a general networking issue. Please follow our Network Troubleshooting Guide to work through possible solutions to your issue.

We strongly recommend switching from WiFi to a wired connection, at least temporarily. This is an important first troubleshooting step to rule out WiFi signal strength/stability as a possible culprit.

https://help.bungie.net/hc/en-us/articles/360048717852-Error-Code-WEASEL

Error Code: BEE

BEE, FLY, and LION error codes can be caused by general disconnections between you and the various routes your traffic takes across the internet to get to Bungie. This includes packet loss or disconnections between your home network and Bungie (such as ISP saturation or general internet congestion). It can even be caused by certain WiFi setups, faulty in-home wiring, or other issues that require on-site support or expert investigation.

Disconnects of this type can also be caused by bandwidth being claimed by other devices and applications. It may be necessary to avoid file-sharing, video streaming or other bandwidth intensive tasks on any device connected to your network while playing Destiny, including console applications that run in the background or in a window as you game.

If you hit this frequently, please follow the suggestions in our Network Troubleshooting Guide to see if troubleshooting your setup, or switching from a wireless to a wired setup improves your experience.

During investigation, Bungie has seen users hitting these errors in geographic clusters in different places at different times. For example, we recently detected 25% packet loss from the UK at the same time a number of users located there saw errors. Sometimes these issues can arise with ISP outages, resolving on their own over time.

If you have performed all of the troubleshooting steps called out above and are still hitting these errors, you may not be able to resolve this issue by changing your home network configuration. Please contact your ISP for further assistance.

https://help.bungie.net/hc/en-us/articles/360048715792-Error-Code-BEE

Error Code: NIGHTINGALE

If this is the first time you've received this error, please try that activity again and resume what you were doing before the error occurred. If you encounter the issue a second time, please exit Destiny and relaunch the game.

Steam

You may want to clear the download cache in the Steam launcher to see if that may help with your issue. Another solution is to verify the integrity of game files.

https://help.bungie.net/hc/en-us/articles/360049195931-Error-Code-NIGHTINGALE

Optimizing Connections: Improving Latency and Packet Loss

https://help.bungie.net/hc/en-us/articles/360049024092-Optimizing-Connections-Improving-Latency-and-Packet-Loss

Advanced Troubleshooting: UPnP, Port Forwarding, and NAT Types

https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types

Required Ports for Steam

https://help.steampowered.com/en/faqs/view/2EA8-4D75-DA21-31EB

Fix 1:Verify the Integrity of the Game File and Clear download cache

Verify Integrity of Game Files

Clear download cache

Fix 2: Run SFC and DISM

Step 1: Click Start menu, type cmd, right-click the Command Prompt application and choose Run as Administrator. When the User Account Control window appears, click Yes to launch the elevated cmd.exe.

Step 2: Type sfc /scannow and then press Enter to run the SFC scan.
Use the System File Checker tool to repair missing or corrupted system files[support.microsoft.com]

Step 3: To run DISM, type the following commands and press Enter after each.

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

Fix 3: Update Windows, Driver

Check for Windows and Driver Updates

[T3rAbYt3]

ipconfig

Displays all current TCP/IP network configuration values and refreshes Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS) settings. Used without parameters, ipconfig displays Internet Protocol version 4 (IPv4) and IPv6 addresses, subnet mask, and default gateway for all adapters.

Step 1: Click Start menu, type cmd, right-click the Command Prompt application and choose Run as Administrator. When the User Account Control window appears, click Yes to launch the elevated cmd.exe.

Step 2: Type "ipconfig /flushdns" and then press Enter to run.

Step 2: Type "ipconfig /registerdns" and then press Enter to run.

/flushdns

Flushes and resets the contents of the DNS client resolver cache. During DNS troubleshooting, you can use this procedure to discard negative cache entries from the cache, as well as any other entries that have been added dynamically.

/registerdns

Initiates manual dynamic registration for the DNS names and IP addresses that are configured at a computer. You can use this parameter to troubleshoot a failed DNS name registration or resolve a dynamic update problem between a client and the DNS server without rebooting the client computer. The DNS settings in the advanced properties of the TCP/IP protocol determine which names are registered in DNS.

https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/ipconfig

Netsh Commands for Windows Sockets (WINSOCK)

You can use commands in the netsh winsock context to configure Windows Sockets. The Netsh commands for winsock can be run manually at the netsh prompt or in scripts and batch files.

Step 1: Click Start menu, type cmd, right-click the Command Prompt application and choose Run as Administrator. When the User Account Control window appears, click Yes to launch the elevated cmd.exe.

Step 2: Type "netsh winsock reset c:\winsocklog.txt" and then press Enter to run.

Parameter: reset

Restores the Winsock Catalog to a clean state and uninstalls all Winsock Layered Service Providers.

The reset command restores the Winsock Catalog to a clean state. After the command is run, all Winsock LSPs that were previously installed must be reinstalled. This command does not affect Winsock Name Space Provider entrie.

https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc753591(v=ws.10)

netsh int ip v4/v6 reset

The command "netsh int ip reset" will reset TCP/IP configuration and restore TCP/IP to its original state. If you use IPv4 or IPv6, use the command lines below to reset IP address: netsh int ipv4 reset netsh int ipv6 reset

Step 1: Click Start menu, type cmd, right-click the Command Prompt application and choose Run as Administrator. When the User Account Control window appears, click Yes to launch the elevated cmd.exe.

Step 2: Type "netsh int ipv4 reset" and then press Enter to run. Resets the IPv4 configuration state.

Step 3: Type "netsh int ipv6 reset" and then press Enter to run. Resets the IPv6 configuration state.

https://learn.microsoft.com/en-us/windows-server/networking/technologies/netsh/netsh-interface-portproxy

[DCR]

Originally posted by BelgianBagel:

I live in student housing, so our Internet is run through the apartment complex.

If your on wifi you need to make sure your using technologies that enable multi user compability. There's a few of them. Those are often disable for single user system, for slight power saving benefits - more like placebo tbh.
But typically, for this kind of issue, someone may have set a specific DNS that doesn't comply so well for d2. Or a advertisement blocking feature in hardware, or something like a pihole. If you can play other network games fine, your DNS is a high candidate.

Nat type moderate is quite ok, doesn't matter.

[T3rAbYt3]

Choosing a NAT Type

NAT (Network Address Translation) works based on a player’s UPnP or Port Forwarding setup and can open or restrict internet connections to devices.

Changing the NAT Type by setting up UPnP or Port Forwarding can help resolve the following issues:

• Frequent BEAVER/FLATWORM/LEOPARD error codes
  
• Frequent empty social spaces, like in the Tower
  
• Players unable to hear voice chat from other players in their Fireteam
  
• Matchmade activities failing to find a game, resulting in ‘unable to find a match in time’, or MONGOOSE error codes
  
• For information on the "Double NAT" issue, please see the Common Hardware Issues[help.bungie.net] portion of this guide

Type 1: Open

1. The device is connected to the internet without a router or combination modem+router.
   
2. All network connections are allowed between the platform and other players.
   
3. Players will be able to play and chat with any other player.

Type 2: Moderate

1. Most network connections are allowed between the platform and other players, but some connections may be blocked.
   
2. Players can play and chat with players who have a NAT Type of OPEN or MODERATE, but cannot connect to players with a STRICT NAT Type..

Type 3: Strict/Closed

1. The platform is connected to a router that is blocking connections to other players and services.
   
2. Only the bare minimum network connections are allowed between the console and other players.
   
3. Players can only play with players who have an OPEN NAT Type.
   
4. For example, players can't see each other in the Tower or connect to players in matchmade activities.

https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types#nat-types-0-1