Menu
Reply
  • 4
  • 0
  • 0
jarryd
Joining in
360 Views
Message 1 of 5
Flag for a moderator

Packet loss and rubber-banding/disconnects Xbox One in N1

Hey all,

Looks like there's an issue in my area (N1) based on similar threads (https://community.virginmedia.com/t5/Gaming-Support/Steps-to-fix-Area-15-issue-Packet-loss/td-p/3905...) so just posting my specific problems for brevity.

Online gaming through Xbox One and Xbox One X – The Division seems to have better tolerance than Destiny 2 for online play. The Division rubber-bands and then disconnects, on average, every 30 minutes. With Destiny 2 I'm lucky if I can log in at all or play for even 5 minutes.

I've done the works:

  • Static IP address + forwarded ports
  • Disabled and re-enabled UPnP
  • Placed Xbox in DMZ
  • Hard reset and power cycle both console and Hub 3.0
  • Always been ethernet connection from console to router
  • Factory reset of Hub 3.0
  • Changed DNS from default to Cloudflare and also Google.

Called phone support and they recommended a factory reset after getting me to test my connection speed on speedtest.net, which I had already done.

Tests on the console show packet loss between 17-40%.

My Broadband Ping - Virgin Media VIVID Gaming 200 Optical Fibre

I'm not savvy with network engineering so hopefully these diagnostics on the Hub 3.0 make more sense to someone else!

Cable Modem Status
ItemStatusComments
Acquired Downstream Channel (Hz)
299000000
Locked
Ranged Upstream Channel (Hz)
60300000
Locked
Provisioning State
Online
 

 

0 Kudos
Reply
  • 4
  • 0
  • 0
jarryd
Joining in
358 Views
Message 2 of 5
Flag for a moderator

Re: Packet loss and rubber-banding/disconnects Xbox One in N1

Downstream bonded channels

ChannelFrequency (Hz)Power (dBmV)SNR (dB)ModulationChannel ID
12990000003.237256 qam21
23230000002.237256 qam24
33150000002.237256 qam23
43070000002.737256 qam22
5291000000337256 qam20
6283000000337256 qam19
72750000002.737256 qam18
82670000002.737256 qam17
92590000002.537256 qam16
102510000002.237256 qam15
112430000002.237256 qam14
122350000002.237256 qam13
132270000002.237256 qam12
142190000002.437256 qam11
152110000002.437256 qam10
162030000002.237256 qam9
171950000002.237256 qam8
181870000002.537256 qam7
191790000002.537256 qam6
201710000002.537256 qam5
211630000002.537256 qam4
221550000002.537256 qam3
231470000002.737256 qam2
241390000002.536256 qam1

 

ChannelLocked StatusRxMER (dB)Pre RS ErrorsPost RS Errors
1Locked37.350
2Locked37.3170
3Locked37.6120
4Locked37.6220
5Locked37.6110
6Locked37.6170
7Locked37.6130
8Locked37.6200
9Locked37.6120
10Locked37.680
11Locked37.6130
12Locked37.680
13Locked37.6130
14Locked37.6150
15Locked37.3130
16Locked37.6320
17Locked37.3290
18Locked37.3250
19Locked37.3310
20Locked37.3430
21Locked37.3410
22Locked37.3260
23Locked37.3230
24Locked36.6360

 

Upstream bonded channels

ChannelFrequency (Hz)Power (dBmV)Symbol Rate (ksps)ModulationChannel ID
16030000049512064 qam1
23940000048512064 qam4
35370000048.5512064 qam2
44620000048.3512064 qam3

 

ChannelChannel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
1ATDMA0030
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

General configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file 

 

Primary Downstream Service Flow

SFID62394
Max Traffic Rate230100000
Max Traffic Burst42600
Min Traffic Rate0

 

Primary Upstream Service Flow

SFID62393
Max Traffic Rate22000000
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst16320
Scheduling TypeBestEffort

 

Network Log

TimePriorityDescription
2018-12-13 00:47:14.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2018-12-15 02:34:57.00criticalNo Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2018-12-16 18:18:20.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2018-12-17 18:43:14.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2018-12-19 17:33:36.00criticalNo Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2018-12-21 17:38:27.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2018-12-22 19:31:45.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2018-12-22 23:51:52.00criticalNo Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2018-12-28 06:41:42.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2018-12-31 02:22:45.00criticalNo Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2019-01-01 16:37:03.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2019-01-01 18:41:40.00criticalNo Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2019-01-02 02:05:26.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2019-01-02 05:00:37.00criticalNo Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2019-01-02 06:49:38.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2019-01-02 11:33:55.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
2019-01-02 13:36:09.00criticalNo Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:30.00Warning!Lost MDD Timeout;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:30.00Warning!MDD message timeout;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:44.00criticalNo Ranging Response received - T3 time-out;CM-MAC=redacted;CMTS-MAC=redacted;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 4
  • 0
  • 0
jarryd
Joining in
353 Views
Message 3 of 5
Flag for a moderator

Re: Packet loss and rubber-banding/disconnects Xbox One in N1

Some extra information

Traceroute for fast.com:

traceroute to fast.com (104.127.31.168), 64 hops max, 72 byte packets
 1  192.168.0.1 (192.168.0.1)  3.958 ms  3.109 ms  2.608 ms
 2  * * *
 3  hari-core-2b-xe-322-0.network.virginmedia.net (62.252.114.117)  13.975 ms  12.932 ms  14.447 ms
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  tcma-ic-2-ae9-0.network.virginmedia.net (62.253.174.178)  27.514 ms  20.341 ms  18.007 ms
 9  * tele-ic-2-ge-408-0.network.virginmedia.net (212.250.14.98)  2570.878 ms  689.286 ms
10  a104-127-31-168.deploy.static.akamaitechnologies.com (104.127.31.168)  26.275 ms  18.804 ms  27.934 ms
0 Kudos
Reply
  • 4
  • 0
  • 0
jarryd
Joining in
301 Views
Message 4 of 5
Flag for a moderator

Re: Packet loss and rubber-banding/disconnects Xbox One in N1

Latest graph...

My Broadband Ping - Virgin Media VIVID Gaming 200 Optical Fibre

0 Kudos
Reply
  • 12.78K
  • 573
  • 2.03K
Forum Team
Forum Team
240 Views
Message 5 of 5
Flag for a moderator
Helpful Answer

Re: Packet loss and rubber-banding/disconnects Xbox One in N1

Hi jarryd

I appreciate you getting in touch regarding this.

Our Network teams were made aware that this issue was possibly affecting some customers and have been working to resolve this.

This issue should be rectified now so please let us know if you are still affected and we can look into this on an individual basis.

Kindest regards.

Karen


Forum Team

Need a helpful hand to show you how to make a payment? Check out our guide - "How to pay my Virgin Media bill"

0 Kudos
Reply