Use a network cable and not wired. Don't manually port forward (prone to errors or causing issues with other devices). Instead enable UPnP in the router and check the network settings of the console(s) to make sure it also doesn't need to be enabled there. Manually forwarding should only ever be used for single consoles when UPnP proves unreliable, and you need to forward all potential ports the console MIGHT use....why it can create issues. UPnP should only open ports actually needed, when needed. After any network changes, be sure to run the connection tests to refresh the interface and latch any new services. Make sure there is AT LEAST about 768k upstream available for EACH console playing Destiny in 12-player instances, at least about 384k upstream for 6-player (ie: 1mbit upstream may not be good enough for two consoles at once in 12 player instances) If you are getting kicked by errors indicating packet loss or other loss of session types of issues, there may well be something your ISP's Tier3 team needs to investigate. Not the normal helpdesk guys...but Tier3 (sometimes referred to as Engineering). Afterthought: a couple things you can try that may help with some potential wonkiness: Manually configure the IP of your console(s)--make sure to reserve the address(es) in DHCP though to avoid conflicts. When doing so, set actual DNS server addresses... Don't point it to the router. Disable IPv6. Set your router to respond to pings. Lower the MTU in your console's network settings to skirt around potential anti-ddos measures. Nothing drastic... Shouldn't need anything lower than 1392 or 1400 (default should be 1492 or 1500). If your ISP finds signs of fragmentation in route, this could be a workaround for that. Some VPN's may run between 1460 and 1480, so if using one this may be needed for those setups as well.