Guys, you have added servers for load sharing... and broken messaging between them to support local fire teams, I guess this is to do with NAT (multi profile on same IP but different ports). Most of the solutions involve some sort of timing and with my own testing its about trying to connect to the same server for profiles on local network to connect local fire team. The is not an issue with people on differing IP's this is handled well for load sharing. The issue is inter server comm's for profiles on the same IP: Test it yourself in the staging area and prove out the configuration and stop with the scatter gun approach please. Try adding a new rule to load sharing as an interim fix, different ports / profiles on same IP's connect to same server. More than 10 profiles on same IP would indicate Business and not needed. This will fix for families and ordinary users like myself. This issue causes a lot of angst in our household we have 6 boys of which 4 are active destiny users. Many thanks in general LOVE THE GAME well done # UPDATE 2 # WORK AROUND NOW FAILS WITH UPDATE 2.4.1 !!!!! I have success with connecting local fire teams 100% of the time PS4's. Seems you need to boot Console's. Start destiny on only 1 console leaving others on initial start menu screen. In Destiny from orbit go to Friends list and invite other Console profile to join. On the console with initial start screen you should receive a request to join game. Accept request and the console will start Destiny automatically, you need to login in on intended profile and the system will automatically join fire team. This seems to get both consoles onto the same server and alleviate the problem of timing issues with random restarts or timed restarts. I don't know if it works for more than 2 consoles or if the servers run out of room to connect to single server. # UPDATE 2 # WORK AROUND NOW FAILS WITH UPDATE 2.4.1 !!!!!