{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/22/2016 12:05:32 PM
12
[i][/i]So this is a work around that seems to work 100% of the time. Trust me when I say I have tried EVERYTHING else!
1. Both players load the game and go to the tower.
2. Both player at the same time press the XBOX button and quit the game.
3. Both players at the same time start destiny again and this should generate a 'WEASEL' error. This should usually happen to both players.
4. Close the error and continue to selecting your characters.
5. You should now be able to join the same fireteam team.
I know it's a ball ache it this does genuinely work. You can even leave the fireteam after and you will have no issues rejoining.
This is a fix for as long as you are online but the next time you play you will have to do this again.
Just goes to show that this is truly a bungie issue as to get this to work no changes to any network settings need to happen.
Hope this helps.
English
-
Worked for us mate thanks
-
I'm a network engineer and I was sceptical this would work. But amazingly it does. Seems to indicate some sort of issue in the server side session tracking code. Perhaps the server isn't correctly logging the upnp port on first connect as the xbox still hasn't obtained it? Anyway at least i can put the wifi hotspot away.
-
I'm a network engineer and I was sceptical this would work. But amazingly it does. Seems to indicate some sort of issue in the server side session tracking code. Perhaps the server isn't correctly logging the upnp port on first connect as the xbox still hasn't obtained it? Anyway at least i can put the wifi hotspot away.
-
Never mind. It worked first go with no weasel error though. Thanks for the tip!!!!!
-
Any idea if this would work for ps4?
-
I can't believe this worked, but it did. Thank you.
-
Dude, My boyfriend and I have been trying to find a way around this for over week. THANK YOU!
-
Glad I could help
-
You sir are a legend of gigantic proportions I shall name my first child after you and statues shall be erected in your honour! I spent the best part of 5 hours yesterday trying to get over this thought I would see if there was any update from bungie saw this and it worked first time and has continued to do so Can't thank you enough BUNGIE : - Check - your move!
-
what if we don't get the weasel error? I really don't want to sit here all day power cycling my xbox and router until it works
-
In all honesty I and my partner have been using this work around for 2 weeks and it has worked everytime. Sometimes only one of us gets the error but the results have always been the same. You don't need to restart your console or change any settings on your router for this to work.
-
Same here, has worked a treat since I read about it 2-3 weeks ago.
