{{
`${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.
-
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).
