{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by BraveSirrRobin:
7/15/2015 11:01:15 PM
15
Solution to Networking Issues with Hitron CGN3 Modem and Possibly Other Modems
In my previous post ([url=https://www.bungie.net/en/Forum/Post/125223029/0/0/1]click here [/url]) I outlined the steps I took to rectify the issues I have been experiencing with the Hitron CGN3 router provided by my ISP (Rogers). Overall, the Destiny community identified the Hitron CGN3 modem doesn't connect well with Destiny servers, which Bungie agreed with; however, sadly Bungie offered me no solution.
To make a long story short, I believe I found the best way to rid yourself of your networking woes. The solution is to set up bridge mode on your ISP modem and use a secondary router as your gateway. This solution worked for me so hopefully it works for you as well!
[b]NOTE:[/b] This fix is for XboxOne. I'm assuming the same methodology can be applied to other consoles.
[b]Step 1: Get the following equipment[/b]
1) ISP modem/router.
2) Secondary router (I used the Linkysys E2500).
3) Laptop and network cables.
4) Some patience and time (I’m hilarious!).
[b]Step 2: Read and Learn about Network Troubleshooting![/b] (You can skip this step)
1) Read through Bungie's [url=https://www.bungie.net/en/Help/Article/11930]Network Troubleshooting Guide[/url] to gain an understanding what you're doing. Trust me, do this!
2) Read through PortForward.com [url=http://portforward.com/help/destiny/]How to Port Forward Destiny[/url]. This guide will give you all the information needed for your secondary router.
[b]Step 3: View these YouTube videos by ManiSuReal[/b]
1) [url=https://www.youtube.com/watch?v=bD-mHgVyiQA]How to set a Static IP for XboxOne[/url]
2) [url=https://www.youtube.com/watch?v=xXzidslAZdc]How to enable ports for XboxOne and Destiny 2014[/url]
[b]Step 4: Fixing Destiny: Bridging your ISP Modem[/b]
[b]1)[/b] Wire the Hitron CGN3 modem and XboxOne into the Linksys E2500 router.
[b]2)[/b] Restore your Hitron Technologies CGN3 modem and Linksys E2500 to its factory settings.
[b]3)[/b] Using your PC, wire into the Hitron modem, open its configuration application, and follow the instructions found at [url=http://www.rogers.com/web/support/internet/home-networking/247?setLanguage=en]Rogers.com[/url] to turn bridge mode on.
[b]4)[/b] Using your PC, wire into the E2500 Linksys router and setup your network and Wifi.
[b]NOTE:[/b] Keep your PC wired into the router.
[b]5)[/b] Turn on your XboxOne and select: Settings > Network > Advanced Settings. Write down the XboxOne’s IP address.
[b]NOTE:[/b] Do not power off your XboxOne.
[b]6)[/b] Using your PC, in the Linksys E2500 configuration application, select: Setup > DHCP Reservation. Now, reserve the IP address of your XboxOne.
[b]NOTE:[/b] You’ve just set up a static IP address for your XboxOne, good job!
[b]7)[/b] Using your PC, in the Linksys E2500 configuration application, select: Application and Gaming > Single Port Forwarding. Assign ports 53, 80, 88, 500, 3074, 3544, and 4500 to your XboxOne's static IP address.
[b]NOTE:[/b] Use the configuration that ManiSuReal suggested in Step 3, video 2.
[b]8)[/b] Using your PC, in the Linksys E2500 configuration application, select: Application and Gaming > Port Range Forwarding. Assign ports 7500-17899 and 30000-40399.
[b]9)[/b] Save your router settings, turn your router and XboxOne off, unplug both devices and turn them on again.
[b]10)[/b] Open the Network settings on your XboxOne. The NAT Type should indicate it's Open.
[b]Congratulations![/b] You may have successfully fixed your Destiny connection. This solution isn’t perfect; however, I’m rarely being removed from PvE and PvP games, so it leads me to believe this solution does work. I’m not an expert at networking and I apologize in advance if my technical language is a bit off or if this solution doesn't work for you.
Cheers and best of luck Guardians.
[b]EDIT:[/b] Apparently Rogers has come out with a firmware update that completely resolves the connection issues with the CGN3 modem, without the need to create a static IP for your Xbox One and/or port-forwarding. I haven't confirmed this but once I do I'll report back.
-
1 ReplyI have now had 2 different CGN3 modems at 2 different locations that gave me the same issue. Called Rogers. They pushed the new firmware 4.5 and it works flawlessly. It can take 24-72 hours which does suck but it pays off. All the hoops that have be put forth for you to jump through are not needed if you make a simple phone call. Did not need to set a static ip or put the console in the DMZ. No port forwarding needed. All of this is a flaw with the modem and not rogers or bungies fault.
-
Edited by me2ez: 7/6/2015 3:13:24 PMIm just here to play video games. And instead of having to deal with this nonsense ill just happily play other games until they fix their encyclopedia of error codes.
-
Bump for awareness
-
6 RepliesFrom my discussions with rogers, the modem needs a firmware update. Call them and they will push it out in 72 hours. I'm awaiting my update. It's supposed to be pushed to everyone in 2 weeks
-
1 ReplyBraveSirrRobin, Thank you so much for taking the time to post this. It's been very helpful and my connection is much better. It shouldn't be necessary to go through all this effort but Microsoft and Bungie have gotten their money out of us so what do they care if the connection is stable or not. Still getting Beetle, Viper and Anteater errors but with much less frequency. It used to be that I could only connect for about 5 to 10 minutes but I played the PoE the other night for an hour with no disconnect issues. Cheers, CanadianSocks PS: Great name. Gotta love Monty Python. I hope when you get into trouble playing you yell, "RUN AWAY!" LOL
-
Bump for awareness
-
3 RepliesEdited by KatzeHalifornia: 6/23/2015 2:13:41 PMHi BraveSirrRobin (great GT, by the way), Thanks for posting this! I'm going to try out a few things before a buy a new router (sigh). We are moving our XB360 upstairs to the other tv and will be hardwiring it to our modem downstairs. We are also going to be wiring our tv upstairs to our terabyte drive. We will be using an unmanaged switch to connect the two to the modem downstairs. I am going to try and replicate the conditions that the bridging provides with the unmanaged switch (which is way cheaper than a second router!). Will write back and let others know how it goes!
-
3 RepliesThis is probably the most helpful to people in our situation. I am not being a douche but if you mean Hiltron instead of Hitron, can you add 'Hiltron' as a tag? Maybe add your ISP as well. Great post and the help by other users is above and beyond!
-
1 ReplyThanks man, I'll try this tomorrow
-
12 RepliesThis is outdated, and overly-complicated advice. Port forwarding is an obsolete solution, with several limitations: - the console doesn't know what ports are being forwarded, so it can't tell other consoles what ports it's on, or know with certainty what its NAT status is - the console can't decide for itself what ports to use, so if you want to have, say, an Xbox One and a 360 on the same network, you are SoL - You're setting up which ports get forwarded manually, so if these requirements change (say, in a dashboard update), you need to find out about them and make the changes yourself. There's a far better solution, and it's one OP got so close to before snatching defeat from the jaws of victory: [b]get UPNP working[/b]. UPNP IGD is a modern technology that solves all these problems: the console itself requests ports be forwarded, and the router tells the console what it's doing. Port forwarding through UPNP just works: switch on your console, and it will discover the router, and ask for its ports, without you needing to configure anything. If two consoles want the same port, the router tells the second one it can't have it, and the second one will pick a different port. Because the second console has been told what's going on, everything still works perfectly. You can even join the same multiplayer session and party chat on two consoles behind the same router. [b]So how do we set up this amazing technology?[/b] The answer is very simple: we get a router that supports UPNP, use that as our new main router, and remember to switch UPNP on. We tell our ISP's router that our new router is the DMZ machine, so the ISP's router forwards all ports to it. ...and that's it. No messing around with static IPs, no messing around with port mappings, no messing around with settings on the consoles. Switch them on, and they just work.
-
I have talked to Rogers Tech and they are aware and acknowledge the issues gamers are having with their new (better) modem and recommended going BACK to the CGN2 model or bridging with a router that supports UPNP. I've noticed on my console that Xbox is having matchmaking issues, so wonder if that could also be the problem
-
2 RepliesKudos to you,sir for going to all this trouble. But have we really reached the point where gamers need to train in IT just to play a game that cost 80 quid/bucks? Or am I about to receive a slew of replies from PC gamers along the lines of 'Welcome to our world!'.
-
2 RepliesYou forgot to include finding dns servers, not as important as forwarding ports but still worth changing. Google "Namebench" on pc, run program and set recommended dns servers through router and all devices (with static ips)
-
2 RepliesAin't nobody got time for that! [spoiler]I seriously hate the rogers router, thank you for posting this. I need to do this asap[/spoiler]
-
Edited by Pure Potential: 5/29/2015 8:28:18 PMHopefully this helps people with similar issues. Good work with this post.
