{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by 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.
-
I'm having the same issue, and have the same setup, Xbox One, with a wired connection. I keep getting kicked out of strikes right before they end and don't get the rewards for beating it. I also get kicked out of free roams very often as well!
-
Edited by Onilink: 9/11/2014 4:50:17 PMI had this problem in the Beta and hoped it would be fixed, now I don't know what to do. I'll admit the problem has weakened in the full game but it is still present and frustrating. I'm on Xbox One, using Open NAT, I have tried wired and wireless but there isn't much of a difference. If anyone has any information on Bungie working on a patch, I'd be grateful if you could share.
-
Im getting it too
-
1 ReplyI believe that's the error I got going to the reef, part way through the cut scene with the Queen it disconnected me. I now can not go to the place on the reef because it is gone. I can click on the reef but no missions show there now.
-
6 RepliesYeah, I get bee at the end of about every crucible match. Or near the end anyways... The game will play flawlessly for about 5-10 minutes then suddenly kick me out and disconnect me from Bungie. I've gotten kicked out of missions once or twice but most the time I can play them for hours with no problems. Sometimes during crucible matches it will start flashing "connecting to bungie servers" or something at the bottom of the screen, but even during that there is no lag and I can still play fine. I don't have the best internet in the world, but I can play all of my other multiplayer games without any problems. Not sure what the problem is with Destiny but I hope it's fixed soon as I don't want to have to stop playing.
-
I only get it in PVP. I've only been able to finish one match. Pve works just fine.
-
Open NAT... Same problem... Can't play crucible and occasionally get it in fireteam strikes
-
I am also plagued by the bee. Always get kicked halfway through a crucible match. And once or twice a night playing coop. xbox one no firewall
-
This is such a joke, I get the bee message about 5 mins into every crucible game and can't complete any of them. I don't get disconnected in missions rarely and never in the tower. I've done everything and even taken my xbox to my mates house where he is playing destiny fine on his xbox one and mine still makes the bee error! This leads me to this it could be my xbox or the game disk itself...? my xbox plays all other games fine so all I can think is that it is directly related to the game itself. Bungie could atleast say they have a problem to stop people faffing around with network settings that don't seem to be doing anything...
-
This is a joke now.... Not even any word from bugy.. I mean Bungie. Come on guys, I'm the only one out of my friends having the prob too which is infuriating
-
I'm on ps3 and I can't go 5 mins with out hitting bee and its kinda disappointing
-
I am have the same problems I keep getting the error code bee and my internet is grate with most game it only seem to kick me out on the odd occasion
-
I keep having the same problem but I'm getting either beaver or bee error and I have a wired ps4 less than 2 feet from router
-
2 RepliesEdited by The_Jackel2072: 9/11/2014 3:40:56 AMLet me clarify I have opened all necessary ports on my router, made a static ip for my PS4. I still get error code bee. Mainly strike missions but I will also get kicked out of the tower, the crucible, and explore after about 15 to 20 mins. The only solution I have found is to plug my PS4 directly into my modem. Which is really inconvenient...
-
I'm getting error "bee" a lot, I've not been able to finish one game in the crucible. I have been having trouble with my NAT but that should be fixed now.
-
Error code marionberry .. I can't also start the game .. Why I bought this game. I loved this game since yesterday
-
I CAN'T PLAY ALSO THE NORMAL GAME NOT ONLY CRUCIBLE ... I can't start the Game ERROR CODE "MARIONBERRY"
-
XOne - wireless - forward - NAT open Mostly bee error on crucible(in every single game), sometimes even on coop
-
1 ReplyI have this too whenever I go into the crucible and I have also never had an issue on my end I just don't understand why Bungie are ignoring this, complete crap by them. Even there Centipede fix is rubbish, it's about time they acknowledge they are having issues and give us an eta
-
Yes, I'm getting it alot!
-
Same here. Pls bungie fix it.
-
Now I'm getting Heron errors, thats a new one for me.
-
Same as you: Xbox one - wired connection - ports forwarded - open nat - no problems on any other game.
-
I was suffering from this a lot: PS4, Wireless, Ports forwarded, NAT 2 But I tried some home plugs (Route your internet through your house's electrical system) and it's somehow miraculously fixed it. Bizarre!
-
I'm having trouble with error code Bee, and occasionally Centipede. I can't even do anything. It's sad when I can't even finish my 5 wins in Crucible bounty without getting disconnecting during the match. It's veeeeeery rare when I make it through a full match. I really hope it's on their end and not mine, I've never had previous issues in any other game and I love Destiny to death, but only during solo runs right now..
-
PS4 - wired connection - ports forwarded - DMZ on - NAT 2 ( I can't get NAT 1 due to my provider) - works just fine with other games I keep gettin kicked off the crucible matches (sometimes at the beginning, sometimes I managed to play more than half of the match). I rarely incur the Bee error code in the tower, too. Otherwise I never got connection issues in the other modes (story, strike etc.). The most frustating thing is that I had all those problems playing the beta, both on PS4 and Xbox One console.
