I've gotten the weasel code, on an Xbox one, since Tuesday of last week, then I went to digging to solve the issue client side as best as I could have:
Power cycled everything in between each of the steps
Toggled upnp
Forwarded the correct ports
Set up static ip for the Xbox
Put the xbox in the dmz
Changed the Ethernet cords from the Xbox to the wall and then from the wall to the router on the other end
Then all the Ethernet cords related to the router and modem
Took the router out of the equation and ran straight to the modem
Replaced the modem with another one the ISP tech had when he came out and used a different router when we did that
And I've even bought a new Xbox one thinking it was a faulty box
But alas to no avail
I've been on the phone with Microsoft for a few hours at a time I've been on with netgear for router support and I've had the ISP out twice, I just wanna play. Did I miss something? I enjoyed learning all this stuff but dang. I'll gladly give any more details if you guys need it.
-
Edited by Kreepz: 2/5/2015 2:48:21 AMI for one will also be bumping your thread daily, as I also have been receiving this error code off and on for about 3 months. I have tried all the same steps as the OP minus a new Xbox One. Tonight, I was attempting to do CE and disconnected a total of 16 times before my friends decided to call it for the night. Once I am out of the party, I am running bounties and world events without any disconnect problems. This error is definitely related to party interaction of some sort. I just wish Bungie actually cared enough to take their servers down for a few hours a week to maintenance them. Day 83 for me.