JavaScript is required to use Bungie.net

Forums

Edited by Enza Knight: 9/26/2014 9:18:43 PM
5
This fix did not work (see replies) Hi Scionyde Have played 3 hours without being kicked off the server. Here's what I changed. Switched my port forwarding off And I think most importantly turned off IPv6 I kept static ip for Xbox and obviously UPnP is on I then shut down Xbox One, rebooted Modem and restarted Xbox One. There was also a small update about 1.8mb for Destiny game but do not think would have made the difference Let me know if it helps you. I will confirm fix in a couple of days.
English

Posting in language:

 

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

  • I fixed mine by limiting my bandwidth. You can apparently get a "more consistent" connection by lowering your upload speed until it stops losing packets. I still get error codes a lot, but I've actually been able to halfway play now. Refer to Jorgelucasds's post about it. Good luck guys.

    Posting in language:

     

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

  • So I got kicked off doing a challenge with a friend after 5 mins. Decided to revert to my original setup i.e static ip, UpnP and iPv6 and played solo and multiplayer for a solid 2.5 hours with no problems. So like most I have tried every option and can only conclude that its Destiny game or Servers. Sorry folks.

    Posting in language:

     

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

  • Enza, What this tells me is that you didn't have port forwarding configured correctly - you possibly missed forwarding some. What UPnP does is that it will automatically map any available port to an incoming port request. The mapped port may or may not be the same port that the incoming request is for. UPnP is useful if you have more than one console on your home network that may be contesting for the same port. However, if that is the case, the best way to get around it is to use port triggering as opposed to port forwarding. The reason is that port forwarding requires that certain ports are tied or mapped to a specific IP. That will also cause other devices on your network requiring those ports to fail. Port triggering, on the other hand, specifies an outgoing port based on a trigger from an incoming port request. The trigger may or may not be the same port you open for outgoing transmission. Port triggering is based entirely on an input trigger and doesn't require the outgoing port to be mapped to a specific static IP. That is why port triggering is the best way to allow multiple consoles to coexist on the same home network. UPnP is easy. You let the router take care of all the mapping details, but it does open you up to possible security risks. If you can figure out how to set up port triggering, I highly recommend you to do so as that is the most secure way to go.

    Posting in language:

     

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

  • Thank you for the great reply Mike. Your correct, I could not set up 1 port. Understand the security risks. So my fix has not held but tried another option. Go to Network on XB1 and choose multiplayer test then activate both bumpers & triggers. If this does not show "Cone NAT" then repeat until it does and this appears sort out ports ? This seems to stabilize my connection more. Will let you know how things go after tonight.

    Posting in language:

     

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

  • Edited by mikelimtw: 9/28/2014 7:11:29 AM
    I don't have an XB1... yet. They just started selling here in Taiwan 2 days ago as Taiwan was not an original launch region. I may pick one up by the middle of next month. We'll see. If I do, I'll be able to see what you're talking about and maybe give you some more suggestions. As to not being able to map 1 port, I had the same situation for my PS3 Destiny contesting 3074 UDP with Xbox Live 3074 TCP/UDP - I own both a 360 and a PS3. Since you're on XB1 and Live, I am willing to bet this is the port you're referring to. Now 3074 is not required for PSN, but it IS required for XBOX LIVE. That the port is also required by Destiny seems to be out of place with regards to the rest of the port allocations, so I'm not sure if Destiny requires port 3074 for compatibility with the XBOX LIVE service or for some other reason. But I'm willing to believe odds are great it is for XBOX LIVE. In this case, you can remove port forwarding for 3074 for XBOX LIVE as that ties this port to a specific static IP in your home network. You can set up port triggering instead for this port to make it generally accessible to everything on your network. It's simple to do so - on your port triggering setup page, just use 3074 as the input trigger port and 3074 as the outgoing port and allow both TCP and UDP data packets. That is the easy fix to this problem. The upside to this is that now you can have more than one XBOX running on your home network and connected to XBOX LIVE concurrently. All the other ports "required" by XBOX LIVE, ie 53, 80, 443 are actually standard TCP IP ports that are required by other applications on your home network. You don't specifically need to forward those. The ONLY port you need to open up for access to XBOX LIVE is 3074. Don't forget to shut down UPnP as you probably won't be able to get port triggering to work correctly with it on. You can use either static IPs or automatic ones from DHCP as port triggering doesn't care what internal IP makes the port request. Hope this info helps you.

    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