Menu
Reply
  • 5
  • 0
  • 1
koya
Tuning in
349 Views
Message 1 of 8
Flag for a moderator

More WoW disconnects.

Had the problem last weekend, but after resetting the superhub three times and opening some ports it seemed to work itself out.

 

However, boyfriend and I are having the same problem this week. Disconnecting every few minutes from WoW but internet and TV are fine.

 

Yesterday, in addition to power cyclinging the superhub I also did a DNS flush. This seemed to sort out the issue for a while, but it's back with a vengeance today.

 

Wall of information follows.

 

Downstream        

                                       DS-1              DS-2            DS-3          DS-4           DS-5           DS-6           DS-7            DS-8

Frequency (Hz)435000000427000000443000000451000000459000000467000000475000000483000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock)LockedLockedLockedLockedLockedLockedLockedLocked
Channel ID5251535455565758
Modulation256QAM256QAM256QAM256QAM256QAM256QAM256QAM256QAM
Symbol Rate (Msym/sec)6.9520006.9520006.9520006.9520006.9520006.9520006.9520006.952000
Interleave DepthI=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
I=12
J=17
Power Level (dBmV)-3.34-3.20-3.46-3.27-3.26-3.35-3.43-3.56
RxMER (dB)37.9437.6437.3637.6438.2638.2636.3938.26
Pre RS Errors306337282987946304966942
Post RS Errors296289281987945304966942

 

Upstream              US-1      US-2      US-3         US-4

Channel TypeN/AN/A2.02.0
Channel IDN/AN/A58
Frequency (Hz)N/AN/A4620000025800000
Ranging StatusOtherOtherSuccessSuccess
ModulationN/AN/A16QAM16QAM
Symbol Rate (Sym/sec)N/AN/A51200005120000
Mini-Slot SizeN/AN/A44
Power Level (dBmV)N/AN/A38.5037.00
T1 Timeouts0000
T2 Timeouts0000
T3 Timeouts0000
T4 Timeouts0000

 

Network Log

First TimeLast TimePriorityError NumberDescription
19/07/2015 09:22:29 GMT19/07/2015 09:22:29 GMTError (4)68010302DHCP WAN IP - 81.107.76.197
19/07/2015 09:21:36 GMT19/07/2015 09:21:36 GMTError (4)68000407TOD established
Time Not EstablishedTime Not EstablishedNotice (6)84000510Downstream Locked Successfully
18/07/2015 20:04:57 GMT18/07/2015 20:04:57 GMTError (4)68010302DHCP WAN IP - 81.107.76.197
18/07/2015 20:04:05 GMT18/07/2015 20:04:05 GMTError (4)68000407TOD established
Time Not EstablishedTime Not EstablishedNotice (6)84000510Downstream Locked Successfully
18/07/2015 10:44:12 GMT18/07/2015 10:44:12 GMTError (4)68010302DHCP WAN IP - 81.107.76.197
18/07/2015 10:43:36 GMT18/07/2015 10:43:36 GMTError (4)68000407TOD established
18/07/2015 10:43:15 GMT18/07/2015 10:43:15 GMTNotice (6)84000510Downstream Locked Successfully
18/07/2015 10:43:01 GMT18/07/2015 10:43:01 GMTCritical (3)82000200No Ranging Response received - T3 time-out
18/07/2015 10:42:33 GMT18/07/2015 10:42:33 GMTCritical (3)82000200No Ranging Response received - T3 time-out
18/07/2015 10:42:31 GMT18/07/2015 10:42:31 GMTCritical (3)82000200No Ranging Response received - T3 time-out
18/07/2015 10:42:26 GMT18/07/2015 10:42:26 GMTCritical (3)82000200No Ranging Response received - T3 time-out
18/07/2015 10:42:19 GMT18/07/2015 10:42:19 GMTNotice (6)84000510Downstream Locked Successfully
18/07/2015 10:41:35 GMT18/07/2015 10:41:35 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
18/07/2015 08:43:28 GMT18/07/2015 08:43:28 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
18/07/2015 04:47:13 GMT18/07/2015 04:47:13 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
17/07/2015 20:54:43 GMT17/07/2015 20:54:43 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
17/07/2015 05:09:40 GMT17/07/2015 05:09:40 GMTError (4)68010100DHCP RENEW sent - No response for IPv4
16/07/2015 10:52:33 GMT16/07/2015 10:52:33 GMTError (4)68000411TOD error 4849 msec

 

 

Blizzard lists two IP's to connect to their WoW servers:

 

Using the tracert command on the two IP's, I get the following:


Tracing route to 185.60.114.159 over a maximum of 30 hops

 1   <1 ms   <1 ms  <1 ms   routerlogin.net [192.168.0.1]
 2    7 ms    6 ms    8 ms    10.***.**.1
 3    8 ms    8 ms    7 ms    winn-core-2a-xe-1121-0.network.virginmedia.net [62.253.123.105]
 4    12 ms  9 ms    9 ms    brnt-bb-1c-ae2-0.network.virginmedia.net [62.253.96.169]
 5    * * *    Request timed out.
 6    * * *    Request timed out.
 7    * * *    Request timed out.
 8    * * *    Request timed out.
 9    * * *    Request timed out.
