JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Dreamforge: 6/15/2015 1:59:14 AM
7

Hoards of Weasels and other networking problems [Fixed]

After the release of HoW, I'm back to getting disconnected all the time during peak hours on my XBox One. Weasel seems to be the most frequent error, with the occasional Caterpillar. This Saturday morning was fairly awful, with probably 12 disconnects in Crucible, Prison and Strikes. There is no way I can attempt osiris with this high of a disconnect rate. Xbox Live remains connected the whole time. I'm fairly confident in my networking setup and there was no other traffic on my network at that time. Config: Comcast Blast 125Mbit Motorola Surfboard 6141 Modem Router: Asus rt-n66u. Current Firmware, QoS & traffic shaping disabled Wired connection to Xbone Other fixes attempted: Wiping the Xbox one and reinstalling everything from scratch 2 months ago Rebooting the cable modem and router this morning. EDIT: Xbox was detecting moderate NAT until I re-enabled uPNP on the router. Afterwards, it reported open and still disconnected me w/ weasel. I had it disconnect me, again, twice. Both with Weasel. My initial guess is that someone is having load problems handling the resurgence of people playing destiny after the expansion update.

Posting in language:

 

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

  • My weasel problem is now fixed. The fix was to manually forward the ports as mentioned in: https://www.bungie.net/en/Help/Article/11931 Step #2 for anyone else following is to configure your router to give the Xbox a static DHCP address. Aka the same IP each time. Something with my UPnP implementation (Asus RT-N66U) was aggravated by the reconnect feature and the load on bungie servers during the Trial of Osiris. Switching over to hard port forwarding fixed the problem. I was one step away from putting the XBox in a DMZ.

    Posting in language:

     

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

  • Thanks, bump my post for later please!

    Posting in language:

     

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

  • [quote]After the release of HoW, I'm back to getting disconnected all the time during peak hours on my XBox One. Weasel seems to be the most frequent error, with the occasional Caterpillar. This Saturday morning was fairly awful, with probably 12 disconnects in Crucible, Prison and Strikes. There is no way I can attempt osiris with this high of a disconnect rate. Xbox Live remains connected the whole time. I'm fairly confident in my networking setup and there was no other traffic on my network at that time. Config: Comcast Blast 125Mbit Motorola Surfboard 6141 Modem Router: Asus rt-n66u. Current Firmware, QoS & traffic shaping disabled Wired connection to Xbone Other fixes attempted: Wiping the Xbox one and reinstalling everything from scratch 2 months ago Rebooting the cable modem and router this morning. EDIT: Xbox was detecting moderate NAT until I re-enabled uPNP on the router. Afterwards, it reported open and still disconnected me w/ weasel. I had it disconnect me, again, twice. Both with Weasel. My initial guess is that someone is having load problems handling the resurgence of people playing destiny after the expansion update.[/quote] I'm having alot of trouble with the weasel error code, this error code disconnects my xbox one from my internet. What is going on? I need help. Any suggestions?

    Posting in language:

     

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

  • Noted. So far I am just getting names of the effected so that this weasel is brought to justice. I have done everything I can on my end to solve this issue but its looking like bungie cant even solve this.

    Posting in language:

     

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

  • Yep. Still happening. Been unable to stay connected for most matches. Almost always weasel.

    Posting in language:

     

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

  • The connection was fine until the Iron Banner started up again.

    Posting in language:

     

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

  • The weasels and ferrets are back today.

    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