NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
NUKLRSOLDR
Dec 14, 2014Guide
Xbox one best settings?
Bottom line up front: I am in search of the settings that provide the best online experience specifically for Advanced Warfare (single xbox setup). I.E. provide the lowest latency experience. No I...
- Nov 07, 2015So with Black ops 3 coming out I wanted to make sure I was going to get the best experience that I could.
I did a lot of sole searching and research made the changes and did a proper reboot. So far my online experience is awesome and is like night and day compared to playing advanced warfare. I'm not sure if Black Ops 3 is the only reason or not but I will detail below what is currently working great for me.
On my modem (standard Xfinity modem/router with the 90/15 gb plan) I turned off the firewall completely and set to bridge mode. Then plugged my router into it. For the modem settings for me it was 10.0.0.1 and default username and password (admin and I can't remember PW but you can google it if you have Comcast.
On the nighthawk.
I updated the firmware.
Updated my time zone in the security menu.
Changed the DHCP reservation range to a max of .100
Setup Xbox with a reserved ip (static ip) of .150 (well outside the range of the reserved ips)
Setup port forwarding to the Xbox with
TCP: 80
UDP: 88, 500, 3544, 4500
Both: 53, 3074-3075, 3076, 1863, 16000
I left upnp on
Disabled SIP and set to open
Turned on upstream qos and used the built in speed test to set upload bandwidth.
Edited all default rules with a highest priority and changed to a high priority.
Changed the default Xbox priority from high to highest.
And set up a custom rule to my Xbox MAC address with highest priority.
On the Xbox:
I turned off Kinect and DVR
Left network ip settings to get automatically
But set dns manually (I use 8.8.8.8 and 8.8.4.4)
On my TV:
Game mode on
All reductions and motion smoothing off.
If you have the option choose refresh rate as close to 60 hz as possible
Proper reboot after all settings changed:
Unplug router
Then unplug modem
Then fully turn off Xbox (hold power button until it turns off)
Wait 1 minute then turn on Xbox
After Xbox is on wait at least 5 minutes before plugging in modem.
Wait for modem to fully turn on
Then plug in router and wait for it to fully turn on
Once Xbox connects to XBL go to network settings and run multiplayer test. After test hold all triggers and bumpers until the next screen pops up.
Some of this may not matter but it's what I did and knock on wood I continue to have an amazing experience as I have had so far with black ops 3.
NUKLRSOLDR
Dec 19, 2014Guide
New Update important!
Although everything worked like a dream at first i kept running into more and more issues.
I checked the router log and saw many many unusual ports being opened to the xbox one (192.168.1.8) ports that are not used by xbox live.LAN access from remote] from 61.160.224.130:38426 to 192.168.1.8:32764, Friday, Dec 19,2014 09:34:47
[LAN access from remote] from 151.236.42.10:12861 to 192.168.1.8:5631, Friday, Dec 19,2014 09:32:38
[LAN access from remote] from 61.160.224.129:60069 to 192.168.1.8:8080, Friday, Dec 19,2014 09:31:26
[LAN access from remote] from 122.225.97.91:6000 to 192.168.1.8:22, Friday, Dec 19,2014 09:26:25
[LAN access from remote] from 162.253.128.163:13614 to 192.168.1.8:23011, Friday, Dec 19,2014 09:24:10
[LAN access from remote] from 192.210.233.162:33171 to 192.168.1.8:1900, Friday, Dec 19,2014 09:22:12
[LAN access from remote] from 60.173.11.195:6000 to 192.168.1.8:9064, Friday, Dec 19,2014 09:16:52
[LAN access from remote] from 195.64.208.167:29873 to 192.168.1.8:23011, Friday, Dec 19,2014 09:14:46
[LAN access from remote] from 218.77.79.43:54421 to 192.168.1.8:3389, Friday, Dec 19,2014 09:14:37
[LAN access from remote] from 89.46.100.25:54955 to 192.168.1.8:9064, Friday, Dec 19,2014 09:13:23
[LAN access from remote] from 222.244.215.213:55247 to 192.168.1.8:23, Friday, Dec 19,2014 09:12:26
[LAN access from remote] from 112.85.42.106:52982 to 192.168.1.8:9064, Friday, Dec 19,2014 09:10:40
[LAN access from remote] from 162.253.129.202:13614 to 192.168.1.8:23011, Friday, Dec 19,2014 09:09:30
[LAN access from remote] from 60.173.11.195:6000 to 192.168.1.8:9064, Friday, Dec 19,2014 09:07:09
[LAN access from remote] from 93.174.93.106:53672 to 192.168.1.8:143, Friday, Dec 19,2014 09:05:46
[LAN access from remote] from 107.160.10.74:46557 to 192.168.1.8:3128, Friday, Dec 19,2014 09:05:34
[LAN access from remote] from 89.99.0.16:57430 to 192.168.1.8:23011, Friday, Dec 19,2014 09:03:40
[LAN access from remote] from 121.125.71.200:9090 to 192.168.1.8:22, Friday, Dec 19,2014 09:02:52
[LAN access from remote] from 63.141.246.107:12200 to 192.168.1.8:9064, Friday, Dec 19,2014 09:00:45
[LAN access from remote] from 66.240.236.119:22552 to 192.168.1.8:1234, Friday, Dec 19,2014 09:00:16
[LAN access from remote] from 93.174.93.106:53672 to 192.168.1.8:22, Friday, Dec 19,2014 08:59:18
[LAN access from remote] from 184.75.211.244:13614 to 192.168.1.8:23011, Friday, Dec 19,2014 08:58:34
[LAN access from remote] from 189.68.182.204:6881 to 192.168.1.8:23011, Friday, Dec 19,2014 08:52:39
[LAN access from remote] from 218.77.79.38:34876 to 192.168.1.8:3306, Friday, Dec 19,2014 08:52:03
[LAN access from remote] from 60.173.10.166:6000 to 192.168.1.8:9064, Friday, Dec 19,2014 08:50:55
[LAN access from remote] from 218.150.191.216:1548 to 192.168.1.8:53413, Friday, Dec 19,2014 08:49:23
[LAN access from remote] from 50.56.25.41:2900 to 192.168.1.8:445, Friday, Dec 19,2014 08:47:46
[LAN access from remote] from 122.225.109.202:6000 to 192.168.1.8:22, Friday, Dec 19,2014 08:44:02
[LAN access from remote] from 60.173.11.227:6000 to 192.168.1.8:9064, Friday, Dec 19,2014 08:41:44
[Time synchronized with NTP server] Friday, Dec 19,2014 08:41:31
[Internet connected] IP address: 98.124.111.89, Friday, Dec 19,2014 08:41:26
[LAN access from remote] from 95.31.167.239:11660 to 192.168.1.8:23011, Friday, Dec 19,2014 08:38:35
[LAN access from remote] from 108.61.126.52:2536 to 192.168.1.8:3389, Friday, Dec 19,2014 08:36:31
[LAN access from remote] from 203.50.20.254:53 to 192.168.1.8:12883, Friday, Dec 19,2014 08:36:14
[LAN access from remote] from 186.89.118.198:2780 to 192.168.1.8:445, Friday, Dec 19,2014 08:35:25
[LAN access from remote] from 122.225.109.115:6000 to 192.168.1.8:22, Friday, Dec 19,2014 08:34:56
[LAN access from remote] from 115.186.104.244:4973 to 192.168.1.8:445, Friday, Dec 19,2014 08:34:46
[LAN access from remote] from 23.94.149.242:42700 to 192.168.1.8:80, Friday, Dec 19,2014 08:34:22
[LAN access from remote] from 137.63.74.210:13614 to 192.168.1.8:23011, Friday, Dec 19,2014 08:33:21
[LAN access from remote] from 212.57.16.98:38793 to 192.168.1.8:8080, Friday, Dec 19,2014 08:24:55
[LAN access from remote] from 162.219.179.100:13614 to 192.168.1.8:23011, Friday, Dec 19,2014 08:23:16
[LAN access from remote] from 89.46.100.25:32864 to 192.168.1.8:9064, Friday, Dec 19,2014 08:21:42
[LAN access from remote] from 61.174.50.188:6000 to 192.168.1.8:22, Friday, Dec 19,2014 08:18:56
[LAN access from remote] from 61.160.224.129:34626 to 192.168.1.8:3389, Friday, Dec 19,2014 08:18:41
[LAN access from remote] from 203.191.150.102:5498 to 192.168.1.8:3389, Friday, Dec 19,2014 08:17:00
This went on for quite some time, And I believe it may have been what was causing me problems.
there is another thread for the r7000 about unauthorized access, and it appears that this problem may extend beyond using DMZ.
I am not sure but until more is known, I do not suggest using the settings that I suggested for WAN settings, UPnP, etc.