Hey guys,
I'm seeing something very similar to this guy 2 years ago: https://www.reddit.com/r/xboxone/comments/3f6p6f/is_anyone_having_trouble_getting_online_games_to/
We have 3 Xbox One consoles in the house (Original, Xbox One X, Xbox One S) and all 3 exhibit this behaviour. We're unable to play online games for more than a few minutes before the connection dropping out, same goes for chat.
We have 100/40 Fibre to the Premises and no other devices in the house experience any latency/dropout issues.
When I try to ping any of the 3 consoles, I get what you would expect; nice healthy replies:
ping 10.1.5.177
PING 10.1.5.177 (10.1.5.177): 56 data bytes 64 bytes from 10.1.5.177: icmp_seq=0 ttl=128 time=1.834 ms 64 bytes from 10.1.5.177: icmp_seq=1 ttl=128 time=1.978 ms 64 bytes from 10.1.5.177: icmp_seq=2 ttl=128 time=5.040 ms 64 bytes from 10.1.5.177: icmp_seq=3 ttl=128 time=2.015 ms 64 bytes from 10.1.5.177: icmp_seq=4 ttl=128 time=1.865 ms 64 bytes from 10.1.5.177: icmp_seq=5 ttl=128 time=2.456 ms 64 bytes from 10.1.5.177: icmp_seq=6 ttl=128 time=1.687 ms 64 bytes from 10.1.5.177: icmp_seq=7 ttl=128 time=4.870 ms 64 bytes from 10.1.5.177: icmp_seq=8 ttl=128 time=1.661 ms 64 bytes from 10.1.5.177: icmp_seq=9 ttl=128 time=1.791 ms 64 bytes from 10.1.5.177: icmp_seq=10 ttl=128 time=2.213 ms 64 bytes from 10.1.5.177: icmp_seq=11 ttl=128 time=1.934 ms 64 bytes from 10.1.5.177: icmp_seq=12 ttl=128 time=1.724 ms 64 bytes from 10.1.5.177: icmp_seq=13 ttl=128 time=2.720 ms 64 bytes from 10.1.5.177: icmp_seq=14 ttl=128 time=1.538 ms 64 bytes from 10.1.5.177: icmp_seq=15 ttl=128 time=2.020 ms 64 bytes from 10.1.5.177: icmp_seq=16 ttl=128 time=1.915 ms 64 bytes from 10.1.5.177: icmp_seq=17 ttl=128 time=1.647 ms 64 bytes from 10.1.5.177: icmp_seq=18 ttl=128 time=1.878 ms 64 bytes from 10.1.5.177: icmp_seq=19 ttl=128 time=1.650 ms 64 bytes from 10.1.5.177: icmp_seq=20 ttl=128 time=1.561 ms 64 bytes from 10.1.5.177: icmp_seq=21 ttl=128 time=2.400 ms 64 bytes from 10.1.5.177: icmp_seq=22 ttl=128 time=1.719 ms 64 bytes from 10.1.5.177: icmp_seq=23 ttl=128 time=1.818 ms 64 bytes from 10.1.5.177: icmp_seq=24 ttl=128 time=2.136 ms 64 bytes from 10.1.5.177: icmp_seq=25 ttl=128 time=1.710 ms
Until I launch a game, then things get interesting:
64 bytes from 10.1.5.177: icmp_seq=114 ttl=128 time=2.046 ms 64 bytes from 10.1.5.177: icmp_seq=39 ttl=128 time=75259.934 ms (DUP!) 64 bytes from 10.1.5.177: icmp_seq=115 ttl=128 time=4.370 ms 64 bytes from 10.1.5.177: icmp_seq=115 ttl=128 time=4.595 ms (DUP!) 64 bytes from 10.1.5.177: icmp_seq=116 ttl=128 time=5.452 ms 64 bytes from 10.1.5.177: icmp_seq=116 ttl=128 time=5.652 ms (DUP!) 64 bytes from 10.1.5.177: icmp_seq=117 ttl=128 time=4.380 ms 64 bytes from 10.1.5.177: icmp_seq=118 ttl=128 time=4.642 ms 64 bytes from 10.1.5.177: icmp_seq=118 ttl=128 time=4.847 ms (DUP!) 64 bytes from 10.1.5.177: icmp_seq=119 ttl=128 time=4.475 ms 64 bytes from 10.1.5.177: icmp_seq=119 ttl=128 time=4.581 ms (DUP!) 64 bytes from 10.1.5.177: icmp_seq=120 ttl=128 time=1.699 ms 64 bytes from 10.1.5.177: icmp_seq=120 ttl=128 time=2.276 ms (DUP!) 64 bytes from 10.1.5.177: icmp_seq=121 ttl=128 time=1.795 ms 64 bytes from 10.1.5.177: icmp_seq=121 ttl=128 time=1.965 ms (DUP!) 64 bytes from 10.1.5.177: icmp_seq=122 ttl=128 time=2.530 ms 64 bytes from 10.1.5.177: icmp_seq=122 ttl=128 time=3.103 ms (DUP!) 64 bytes from 10.1.5.177: icmp_seq=123 ttl=128 time=1.611 ms 64 bytes from 10.1.5.177: icmp_seq=123 ttl=128 time=1.789 ms (DUP!)
Not so healthy there. Then, if I go back to the dashboard and quit the game (actually quit it from the xbox menu), everything returns to normal:
64 bytes from 10.1.5.177: icmp_seq=139 ttl=128 time=4.544 ms (DUP!) 64 bytes from 10.1.5.177: icmp_seq=140 ttl=128 time=4.591 ms 64 bytes from 10.1.5.177: icmp_seq=141 ttl=128 time=4.617 ms 64 bytes from 10.1.5.177: icmp_seq=142 ttl=128 time=4.945 ms 64 bytes from 10.1.5.177: icmp_seq=143 ttl=128 time=4.860 ms 64 bytes from 10.1.5.177: icmp_seq=144 ttl=128 time=2.200 ms
All 3 Xboxes connected via Ethernet, connecting to 3 different switches in different locations of the house (we have 6 switches in total, it's a pretty big network). I've tried cutting them over to Wi-Fi, disconnecting all of the switches down to one and trying that, using a different switch for the isolation test, and I can replicate this issue every single time so the switches don't seem to be the issue in this case.
Some research online points to check the MTU but that's irrelevant on the local network (all of our switches are smart switches and are set to the standard 1500 MTU).
This has only cropped up very recently, and nothing else on the network is experiencing this, only the Xbox One consoles. I noticed there was a Dashboard update released on 17/02, not sure if that might have anything to do with it but it's worth mentioning.
Wireshark shows these duplicate replies as both coming from the same console, and we've changed the IP of one of the consoles so it definitely isn't duplicated.
Not sure what to do here guys, though maybe /u/Xbox_Support or someone in-the-know can offer some insight?
Submitted by carp3tguy | #Specialdealer Special Offer Online Shopping Store 2016
No comments:
Post a Comment