{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
delapugにより編集済み:
9/12/2014 10:33:01 PM
308
Could everyone getting bee error post in here
Please if you're getting this error post in this topic. No stupid remarks about get better internet or other childish remarks. I'll start off.
Xbox one - wired connection - ports forwarded - open nat - no problems on any other game.
[u]UPDATE[/u]
I don't want to be the one to say this but I went and bought a new modem/router(DSL) just plugged it in and no errors for the past 5 hours in the pvp which I couldn't play at all before. Don't know if that means anything but it seems to have taken care of me.
[u]UPDATE 2[/u]
I've been asked a few questions so I thought I'd do another update with my settings
I switched from a netgear combo unit supplied by my isp to an Actiontec GT784WN wireless N DSL Modem. Like I said when I first hooked it up I just made sure plug and play was enabled on the router and started up the xbox and destiny I went straight to the crucible and began playing and haven't stopped since, no more errors at all the only problem was that my nat type was strict. To fix that I forwarded the following ports
Port 88 (UDP)
Port 3074 (UDP and TCP)
Port 53 (UDP and TCP)
Port 80 (TCP)
Port 500 (UDP)
UDP Port 3544 (UDP)
UDP Port 4500 (UDP)
Port 3075 (UDP and TCP) *for call of duty
Ports 7500-17899 (TCP)*from bungie
Ports 30000-40399 (TCP)*from bungie
Ports 35000-35099 (UDP)*from bungie
I now have an open nat and no more errors and even though I suck I can play PvP. I really hope this helps this is exactly what I have done, I compared the settings on each modem/router and other than a few years difference in manufacturing there was no difference.
-
12 通の返信We just updated the BEE/FLY/LION help articles, and are actually making progress on this issue! Read more here (scroll to the bottom for updates): http://www.bungie.net/7_Error-Code-BEE--FLY--LION/en/Help/Article/11791
-
Just started happening this week. I'm getting mostly bee and fly errors, though I've had a few other animals and insects. I just bought a new router a month ago. I'm wired to my router. I can't stay connected for more than a few minutes, no matter the game mode. It is literally broken for me. Not cool. Not cool at all.
-
1 返信I'm getting the bee error so much I can't stand this game. I want to play it so bad but that is the only thing stopping me. I can't get through five minutes of a match without getting the bee error. Please fix this before I have to do the unthinkable and take it to gamestop. My Destiny is your hands now Bungie.
-
I am getting Bee Zebra Lion and DC errors so much it's unbearable before u made the patch to fix the connection issues for people who had them I had never seen an error code now I can't get to the tower with out 6 attempts I can not do anything bungie raids I dc every 20 mins ppl hate to run with me I miss loot I'm level 29 and can't progress threw ur dumb game since ur updates I wish u never made an update to fix it cuz it was never a problem till u did and pvp forget it my Psn is same as name please fix my acc I love ur game ur servers are a joke tho
-
5 通の返信A note to Bungie. We hope you’ve heard, And we hope you see. We’ve got a problem, With an annoying Bee. We do our best, To fight the fight. But every time, The Bee takes flight. We’re kicked from our game, As if we’ve been stung. Thrown from the world, As if we’ve been flung. We’ve tried all we can, It can’t be beaten. We need a light in the dark, To act as our beacon. Please understand, We don’t blame you. I bet you’ve got problems, Effecting you too. So Bungie please, Lend us a hand. We’re stuck without, A leg to stand. It’s glory in the Crubile, That we all crave. So hear our cries Bungie, And please, Be Brave.
-
I get bee errors every so often. It can vary from being disconnected every 3 minutes to every 2 hours. Extremely frustrating to be in the middle of a good run with heroic modifiers and a no respawn zone when I'm just kicked back to the login screen.
-
1 返信redoubt9000により編集済み: 10/4/2014 10:30:06 PMSame, for both today and yesterday constant bee errors. Playing since launch with absolutely no problems on a NAT 3 connection (which only affected mic chat, otherwise no issues arose from that). Short of using hardwire, which made little difference as I still received a NAT 3 connection with ports forwarded... Again until the past two days, it was smooth sailing.
-
1 返信All ports opened open Nat type...Bee every time I try to play the crucible, I love the game but! My pateince is wearing thin. :( help meh,Bungie, help meh!
-
Threre is still a significant Destiny population that still can't play this game as intended 30 days from Destiny going live. Can't understand why they didn't wait before putting the game out to make sure that all the game could be played especially PvP. Out of the 100 games I have attempted in PvP I may have finished no more than 10 before getting kicked out with a bee error code. I have spent more time with error codes than I have been playing.
-
1 返信I'm having the same problem as everyone else, I play on Xbox one all ports forwarded wired connection everything that bungie has suggested and still not working. I've been able to play 3v3 with greater success but whenever I try to play 6v6 I always get the bee error. I've been playing games on Xbox live for years and never had a problem this frustrating, I payed over $100 to play this game and can't really enjoy it because I can't play crucible. Bungie needs to fix this problem or at least acknowledge that there is a problem and not blame it on the gamers packet loss.
