I had the same problem about a year ago. When i looked up the weasel error it said that it was a problem with my internet connection, not a "bungie" error. Sure enough, port forwarding solved the problem for me. Typically though, when it happened before i had port forwarded my console, i would unplug my xbox to do a hard reboot. I wouldn't have anymore problems for a few days.
Not sure if the error still stems from the same issues or not, but i wish you the best of luck in finding a fix for it.
English
-
Ok will try that, but what is very interesting about my problem is that it seems to be almost the exact same amount of time before I get weaseled, every time. Strange. Its almost like my extender can only process a certain amount of info before disconnection...
-
Yea, it is very interesting, but that might be a good thing too, might make it easier to narrow down the problem! Good luck friend, hope it all works out for you!
-
Ok thanks!!! :)
-
Sorry friend, thats all i did to fix the issue. I would reccomend if it is at all possible to try what the mentor said in that other comment. Move your system close to the wifi source and try a hardwired connection just to at least check if is the an issue with the wifi extender you are talking about having. Again, i know it may not be possible, but even if it is just for an hour or so to move a tv and your system closer just to narrow down the source of the problem, thats the only thing i can think of to help you solve your problem.
-
Tried this today. Sadly didn't work :(, any other ideas?
-
Thanks, I'll try that but not getting my hopes up. Anyway though how did you do port forwarding on your console, I did it on my router through the router access page on my computer.
-
Yea, i did the same thing. I don't even remember if i changed any setting on my xbox, but i was able to reserve the specific ports required for an xbox regardless. I followed some tutorial online, but ill be honest, i couldn't tell you what i was doing while i was doing it.
-
Ok, Thanks anyway