10    33 ms   32 ms   32 ms  ams2-ic-1-ae0-0.network.virginmedia.net [62.253.188.158]
11    34 ms   35 ms   33 ms  80.249.208.73
12    * * *    Request timed out.
13    * * *    Request timed out.
14    * * *    Request timed out.
15    * * *    Request timed out.
16    * * *    Request timed out.
17    * * *    Request timed out.
18    * * *    Request timed out.
19    * * *    Request timed out.
20    * * *    Request timed out.
21    * * *    Request timed out.
22    * * *    Request timed out.
23    * * *    Request timed out.
24    * * *    Request timed out.
25    * * *    Request timed out.
26    * * *    Request timed out.
27    * * *    Request timed out.
28    * * *    Request timed out.
29    * * *    Request timed out.
30    * * *    Request timed out.

Trace complete.

 


Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:

 1    1 ms     <1 ms     1 ms     routerlogin.net [192.168.0.1]
 2    21 ms    30 ms    20 ms    10.***.**.1
 3    22 ms    24 ms    16 ms    winn-core-2b-xe-1121-0.network.virginmedia.net [62.253.123.109]
 4    20 ms    15 ms    16 ms    brhm-bb-1c-ae2-0.network.virginmedia.net [62.253.96.173]
 5    30 ms    30 ms    25 ms    213.161.65.149
 6    21 ms    22 ms    21 ms    ldn-b5-link.telia.net [213.248.76.85]
 7    20 ms    27 ms    29 ms    ldn-bb3-link.telia.net [80.91.246.144]
 8    29 ms    33 ms    28 ms    adm-bb3-link.telia.net [62.115.134.24]
 9    41 ms    30 ms    30 ms    adm-b2-link.telia.net [62.115.141.3]
10    * * *    Request timed out.
11    * * *    Request timed out.
12    * * *    Request timed out.
13    * * *    Request timed out.
14    * * *    Request timed out.
15    * * *    Request timed out.
16    * * *    Request timed out.
17    * * *    Request timed out.
18    * * *    Request timed out.
19    * * *    Request timed out.
20    * * *    Request timed out.
21    * * *    Request timed out.
22    * * *    Request timed out.
23    * * *    Request timed out.
24    * * *    Request timed out.
25    * * *    Request timed out.
26    * * *    Request timed out.
27    * * *    Request timed out.
28    * * *    Request timed out.
29    * * *    Request timed out.
30    * * *    Request timed out.

Trace complete.

 

 

 

Using the pathping command on the two IP's, I get the following:

 

Tracing route to 185.60.114.159 over a maximum of 30 hops

 0   **-PC   [192.168.0.3]
 1   routerlogin.net [192.168.0.1]
 2   10.***.**.1
 3   winn-core-2a-xe-1121-0.network.virginmedia.net [62.253.123.105]
 4   brnt-bb-1c-ae2-0.network.virginmedia.net [62.253.96.169]
 5    *                *           *
  Computing statistics for 100 seconds...
                 Source to Here     This Node/Link
Hop  RTT   Lost/Sent = Pct    Lost/Sent = Pct      Address
 0                                                                       **-PC [192.168.0.3]
                                               0/ 100   =  0%      |
 1    3ms      0/ 100 =    0%       0/ 100   =  0%       routerlogin.net [192.168.0.1]
                                               0/ 100   =  0%      |
 2     ---      100/ 100 =100%  100/ 100   = 100%    10.***.**.1
                                               0/ 100  =   0%     |
 3   19ms      1/ 100  =   1%      1/ 100   =   1%      winn-core-2a-xe-1121-0.network.virginmedia.net [62.253.123.105]
                                               0/ 100  =   0%      |
 4   22ms      0/ 100  =   0%       0/ 100 =   0%       brnt-bb-1c-ae2-0.network.virginmedia.net [62.253.96.169]

Trace complete.

 

 

Tracing route to 213-155-155-233.customer.teliacarrier.com [213.155.155.233]
over a maximum of 30 hops:
 0   **-PC [192.168.0.3]
 1   routerlogin.net [192.168.0.1]
 2   10.***.**.1
 3   winn-core-2b-xe-1121-0.network.virginmedia.net [62.253.123.109]
 4   brhm-bb-1c-ae2-0.network.virginmedia.net [62.253.96.173]
 5   213.161.65.149
 6   ldn-b5-link.telia.net [213.248.76.85]
 7   ldn-bb3-link.telia.net [80.91.246.144]
 8   adm-bb3-link.telia.net [62.115.134.24]
 9   adm-b2-link.telia.net [62.115.141.3]
10       *           *          *
Computing statistics for 225 seconds...
                 Source to Here     This Node/Link
