Full discloser, I did figure out the issue I was having. I was under a double NAT. One from my ISP and one from my router. I have a separate modem and router.
I connected my XB1 to my modem directly and restarted my modem. After that I had no issues. But why did I have to do that? I understand a NAT and the issues that bares but if I can be under one, from my ISP, why does being under two cause so many problems?
This is an issue I would like to investigate if anyone has an idea of which direction I should go. My first thought is the nature of TCP/IP with its myriad of protocols, but if that is the issue wouldn't a tunneling protocol take care of any issues?
Anyway, thoughts and comments are welcome.
Love this game and I would like to make the experience better for all players. (Not just those with a dedicated connection) :)
English
-
I don't have seperate. I have my router from my ISP, my box is connected on the wifi with no interruptions or weak signal. My discontents always happen with an immediate disconnect and weasel error message as if a light switch is flipped off. I'm returned to the title screen where if I attempt to immediately begin the game it will give me the canary error code for about 30 seconds since it apparently cannot detect an internet connection despite me usually being in a party. It has been this way since destiny 1....
-
Baal, you issue sounds just like mine. Your second NAT is the wifi. If you can connect directly to the box and do the DMZ it should fix your problems. You might be able to do it with wifi but I'm not sure. My experience with wifi is limited.
-
I believe I've tried that before but I'll give it another try. Just boggles my mind why the hell I even have to go through this in the first place. It's highly annoying.
-
Edited by Squidy P: 7/15/2018 2:34:15 AMI agree. Don't have this issue with other games!
-
If you use your modem only for your internet connection and use your own router, then you want to go into the modem and set your router as DMZ point for it. The UPnP port opening generally only goes through one firewall but may be blocked by a second one, thus leading to issues. This isn't always the case, but it sounds like it was the case for you, and why bypassing the first one fixed it.