still not working for me. two xbox's on best available BT internet where i live. should i have portforwarding off??

I ended up switching out my Tmobile hotspot AC-1900 router with another ASUS AC66 router w/ Merlin Custom Firmware and that seemed to have solved the problem for me. Unfotuntately, the router occasionally dies and knocks everyone off the network, not sure if that's the router or 3-players playing Destiny at the same time. Gives me Marlonberry sometimes too :(

Cheers for this, I managed to team up with my brother once running through my Macbook multiple times. Got some strange issues though. 1. I could join my brothers fireteam, he couldn't join mine. 2. It always appeared to show him "In Orbit" on my console regardless of what he was doing. 3. On my fire team roster, it showed him as Level 0, and light level 0. I also got pretty long load times moving between areas while patrolling too. (That could be destiny severs I guess) Just thought I'd share, although I'm happy its at least kinda working. I hate that the fact there's a few temp fixes will likely push this issue down (or off) Bungie's priority list.

The reason that works is because computer uses UPNP - Universal Plug and Play / SSDP which is exactly what I've suggested people change on their router. For those who don't have that option then this will work pretty much the same way.

The other fix which works quite well, but is not going to be for everyone is to get multiple IPs statically assigned to your internet connection. Based on the packet traces and how it appears to be functioning, basically, Bungie is not able to really tell the difference with two or more stations that reside behind a single IP address, even though everyone one else did. I spent the $20 (since i am WAAAAAAY above that now with multiple xbox 360s and now XBox Ones and having to buy the entire set of original desitiny and DLCs for each console TWICE). I have assigned one external IP per xbox going through and have absolutely no issues whatsoever with respect to all of us joining a fireteam. It just proves that the issue lies with Bungie in being able to differentiate the IP and SOURCE Port on their end.

Hey man hopefully I can help. So The issue is that Bungie ahs changed their infrastructure for Destiny. There is a conflict with a certain type of UPNP connection which is very popular amongst commercial routers. I don't expect them to address or publicly comment on this but I've run a few test to determine the cause. Heres what worked for me. Comcast XB3 router/modem combo Disable the wifi in the UI for the modem. (type in 10.0.0.1 in your internet browser). Hardline your computer/laptop to your router and again type in 10.0.0.1 to reach the UI and set the modem/router combo to bridge mode. This essentially removes the router function from your formerly combo modem gateway/router. Pick a 3rd party router with a good UI and the option to toggle nat filtering. My choice was the Netgear AC3200 Nighthawk X6. Plug the new router directly into your gateway. Using the netgear wizard setup your connection. Boom done. Everyone on the network should have open NAT and the correct Upnp/ssdp settings. Restart your xbox by resetting you MAC.

I shouldn't have to hook up a computer to my conic to play the -blam!-ing game fix your shit -blam!-ing lazy -blam!-s

I had to move my xbox near my mac ... but it worked for me !!! it's an ugly solution and i dont know why it's working ( man , nat of nat ... usually this make things worse ) ... Thanks for the tip...but it's a freaking ugly patch ... i am still so mad at Bungie ( still no news or timeline from them ) ... if a bunch of player figured out that the problem is related to UPNP protocol , they should have experts on this .... or they should replace them ...

Seems that we have both found the problem that bungie can't seem to find. If they would just look on their own forums then they can fix it easily.