{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
This thread is inspired by another: view original post
Edited by Blaubarschboy:
9/15/2014 1:31:55 PM
9
#Bee Error - Help Thread
I opened this Thread to collect all players with the #Bee error. Post your suggestions on how to fix it or what you think could Bungie do to fix it for us. I want to get the #Bee error out of my sight as soon as possible so let's help together!
What i tried so far:
- Static IP on my Xbox One
- Portforwarding for this static IP of my Xbox One to all Bungie related ports and the Xbox Live ports
- restarted the Console
- restarted my router
- NAT Type is "open"
[u][b]Bungie tells us on their help site to open the following ports:[/b][/u]
- 7500-17899 (TCP)
- 30000-40399 (TCP)
- 35000-35099 (UDP)
- 3074 (UDP)
[u][b]and the following for Xbox Live:[/b][/u]
- 88 (UDP)
- 3074 (UDP und TCP)
- 53 (UDP und TCP)
- 80 (TCP)
- 500 (UDP)
- 3544 (UDP)
- 4500 (UDP)
[u]And you should use a wired connection (LAN)[/u]
For me it did not help so far...
EDIT:
i only get this error after playing crucible / pvp for about 5-10 minutes. I only was able to finish 2 games so far.
-
7 RepliesI hope you speak german, because my answer will be in german (just because it's a lot easier for me) :) Ich hatte das selbe NAT Problem wie du, aber bee-technisch bewirkte ein offenes NAT gar nichts. Sehr viele Leute haben das selbe Problem wie du, mich mit eingeschlossen. Das ist eindeutig ein Problem von seitens Bungie und keines mit unserer Internet-Verbindung. Seit neustem wird bei mir "beaver" drauß, aus der Fehlermeldung. Vorher war es immer nur "bee". Eventuell arbeitet man zur Zeit bei Bungie ja dran.. auch wenn ich dran zweifele (hatte während der Beta das selbe Problem auch schon). Übrigens bekam ich bei mir NAT auf "offen", nachdem ich folgende Schritte noch ergänzte: 1. UPnP im Router deaktivieren 2. Konsole und Router neustarten 3. UPnP aktivieren 4. Konsole und Router erneut neustarten Vorher machte ich exakt das gleiche wie du, nichts bewirkte eine Veränderung bei meinen NAT-Einstellungen. Als ich UPnP deaktivierte, neustartete und reaktivierte war NAT dann aber offen. Traurigerweise aber ist das Spiel im Crucible und Tower aber trotzdem noch das reinste Beemargeddon :(
-
[quote]I opened this Thread to collect all players with the #Bee error. Post your suggestions on how to fix it or what you think could Bungie do to fix it for us. I want to get the #Bee error out of my sight as soon as possible so let's help together! What i tried so far: - Static IP on my Xbox One - Portforwarding for this static IP of my Xbox One to all Bungie related ports and the Xbox Live ports - restarted the Console - restarted my router - NAT Type is "open" [u][b]Bungie tells us on their help site to open the following ports:[/b][/u] - 7500-17899 (TCP) - 30000-40399 (TCP) - 35000-35099 (UDP) - 3074 (UDP) [u][b]and the following for Xbox Live:[/b][/u] - 88 (UDP) - 3074 (UDP und TCP) - 53 (UDP und TCP) - 80 (TCP) - 500 (UDP) - 3544 (UDP) - 4500 (UDP) [u]And you should use a wired connection (LAN)[/u] For me it did not help so far... EDIT: i only get this error after playing crucible / pvp for about 5-10 minutes. I only was able to finish 2 games so far.[/quote] Meine nat ist auch offen und schon immer gewesen weil ich von den ersten halo teil an zocke und seit dem 2 te online. Und mir wird diese verfickte bee Meldung auch ständig angezeigt flieg in Minutentakt raus. Von 6vs6 mal abgesehen. Da komm ich garnicht erst rein. Bungie soll das beheben so ist das schöne game für den arsch. das ist einfach ein Fehler im System oder auf den Servern das die nicht erkennen das die nat offen ist oder nicht. Punkte was die andern labern. Macht da was und zwar schnell Bitte.
-
1 ReplyI have changed 3 routers too....nothing changed. There isn't a "true" solution, it's all in bungie's hands...
-
i know what causes my Bee error code. large amounts of other players. if im playing with 10+ people i get the Bee. that means no crucible (except for the 3v3 modes) hardly can stay in the tower. and a public event can be a bitch occasionally i have all of the ports opened and such. i even have UPnp on but im sure destiny doesnt use that. ssooooo yeah. have no idea how to fix that
-
Same here. I haven't been able to finish one match. This sucks so bad.
-
1 ReplyUpdate: At the weekend Bungie gave us a new 3 vs 3 mode (Salvage or so...) and another 3 vs 3 (tactical tdm - do not know the name anymore) and this ones were running OK for me! No #Bee errors. I only get the #Bee error in the 6 vs 6 modes (these are most of them and the funniest so far). So there must be some stability issues on the server side from bungie or the ping? Maybe when i play with people from the us (i am from germany).
-
Unfortunately my solution was to buy new gear. Had open NAT wired connection on Xbox One, great connection speed never a problem on any other game but Destiny. For "grins and giggles" I bought my own new [b]MODEM[/b] and [b]ROUTER[/b] and hooked it up. Since then I haven't had a single Bee error. I know its not the solution you want to hear, but it worked for me. The gear I bought is: Motorola Surfboard sb6121 modem and Belkin F9K1103 N750 DB Wireless Dual-Band N+ Router Again, it's not ideal... but so far its worked for me. On the up side I will now save $15 a month on my cable bill for having my own gear.... shoulda done this a long time ago.
-
Same problem here. Need solutions Bungie!
-
I only get bee when I try to play a strike mission...haven't tried cruicible yet because I want to get to that once everything is fixed. Other than that I get other errors occasionally while playing story missions
