Make sure you only use uPnP on the router. Do not use port forwarding. From the router itself, assign each console a static IP from the available IP pool on the router. **I actually assign a static IP to every network device in my network. Make sure each console has a unique name. This is done on the console itself. Hardwire each console for stability. Once that is done, shut off all the consoles and unplug power from them. Wait 10 minutes. One at a time, plug in the power and start it up. Wait until it is fully booted before starting up the next one. This will establish them on your router with the new settings. If your router supports QoS, give each console medium or medium-high priority and everything else on the network low priority Reboot the consoles and give it a try. Make sure there is only a single unique player logged in on each console. The above should help the router with data collisions and trying to figure out which console to send the right data to. As a note, this issue is not isolated to Destiny. I see it sometimes when my daughter and I play completely different games. It’s more a console networking issue. Now, that being said, you may or may not have issues with 2 or more of you all playing Destiny in the same Fireteam while on the same network. That has been a known issue since D1 and sometimes it affects people and sometimes it doesn’t. This outline was more about getting knocked offline in general with multiple consoles on the same network using default specs and settings.