{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/26/2015 5:45:59 AM
3
Does this only work with these error codes? I've just installed a new modem through Comcast yesterday and everything was fine both then and this afternoon. Tonight it all went to hell and I got 7 Caterpillar errors and disconnected from LIVE 5 times. All within two hours.
English
-
xbox is experiencing limited services in some areas, so that might be your problem. If it continues longer than a day, you need to auto configure your network settings and see if that fixes the problem. You might need to also go into your modem's setup (depending to the type of modem - if it's a modem and router in one or something that might require you open certain ports) and adjust your settings that's best for you. If you keep experiencing problems for a day or longer, post back on here.
-
I've still got loads of errors popping up. I haven't been kicked from LIVE at all, but this morning I got Caterpillar 5 times, and tonight I've gotten Caterpillar 8 times, Cattle once, and Fly twice. These happen when I'm on patrol, especially when a Public Event triggers, or when I'm trying to go to the Tower.
-
I believe that's when your connection tries the hardest to stabilize due to loading the game world, players, etc.... So like I said, new equipment might mean you need to configure your router to open specific ports to allow more "traffic" to flow thru your connection. Google "destiny or bungie open ports" and get those port numbers. Then get into your router directions on how setup port forwarding. It could just be that you have to open those specific ports bungie requires to let the game flow smoothly. I had to. Either way, start there with "port forwarding". If you can't find directions on how to do it thru ur Comcast stuff, you can contact Comcast directly and they'll be able to walk you through the steps. Just get the port numbers bungie requires first before you call. Hopefully this solves your issue.
