{{
`${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've been playing since launch day (almost two weeks now), and I haven't had a single problem aside from one disconnect about 3 days after release. It was a no name error that kicked me to my ship. I restarted the match, and everything has been fine up until yesterday. Then, I started getting Cattle errors for about a half hour or so, and I couldn't even log in. That seemed to have fixed itself after a couple hours, and then I played for maybe 4 straight hours that night after I got off work, along with the 2 or 3 I played after the Cattle errors subsided before I had to go to work. I thought I was in the clear. Oh, how wrong I was. Now, I'm getting the Bee error after about 10 minutes into a strike. It's really aggravating. I would say that it was on my end if this had been happening from the start, but I've been playing nearly everyday for at least a few hours for nearly two full weeks. If it's on my end, how could this just start happening now? Nothing has changed in my home network between then and now. Even the beta ran just fine for me. I had maybe two or three disconnects the whole time I played, and that was a beta. Now, I've played nearly flawlessly for almost two weeks on the full game (which I've been enjoying), and it's going to choose now to start giving me issues? Just to add insult to injury, I'm actually off on a weekend, and I have all day to do whatever I want. Well, I guess it's not going to be playing Destiny.
