JavaScript is required to use Bungie.net

Помощь

Помогите нам помочь вам.
Изменено (Millenium Milk): 3/30/2015 5:19:10 PM
43

A guide to help you with connection issues...

I've put this thread here as a help guide for anyone experiencing frequent disconnects, problems with staying in strikes or fireteams, getting booted to orbit. They may or may not help, depending it seems, on whether Destiny is happy with your router or Internet connection. Hopefully Bungie can stabilise the way their game connects you in the future, but for now all we can do is see if there is anything on our end of the connection that we can change to improve our connections. Some or a combination of all these tips might help you, if they don't, please continue to get in touch with bungie posting your errors, remember to include a list of things you've done to try and combat disconnect errors. Remember to include your platform, connection speeds, ISP, Your router's make and model and how long you've been experiencing these problems. If it's less than 24 hours and there was no update from bungie that could've caused the connection issues, please check downdetector.net in case there is a known fault in your area through your ISP or console services. First thing you'll need to look at, is are you connected to a hub [b]wired[/b] or [b]wireless[/b]. If it's wireless please skip further down this post before trying the tips under wired connection. [b]Wired Connection:[/b] The only two main things you can try here are opening your ports on your router, and changing your DNS settings. To open your ports please follow the link to this article posted by bungie which gives a list of the TCP and UDP ports you will need to change depending on which console you are using. To find out how to change the ports on your specific router please Google how to and the router name. [url=https://www.bungie.net/en/Help/Article/11931] https://www.bungie.net/en/Help/Article/11931[/url] You can also try setting your console into DMZ mode, this will open up the routers firewall on your console. This does mean that you will have no protection on your console from outside attacks, but it can also prevent the firewall from blocking any traffic that might have been solicit in the first place. You will still need to open up the ports to fully take advantage of this mode, and you will need to set your console to a Static IP address. Again take a Google look at how you would need to do this on your particular router. [b]Please note that port forwarding won't work with two of the exact same consoles using the same router, you'll need to make sure your router supports UPnP and is switched on. [/b] Please take a look online for how to do that on your specific router. Also note that a lot of cheap routers still won't function properly with two consoles on them still, in which case either use third party firmware for your router, or buy a new router which people have recommended online that worked for them who had similar NAT restrictions and losing connections. [b]The last tip you can try (MAKE SURE YOU READ YOUR IP'S TERMS AND CONDITIONS IF YOU HAVE DATA CAP PLANS OR BUNDLED SUPSCRIPTIONS)[/b]is to change your DNS (Domain Name System) settings. This can be done by setting up your network settings on your console manually. Keep all other settings automatically until you reach DNS which will look something like this: Primary DNS: 62.6.40.178 Secondary DNS: 62.6.40.162 Keep a note of these numbers on your console before changing them in case you need to revert back and the auto set up doesn't change these values. [b]Write them down exactly as you see them[/b], but not the above, as that's the DNS settings used by BT broadband users in the UK. To understand why this might help I'll quickly explain here... DNS are used to translate domain names into ip addresses and vice versa. If a particular server is unable to make the translation it goes and asks another. Most IPs servers don't care how far in the world that next server they ask is. Also, if your DNS means you're connecting to a server over 200 miles away, then just maybe an open DNS might be quicker based purely on geographically it might only be 40 miles away instead! Google is a good place to start as their servers will try and communicate with the closest servers available to them by default. Try looking for country specific open DNS servers as well. You can use a benchmark tool to find the fastest one by running a program called [b]namebench[/b]. To use Google public DNS servers change the values to Primary DNS: 8.8.8.8 Secondary DNS: 8.8.4.4 There are other options out there, but make sure you do some research into this before blindly following the instructions of a stranger like me! Do a speed test as well after making any changes to see if there are any drastic changes, for better or worse! [b]Wireless Connection:[/b] There can be a number of reasons you experience poor connections to your router, the best way to find if it is a wireless issue is to run a speed test, then rerun the speed test from a device after you've plugged it in via an ethernet cable. If there is a large difference from the wireless and the wired connection then there's something causing interference n the air tonight! Getting closer to your router might not be the solution here unless you're situated several walls/floors away. Also a speed test with your console touching your router but connected wirelessly won't give you a true top speed test either! If the speeds [b]aren't[/b] much different, and even while plugged in you still get connection issues, please scroll up and try the wired connection tips out. You can go back to connecting wirelessly now. If the speeds [b]are[/b] quite different or you no longer experience any connection issues while connected via ethernet cable, then it might be worth you either [b]a)[/b] Buy a long ethernet cat 5e or cat 6 cable and use a hard wired connection from now on, or [b]b)[/b] Buy a homeplug network system, which I had to do due to all of the issues I'll list below. [b]If you want to clear the air of WiFi interference[/b], you might want to try these following things. Check the number of devices connected to your hub. Some cheap hubs can only keep up to 4 to 8 devices on the DHCP table (this is like your routers address book on the devices that last connected to it) and sometimes a hub may intermittently lose connection with your console. To make sure it's not this, delete a couple of devices from the hub. Don't worry, you can still connect them to the hub again after, they just usually get given a new IP address. More modern and midrange plus hubs now have an infinite DHCP table. Another good house keeping tool for those with dual band routers (2.4ghz and 5ghz) is to make sure most of your devices that can connect via 5ghz, are, and leave some on the 2.4ghz connection. This will prevent certain devices clashing signals. I have 4 people in my house, 2 laptops, 2 desktops, 4 mobile phones, 4 tablets, a sky box and a smart tv all competing with getting information to and from the hub wirelessly. Not to mention what my two closest neighbours might have. Another useful wireless tip, primarily for those on the 2.4ghz channel, is to check the area for other routers. There are only 3 main channels routers use which are far enough away from other channels so as to not clash with other signals, these are Channels 1, 6 and 11. (It's important to use these channels only as your router will use the next 2 channels either side of what is selected as well. Otherwise you'll cause problems not just for someone else, but yourself) To see what other traffic is in your area, either use a computer with wireless and use a program called inSSider (the free one) or another alternative wireless channel tracker. Or use a phone or tablet and download a free app which will do the same. If there is other routers on the same channel as you nearby, change your router's channel manually. You can change the channel on 5ghz if need be if you live in a built up hub heavy area, usually up to channel 48 or 64 depending on your hub. Hopefully the above may help some of you, it never hurts to try. If it doesn't, don't forget to mention in your posts you've tried these options and still no avail. Sometimes the problems can lie with your Internet provider (IP) or with the gaming server your console has connected to! In which case nothing you do will change this. (apart from switching IPs and or console of course!) [b]If there are any experts reading this and wish too add any input, ideas or notice something I've stated here is wrong. Please feel free to either message me privately or post here for me to read! Thank you all![/b] If any of the above hasn't helped, then try and do some research into your router you have. Most routers provided by your ISPs are pretty useless at dealing with anything other than light use. I speak from experience from using the bt home hub 2 and home hub 3. Comcast also provide a rubbish router and just as rubbish customer service as BT, based on Web chatter. It might be worth investing in a decent router that can support dual band WiFi at its very least if you plan to use the WiFi option. Have a look at multiple websites reviewing routers to get an idea of the cheapest OK routers, to the top of the range for those with a big enough budget to get some hardware that won't let them down!

Публикуется на языке:

 

Играйте достойно. Потратьте минутку на ознакомление с нашими правилами, прежде чем отправлять вашу запись. Отмена Изменить Создать боевую группу Опубликовать

Смотреть всю тему
У вас нет прав для просмотра этих материалов.
;
preload icon
preload icon
preload icon