JavaScript is required to use Bungie.net

Service Alert
Destiny 2 will receive an update tomorrow. Players will be required to log in to Destiny 2 again after installing the update. Please stay tuned to @BungieHelp for updates.

Help

Help us help you.
10/7/2014 8:54:48 AM
2

Any solutions for error code 'groundhog?'

TL;DR - I can't fix my groundhog errors. Can anybody here tell me if/how they fixed theirs? --- I've tried to refrain from posting about errors in the hope that they'd be fixed soon after launch, but I'm getting increasingly frustrated with the frequent disconnects and kicks to orbit. At this point, I feel like I've seen most of the zoo/supermarket of error codes, but the one that gets me most often is groundhog (probably followed by coconut). I don't have a stellar internet connection; it's ADSL at ~5.5Mbps down and 1 up, but it's generally stable - I have 1,000+ hours of online games logged on the PC wired into the same router that my PS4 is wired into (a lot of Warframe and Diablo 3) and have had only the most occasional connectivity issues with those games. With Destiny, I worry about finishing even individual patrol missions, and I gave up tonight on trying to get a public event done on one of my characters after getting disconnected repeatedly right as the event windows were opening or even during the event (tonight - in the mothyards with friend, event begins, disconnect, rejoin, disconnect, rejoin, make it back to event just in time to see everybody [i]else[/i] get their ascendant materials, disconnect). Every time I start to cross into a new zone I brace for a disconnect. If I get DC'd from a friend's fireteam, I usually have to wait for them to cross into a new zone before I can reconnect. I get DC'd from darkness zones when I'm soloing content. I [i]have[/i] occasionally gone for hours without a disconnect (thankfully my raid attempts have been solid so far), but once groundhog errors start appearing, I may as well call it a night. I've seen a handful of user reports that groundhog is due to an interrupted or excessively laggy connection. Destiny's is the only connection that breaks though - I never lose my PSN party chat, I can still browse the internet on my PC, and the never-ending ping test I sometimes set going on my desktop ('ping -t 8.8.8.8') shows no dropped packets or timeouts, so I know my packets are at least leaving the house. My PC continues to play Warframe and D3 as well as it ever did. Onto my network setup. Plugging my PS4 into my router with no additional configuration I get a NAT type 2 (moderate). I tried setting up port forwarding rules, setting a static IP, and eventually putting the console into the network DMZ to see if I could get NAT type 1 (open) but to no avail - still shows at type 2 - an ISP issue? I've tried playing with all the other net-connected devices in the house turned off (phones, PCs, other consoles). I even bought a new modem and router since the old unit was, well, old. Nothing has helped (new router did let me jump on the AC bandwagon though). The only other thing I can think to try is to replace or eliminate the one unusual link in my home network setup: a powerline connection that connects my PC and consoles at one end of the house to the modem located at the other end of the house. Unfortunately I don't have that long an ethernet cable handy. And I really don't want to dismantle my home office/theater setup to plug straight into the modem. I may try this weekend. And so I ask - has anyone who has faced the dreaded groundhog of frustration and disappointment managed to eliminate it? What other potential fixes am I missing?

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon