JavaScript is required to use Bungie.net

Help

Help us help you.
9/16/2014 5:04:33 PM
0

I finally killed the Chicken error

So, I have been having connection issues to Destiny since the launch, and have had my fair share of swearing at the game. After disabling firewalls, port mapping, switching out devices, and generally doing everything suggested, I found my issue. Now this is not to say that it's the same as everyone's issue, but this was mine. I found that I had full internet access on my ps4, as well as a NAT type 2, and a static LAN IP. Even with all of this I still found I would not be able to login. I checked the settings on my router, and found nothing a miss. I finally discovered the issue in my NAT mapping table. It seems that my computer was running Transmission(a torrent program) and it was in turn using and conflicting with the exact same ports Destiny was requesting. Once I turned off the program, my issues stopped. This could mean that the chicken error is due to internal issues of assigning the UDP traffic back to the PS4, as something else is using the same handshake. Just my couple of cents, and I hope it helps everyone.

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