Hop  RTT   Lost/Sent = Pct    Lost/Sent = Pct     Address
 0                                                                     **-PC [192.168.0.3]
                                                0/ 100 = 0%      |
 1    3ms        0/ 100 = 0%         0/ 100 = 0%      routerlogin.net [192.168.0.1]           
                                                0/ 100 = 0%      |
 2     ---       100/ 100 =100%   100/ 100 =100%   10.***.**.1
                                                0/ 100 = 0%      |
 3   19ms       0/ 100 = 0%         0/ 100 = 0%       winn-core-2b-xe-1121-0.network.virginmedia.net [62.253.123.109]
                                                0/ 100 = 0%      |
 4   29ms       0/ 100 = 0%         0/ 100 = 0%       brhm-bb-1c-ae2-0.network.virginmedia.net [62.253.96.173]
                                                0/ 100 = 0%      |
 5   27ms       0/ 100 = 0%          0/ 100 = 0%     213.161.65.149
                                                0/ 100 = 0%      |
 6   29ms       0/ 100 = 0%          0/ 100 = 0%     ldn-b5-link.telia.net [213.248.76.85]
                                                 0/ 100 = 0%     |
 7   28ms       1/ 100 = 1%          1/ 100 = 1%     ldn-bb3-link.telia.net [80.91.246.144]
                                                 0/ 100 = 0%    |
 8   33ms       0/ 100 = 0%           0/ 100 = 0%   adm-bb3-link.telia.net [62.115.134.24]
                                              100/ 100 =100% |
 9     ---         100/ 100 =100%     0/ 100 = 0%    adm-b2-link.telia.net [62.115.141.3]

 

 

IP addresses sourced here: https://eu.battle.net/support/en/article/running-a-pathping-test

 

 

0 Kudos
  • 5
  • 0
  • 1
koya
Tuning in
326 Views
Message 2 of 8
Flag for a moderator

Re: More WoW disconnects.

Forgot to mention that the PC's are on a wired connection to the hub.
0 Kudos
  • 27
  • 1
  • 1
roflbeaer
On our wavelength
305 Views
Message 3 of 8
Flag for a moderator

Re: More WoW disconnects.

Leave Virgin as soon as you can.
  • 24
  • 0
  • 3
Contraband
Tuning in
297 Views
Message 4 of 8
Flag for a moderator

Re: More WoW disconnects.


roflbeaer wrote:
Leave Virgin as soon as you can.

Been a customer since way before NTL I am seriously considering this option.

0 Kudos
  • 5
  • 0
  • 1
koya
Tuning in
292 Views
Message 5 of 8
Flag for a moderator

Re: More WoW disconnects.

@roflbeaer - I've been with VM for years and even with going through four different installs due to moving house, this is the first time I've ever had problems.

Don't hijack my thread just because you are p****ed at VM; at best it's rude, at worst it's trolling.

0 Kudos
  • 14.35K
  • 640
  • 1.44K
Moderator
Moderator
262 Views
Message 6 of 8
Flag for a moderator

Re: More WoW disconnects.

Hi Koya,

 

Welcome to the forum and sorry to hear you're having trouble with WoW. Thank you for posting all the info and running all those traces. Everything looks good from the stats you've posted and I've checked from this side too to make sure. Your network segment looks healthy, low contention and stable SNR. 

The traces you've posted all return good ping times and complete with no problems. It's normal for battlenet servers to ignore ping requests which is why the last entries are all starred out. 

We've been extra vigilant on the WoW front recently as we've seen quite a few similar posts  in the last week or so but almost all of them have been connection specific so far. 

So we can try and narrow down the possible causes a little further could you try the hub in modem mode with a PC in safe mode with networking? This will eliminate the router portion of the hub, other devices on the network and any background programs on the PC as the possible culprit. 

Let us know how you get on and we'll do what we can to get this working Smiley Happy


The do's and don'ts. Keep the community welcoming for all. Follow the house rules


0 Kudos
  • 53
  • 0
  • 10
sbowesuk
Dialled in
247 Views
Message 7 of 8
Flag for a moderator

Re: More WoW disconnects.

"We've been extra vigilant on the WoW front recently as we've seen quite a few similar posts  in the last week or so but almost all of them have been connection specific so far."

 

Yeah, because innumerable gamers magically developed localised connection issues all in the exact same week, right? What a spectacular coincidence!

 

Let's not beat around the bush, most of the people reporting gaming issues here, are clearly being affected by a centralised issue, i.e. an issue with VM's network management. That's the real problem here, and it's a problem you better fix pronto, or you can wave goodbye to a myriad of your paying customers.

  • 5
  • 0
  • 1
koya
Tuning in
233 Views
Message 8 of 8
Flag for a moderator

Re: More WoW disconnects.

I am haveing less disconnects than usual at the moment, so if they go up again it will try to put the hub in modem mode.

 

Last time I tried to launch WoW in safe mode it didn't work (and yes, I was in safe mode with networking), so I will have to look into getting that to work if needed.

0 Kudos