{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Scionyde:
9/18/2014 2:41:58 PM
281
Post Your Connection Issues/fixes Here - Home Networks
I have seen many of these threads, but it seems that most of the posts are just people ranting and complaining. I will say that I am quite guilty of that as well, and my patience is growing thin, but I think we should try to provide Bungie with more specific information so they can get our issues fixed as soon as possible. Please post your specific issues in here, and try to keep it short-ish, to the point, and present it in a professional manner so they don't have to comb through garbage to find what they could possibly need.
I'll start by saying:
I'm on the Xbox 360. I am on my home network. I get mostly just BEE and CENTIPEDE after entering any game zone. I can sit in orbit and stare at my ship for hours, but even entering a mission, strike, crucible match, or the tower nets me a BEE error within 2-10 minutes. I'VE HAD THESE ISSUES SINCE DAY 1. I've tried all the workarounds mentioned on this site (NAT Type, opening ports, QoS, disabling flood protection, DMZ server, static IP for router and console, hard resetting everything multiple times, deleting system cache, deleting and reinstalling the game, using a VPN, going wireless and wired, and multiple combinations of all of these)
Any help/reply would be appreciated. We must keep hammering them until we are heard.
Also, pass this around the forum:
http://arstechnica.com/gaming/2014/09/eight-days-later-bungie-leaving-disconnected-destiny-players-stranded/
^This is getting ridiculous. We are not a tiny portion of the community.
-
6 RepliesI have already posted this in a couple of places. I will post here again to increase the viewer base. After doing some testing on my network I contacted my ISP. We were able to find the culprit for my Cattle Error. It had to do with the packet routing. Who ever was handled routing table for the outgoing traffic probably had something messed up. My ISP switched were there outbound traffic was going and I was able to connect immediately. This is because the internet traffic was taking a different path to the Destiny servers. My buddy who lives in the same town and has the same ISP, was also having the cattle error code and this fixed his problem as well. So you guys might want to call your ISP and see if they can switch who they are routing their outbound traffic through. If you are using a larger company for your ISP , for example Comcast, just have them look into their packet routing for destiny. Those of you who have a smaller local based ISP might get quicker results. I hope this helps someone. If you have any quests please feel free to ask and I will answer them to the best of my ability.
