JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Solemn Vitiator: 12/31/2014 5:58:16 PM
35

weasel error with list of fixes I've tried

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.

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • Same here. As you said: the last time (apart from the answer below) Bungie mentioned it was Nov 13th. I've had Weasel since October and still get it very often.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon