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