JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Phane7: 6/2/2015 9:35:15 PM
0

Near constant Marionberry and Emu

Edit: Nevermind. I found that a miniupnpd update overwrote my old miniupnpd.conf. The default one caused a conflict with port 3074 on my Xbox 360. I had this problem once before during the beta and thought it had been fixed, but over the last week or so I've had no luck at all connecting to Destiny. Almost every time I try I get booted before the character select screen with marionberry. I changed DNS settings to Google DNS and that worked for a while, then one day I started getting disconnected when moving from area to area and then got booted with EMU only to have marionberry come back. Changed DNS from Google to Open DNS and back to my ISP and nothing works. Every time I try and connect now, it's marionberry. I've reset my router and my PS4. I'm connected via gigabit ethernet to the router. I have UPNP enabled for the PS4 and it is working. I tried turning it off and it didn't help. My router is running IP Fire 2.17 CU 90 and I can't find anything in the IP Tables that indicates Destiny being blocked. PS4 network tests are all successful and indicate NAT Type 2 and all other games work without issue.

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