{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/16/2015 9:59:22 AM
6
Port for Destiny
OK I am a complete novice when it comes to opening ports, please please bear with me I have struggled to set my router up for almost 2 weeks now!
When you look at the ports to open for Destiny it lists for the XB1:
TCP outbound: 7500-17899, 30000-40399
TCP inbound: 53, 80, 3074
UDP outbound: 53, 88, 500, 3075, 3544, 4500, 1200, 1001
UDP inbound: 53, 88, 500, 3075, 3544, 4500, 1200, 1001
So I am assuming on my router for example 53 I can set this port protocol as any as it's used for TCP and UDP?
And the TCP outbound 7500-17899 is this a range? as in set it from 7500 to 17899? as I set them as individual ports so I am hoping this is my mistake?
Please any help would be appreciated this is my last throw of the dice before I give up.
-
8 Repliesok I give up, I have no port forwards assigned and if I try and port forward I get a message saying ""The game or application you've selected conflicts with an application () you've assigned to another device" No other devices are port forwarded and I removed the other forward rules I had assigned to the Xbox one, and removed the lines that needed to become a range I re-started the router before I created new rules as a range, as soon as I tried to apply them to the Xbox one IP I get that message. I am a little reluctant to factory re-set the router again, as for the next week it does a line stability test and it means my internet is junk during that time. So it seems I need to forget Destiny and play something else.
-
6 RepliesPort 53 udp/tcp is DNS. You cannot forward this port.
-
3 RepliesAdvanced network configuration should not be necessary to play Destiny reliably. Please try resetting all of your hardware and reconfiguring your console's connection before doing any port forwarding/port triggering. Leaving any port open can present security issues, and it's not really designed for a novice to do. While after watching a few youtube videos you'll be able to do it, you may not understand the risk you leave yourself open to. I recommend starting from scratch, factory reset network equipment first.
-
1 ReplyThere are two parts to the [url=https://www.bungie.net/en/Help/Article/11931]help article[/url] that lists the ports Destiny uses for each platform. The first section lists any port the game might use (yes, that's a range for TCP outbound), but as far as configuring your router goes, go with what is listed in the second table "ports to forward to your console to provide open nat" When a port is listed in both TCP and UDP, then setting the protocol to "any" should be fine. Also, make sure your console has a static IP address, as you should have to specify the consoles IP to forward the port traffic to. YMMV of course, but I've had bad luck with my older linksys router if I had the console getting a dynamic IP, and trying to use a DHCP reservation to give it the same address each time. Note that the ports listed also include the ones for Xbox Live service. So concentrate on getting these forwarded to your xb1: TCP and UDP/Both: 53, 3074 TCP: 80 UDP: 88, 500, 3544, 4500 Just to be safe, power down the console (or have it off when making the changes) and restart the router after updating the forwarding configuration. Port forwarding gets more complicated if you have multiple consoles trying to play at the same time, or if you have a separate router and broadband modem. If the modem is in bridged mode (or can only bridge, doesn't really route), then it shouldn't effect your port forwarding.
-
1 ReplyYou should be able to set them as a range and yes, "any" should work.
-
Bump any advise on this please?
