Ever since this morning my roommate and I have been unable to login at the same time. Worked perfectly fine the last two weeks, but all of a sudden with no network or local changes or settings made only one of us can sign in at a time.
The errors being kicked back are an assortment; anteater, Bee, Jackal etc. etc. Our computers have an active, functioning network share with proper UPNP setup. Our router had proper UPNP setup and routing rules for proper play.
Throughout the day we have done multiple factory resets, firewall disabling on both computers and router. DMZ and port forwarding can only apply to one of our machines, and doing so still incurred the same login issue. We've disabled and re-enabled our network share, reset our upnp services, played with static and dynamic ip settings, etc. No changes anywhere. NAT shows open in game.
Whatever crazy change you guys are trying is fundamentally broken and I really hope you don't screw us who want to play with our partners just because you can't figure out basic networking that games haven't had issues with since like... 2010.
Poll: Is anyone else having issues with same-household networking and login starting 3/6/2021?
-
Edited by T3rAbYt3: 3/8/2021 2:30:36 PM[b]Error Code: ANTEATER[/b] Bungie is actively tracking this general networking error. Your disconnect was reported the moment it occurred. If you continue to receive this error, please consider following the suggestions in our Network Troubleshooting Guide. [b]Network Troubleshooting Guide[/b] https://help.bungie.net/hc/en-us/articles/360049496531 [b]Advanced Troubleshooting: UPnP, Port Forwarding, and NAT Types[/b] https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types ################################ [b]Error Code: BEE[/b] 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. [b]Network Troubleshooting Guide[/b] https://help.bungie.net/hc/en-us/articles/360049496531 https://help.bungie.net/hc/en-us/articles/360048715792-Error-Code-BEE ################################ [b]Error Code: JACKAL[/b] Bungie is actively tracking this general networking error. Your disconnect was reported the moment it occurred. If you continue to receive this error, please consider following the suggestions in our Network Troubleshooting Guide. ################################ [quote]Can you list out all the error messages you receive?[/quote] ANTEATER error codes can potentially signify lost packets in your connection, which can impact Destiny 2. [b]The most common causes for this type of issue are:[/b] * Saturated network bandwidth - Whether due to an old/damaged/low performance router/modem or extremely high network usage, if there's more data being pushed over your network than the connection can handle your messages will wind up in a queue and be delayed in being sent/received. * Outbound connection issues like modem signal problems - Sometimes these issues will only manifest when your network is at maximum usage. Other times they are always there. Typically you would need a technician from your ISP to help diagnose and fix these problems (though some diagnosis can be done if you're an expert user) * Upstream ISP issues - Sometimes your ISP will have hardware upstream from you that is nearing maximum capacity; this is especially hard to diagnose (and ISPs don't always like to admit it!). This can be especially common during "peak hours" when more people in your neighborhood are using the internet. Hopefully this information is helpful. I strongly recommend taking a look at the advanced sections of our Network Troubleshooting Guide. Blocking traffic that the Destiny game client relies on is, fundamentally, a form of network traffic manipulation, and may produce unexpected results. It is possible that this type of behavior could be used to gain advantages in other parts of Destiny. If that were the case, and if the two behaviors were difficult or impossible to differentiate in their symptoms, then we might issue restrictions to accounts that use these methods. I do not want to give the impression that this is safe to do until we are absolutely sure that this would never be flagged as bad. [b]Here are some steps you can take to try and resolve the issue:[/b] [quote]1. A wired connection is recommended to play Destiny, and if your connection is being used for other things when playing the game, such as streaming, it's recommended to quit those programs. 2. Clearing your console cache or, if on PC, verify the integrity of your game files. 3. Power cycling your internet router 4. Review our guide on improving latency and packet loss to see if that might help 5. There are three primary types of network cable issues: connectivity issues, performance issues and continuity issues. f your network connection has stopped working and you believe it may be caused by a faulty cable that connects you to an Ethernet network then Check & Solve Ethernet Cable Problems. 6. Following our Network Troubleshooting Guide for best optimizing your connection to Destiny. If issues persist, try our Advanced Steps Networking Guide for possible router solutions, such as enabling UPnP. You may also want to enable IPV6 on your router if you have it. 7. You may want to change your DNS server on your console to Google's Nameservers (8.8.8.8. and 8.8.4.4.) 8. Contact your internet service provider to see if there are any issues with your connection. 9. Using DSLReports.com I would suggest running several speed tests to see what your actual up/down speeds are coming in at. On DSLReports.com you can also test packet loss and jitter. I would suggest running these tests multiple times as well. Feel free to report back the connection test results you got at dslreports.com for speed, packets, and jitter. 10. Make sure your antivirus software isn’t blocking the Destiny 2 from launching. Add the “Destiny2.exe” application to whitelist on your Antivirus / Windows Security.[/quote] [b]DSLReports Speed Test[/b] https://www.dslreports.com/speedtest [b]World Ping Test[/b] https://www.netmeter.co.uk/tools/world-ping-test/ ################################ [b]Tests for Bufferbloat[/b] Does the quality of your web browsing, voice call, or gaming degrade when someone’s downloading or uploading files? It may be that your router has “bufferbloat” - unnecessary latency/lag created by your router buffering too much data. If the tests below show high latency (say, above 50 msec), read our recommendations at What can I do about Bufferbloat https://www.bufferbloat.net/projects/bloat/wiki/Tests_for_Bufferbloat/ [b]Eliminate Bufferbloat in your Network…[/b] There are lots of ways to throw money at this problem. Most won’t work. Your ISP would love to sell you a faster connection, but link speed isn’t the problem - it’s your router buffering more data than necessary. Buying an expensive router (even one for “gaming”) won’t necessarily help, since most commercial, off-the-shelf router manufacturers are clueless about Bufferbloat. Twiddling the router’s QoS might make a difference, but it’s a hassle, and only helps a bit. Instead, you are going to have to take charge. Once you fix it for your own network, it’ll stay fixed for all time, and you won’t be subject to changing practices at your ISP or other vendors. https://www.bufferbloat.net/projects/bloat/wiki/What_can_I_do_about_Bufferbloat/ ################################ [b]Required Ports for Steam[/b] https://support.steampowered.com/kb_article.php?ref=8571-GLVN-8711 [b]STEAM: Verify Integrity of Game Files[/b] https://support.steampowered.com/kb_article.php?ref=2037-QEUH-3335 [b]STEAM: Clear download cache[/b] Steam: https://support.steampowered.com/kb_article.php?ref=3134-TIAL-4638 [b]Console[/b] Make sure you have no pending updates available for Destiny 2 as well as clear your console cache. You can find steps to do so based on your platform through the links below. Xbox: https://www.bungie.net/en/Help/Article/45178 PS4: https://www.bungie.net/en/Help/Article/45179 Please also refer to our network guide, optimization guide, and advanced troubleshooting for assistance on minimizing connection issues and best optimizing your connection to Destiny 2. [b]Clearing the Console Cache[/b] https://help.bungie.net/hc/en-us/articles/360049199051 [b]Optimizing Connections: Improving Latency and Packet Loss[/b] https://help.bungie.net/hc/en-us/articles/360049024092#Latency [b]Network Troubleshooting Guide[/b] https://help.bungie.net/hc/en-us/articles/360049496531 [b]Advanced Troubleshooting: UPnP, Port Forwarding, and NAT Types[/b] https://help.bungie.net/hc/en-us/articles/360049496751-Advanced-Troubleshooting-UPnP-Port-Forwarding-and-NAT-Types