Still getting weasel. Even went as far as having my ISP (Verizon) come out. Checked everything out, replaced some of the hardware. Ran tests again - everything fine on my end. No packet loss, nothing that hinders me from online game play. Yet I still get error code weasel. Yes, I have an Open NAT with ports forwarded. What do I do next? Seems to also happen more often between 7-10pm EST time. Help, thanks.
-
Same here .. the messed u part is that bungie refuses to address the issue. A great game ruined by piss poor customer service. Eventually a game will come along that's like it with devs and car that give a crap about their clientele.
-
So mine started on The 3rd of November. I have experienced the same error code from 5 to 9 PT.
-
Please fix this ! , so much for " the next great adventure "
-
Bump for -blam!-s sake
-
This is old -blam!-ing news. I've been getting weaseled ever since the -blam!-ing game came out. Now it is not letting my xbox connect to the internet cause my ISP thinks I'm getting DDOS'd. So from playing a game to try and just watch netflix doesn't even happen. Bungie where is my refund for not being able to do anything on my xbox cause my ISP blacklisted it for a couple of hours. Get the -blam!- up and fix this shit. It's not -blam!-ing hard at all. Now I'm pissed and will be tweeting, calling and spamming for answers. I have another xbox one on the SAME network and that one does not get kicked from live, destiny...nothing. So whats going on? They never answer so who do they really care about?
-
This has been happening to me A LOT ever since RoI came out- and of course it always happens when I'm on a roll in the crucible, strikes, etc.
-
i mot using Verizon and this error code is an old problem i like the game but this piss me off a lot wease, can't play for just few minute and the game crash
-
Man this is bs 3 days in a row of this I can't stay on without getting kicked for more then 3 min's...I pay good money for fast internet and I have an open nat. Seriously this needs to be addressed. Crooks.
-
Same here all the issues ur having same with Verizon
-
Day 1: Perfect connection. Day 2: Perfect connection. Day 3: WEASEL 17 TIMES. Day 4: Quits I've had this same problem since forever ago. Been through plenty different wireless providers so year one's discord can be blamed on terrible interweb connection. After I came back to Destiny, I had no error codes(from the launch of TTK till about last month). My family stepped up her wireless game so we're pushing a professional network(because her work requires video sessions with her patients). All other games I have ever played, I've had perfect connection. I gamed on Iron Banner endlessly, got to rank five in 10 hours. After achieving it, I went to the tower and I got my gear, to be greeted by [ATTENTION. CONTACTING DESTINY SERVERS.] And it went away at first, but came back, and again and again- until after 4 weasels later I gave up. I checked my ports and my NAT's also open. Wasn't sure if the 360 was just lackluster at matchmaking, so the next day after the Iron Banner closed, I launched a strike(or whatever). Yet another weasel. And they've been consistent for the last three weeks. 6 times a week usually, but then I can't launch Destiny for another 3 hours. I think Bungie just wants to toss in the hat already.
-
Yeah, it just -blam!-ing kicked me from a trails match, and there was nothing I could do about it, we were winning 4-0 and I got kicked, and it counted as a loss, so my flawless went down the -blam!-ing drain. They need to -blam!-ing fix this shit, even if it's just in Trials, because this is -blam!-ing bullshit
-
Hey there, Please go over the following networking Help article to troubleshoot any connection issues you may be experiencing: https://www.bungie.net/en/Help/Article/11930
-
Just happened to me for the 100th time this week. Ever since iron banner I have had terrible connection. Also as a side note I have a fiber line backbone Internet connection at almost 100 mb dl speed. This needs addressing...
-
[quote]Still getting weasel. Even went as far as having my ISP (Verizon) come out. Checked everything out, replaced some of the hardware. Ran tests again - everything fine on my end. No packet loss, nothing that hinders me from online game play. Yet I still get error code weasel. Yes, I have an Open NAT with ports forwarded. What do I do next? Seems to also happen more often between 7-10pm EST time. Help, thanks.[/quote] I have only gotten weasel errors from after the Taken King has launched, being who I am a have tried countless things to fix this, this is just getting to the point where the game is un-playable and frustrating to deal with, at that there is no error on my part, great multiplayer connection, great online connection, this is all the the behalf of bungie and they seem to be ignoring this error... I expected much more
-
-
I'm getting weasel multiple times a day now. Before the latest patch it was never an issue. I'm playing on xbox live on xbox one.
-
More BABOON AND WEASEL TONIGHT...Last night It booted me out of fricken SKOLAS... ARE YOU KIDDING ME... I got hosed for my TRIUMPH, by a Damn error. I want compensated... It took fricken 5 hours of my time beating it... And Error at the Fricken chests. Assholes... I still show Skolas missing on my Triumphs now... Pissed off player... Thanks Bungie.
-
Edited by OldeSkoolKool: 9/26/2015 11:25:39 PMSame here. I've been through this a hundred times over the past 12 months. Only game I ever have issues with is Destiny. Game is unplayable tonight. I've been weaseled out of tower twice and now 3 heroic strikes in a row. Can't stay on for more than 5 minutes before getting booted to title screen.
-
I've been getting a lot of disconnects lately. I don't know what's going on. I went as far as putting the PS4 on DMZ and I'm still getting weasels.
-
Been happening constantly to me all week, last night was the worst one yet for error codes. And I'm on a WIRED connection, NAT type open cause I know how to port forward for console crap. Doesn't matter, it's not my internet, with this many people complaining it's their awful servers, it's always been bad.
-
GUYS IVE BEEN GETTING WEASEL EVERY 15 MINUTES OR SO when I played everyday I get it like every single second it's so annoying plus I get contacting destiny servers during trials of Osiris which made me super mad!! After a little of research of this error code I've figured out its all the router and yes my internet was perfectly fine running 80mpbs download and 60 upload no problems all fine every game never laggs but destiny always gives me weasel and contacting destiny servers. What I did is I bought a new router and just a relief I haven't got a single weasel error code or contacting destiny servers for almost 1 week!
-
Bump bump even after the recent update am still getting this damn error cant play 1 game without it kicking my only game that does this SO SAID they want to charge 60 for a game another 40 for two dlcs and another 40 for taken king fix the servers man. My end is good am in IT so I know what am doing.
-
They tell us the same shit every time we co plain about this and whenever WE fix the "problem" it co tiniest to come back. I've been told to troubleshoot over and over and my connection to Xbox live is great. So why so many BLAMING ERROR CODES!!! FIX THIS SHIT ASAP!
-
not enough people r posting for it to be relevant make ur own forum posts please i cant stand not enjoying destiny on my days off havent played more than 30 mins of gameplay since maintenance update
-
Thank god I got to finish weekly somehow, but it took like 5 hours!!!!!