If you've an issue that matches with the description below, and you've a Thomson (eg: TG784) router, here's how you might be able to hack together a fix (PC): [b]1. Enable Telnet[/b] Control Panel > Programs > Turn Windows features on or off > Tick "Telnet Client". [b]2. Open the Telnet CLI[/b] Open Command Prompt > Enter the command "telnet 192.168.1.1" > Enter username and password. [i]The username and password depend on your router. While the username might likely be "Administrator" by default, the default password can be found by physically inspecting the router (likely under something like MODEM ACCESS CODE).[/i] [b]3. Disable ALG for Destiny 2 by entering the following commands into the Telnet CLI[/b] "connection unbind application=CONE(UDP) port=3074" "connection unbind application=CONE(UDP) port=3478-3479" "saveall" [b]4. Done[/b] [i][u]/*------------------------------------------------------------------------------------------------*/[/u] [b]Issue for future reference:[/b] I've had Destiny 2 for over a week and I haven't had any technical issues at all until two days ago. Suddenly, areas (such as Lost Sectors, Mission instances, or the open world itself) have about 50/50 chance of not loading properly. When they don't, I end up running around in an empty map all alone for some 30 seconds until the game kicks me out with the "cabbage" error.[/i]