This is another post about 2 consoles on same network unable to join. im just adding to the numbers. have attempted multiple combinations of power cycling and cache resetting for the two consoles and the modem. i have actually tried it on two different modems due to a recent upgrade with no success. i have allocated static IPs to both consoles and set up port forwarding for both. and also tried having one console static with the other on auto dns and ip (both combinations). i have tried the whole timed joining or joining players with destiny not started or characters not selected and tried different characters and different methods of joining the problem also never declares an error, only that it should be tried again. also it seems to start joining the team abd then the "joining foreteam box" pops back up just before changing to the whole try again message. this is a joke and its been going on for too long. this issue was present in y1 and was fixed, it shouldn't be hard to find out which piece of netcode has leaked back into the final patched netcode or which section is causing conflict. the fact that its taken months to resolve this and only weeks to tweak your economy doesn't look good for your company's on going public relations. other than that.... gg bungie. *edit* There has been a few solutions thrown around below so have a read. but currently a temp fix which works so long as all consoles do a quick network check at the same time and then join destiny at the same time and fireteam up straight away is described below.... hardly a permanent result but id rather a bandaid while waiting than cascading disappointment every day. *additional edit* this fix didn't work last night despite an hour of attempts and various combinations of hard cycling and network tests. this issue is a fickle bitch