{{
`${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.
-
1 ReplyDear Bungie, NTS Internet users are now approaching one week of not being able to access Destiny due to the Cattle error on the sign in screen. Could you please provide some feedback as to where you and NTS are in the process of solving this issue? Most, if not all, of the people affected by this bug are beyond the point of frustration with this situation. I believe the ultimate fix to this problem resides in your hands at this point. If that is not the case, I apologize. Every aspect of my internet service works fine except for Destiny. That includes other online games. I know you deal with many, many problems each day, but I implore you to take some time and resolve this issue. It would seem to me that errors like this would take priority over whether or not somebody can see their ship, or similar cosmetic bugs like this. At least those people are in the game playing. Those of us with the Cattle error cannot even access the game to play! Please make this issue a TOP priority if it is not already. I have no way of knowing if it is being worked on due to the lack of information you are providing. Your attention to this important function will be much appreciated!
