{{
`${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.
-
2 RepliesEdited by Blue marksmen: 9/11/2014 12:16:56 AMI'll break the mold, since everyone seems to be having crucible problems, I'm getting them during a mission. I'm getting a Bee error EVERY. SINGLE. TIME. I try to play the endless steps mission on Venus (the idea of an entire planet getting turned into a machine sounds more ridiculous each time). I have played other strikes. Other strikes on Venus (every other strike in fact). It only happens here. I have rebooted my PS4. I have deleted and Re-installed Destiny. It still happens every time. Here is the really weird thing: it seems to be tied to a specific location. At the point where you reach the non-baryonic mater stream or whatever, and deploy your ghost. I also got it while trying to do the vex sacrifices public event. I did not try to activate my ghost. A side note, this is also the place where I always pass another player or two. So, possibly this also is a part of the problem. Yesterday I had smooth playing, alone, with friends, in a fire team, etc. Although my PS4's wireless problems reared there head a couple of times, this can't be the same things, since those seemed random, and this has consistent, reproducible behavior. I've gotten the "Bee" error 4 times now, and the "Centipede" error twice. All in the same small area. I'm on a PS4, connected over WiFi, my NAT type is 2.
