Random disconnect/delayed login times. VoiceError: 16

Getting disconnected randomly when logging into the game. Sometimes the login attempts are delayed for over a minute, followed by the error “Cant connect to voice chat server right now. Please try again. (VoiceError: 16)”, displayed in my chat box when it eventually does login.

Sometimes there is no issue at all. But If I repeatedly log between characters it will eventually happen again. Have tried from a separate machine with a fresh install of the game, same issues. No other apparent issues when successfully logged into the game.

Just started happening yesterday, and theres no other issues I’m finding. Kind of hoping my ISP is just dealing with issues and resolves itself? but if my WinMTR thing shows other issues I need to be aware of, please help. This is really frustrating.

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                                10.0.0.1 -    0 |  306 |  306 |    0 |    0 |    1 |    0 |

|                           96.120.13.117 -   12 |  212 |  188 |    7 |    8 |   16 |    8 |

|ae-255-1276-rur102.cosprings.co.denver.comcast.net -   11 |  216 |  193 |    6 |    9 |   31 |    9 |

|ae-2-rur101.cosprings.co.denver.comcast.net -   12 |  212 |  188 |    7 |   10 |   40 |    9 |

|                          24.124.155.233 -    6 |  255 |  242 |    7 |    8 |   59 |    8 |

|                            96.216.22.45 -    3 |  274 |  266 |    6 |   12 |   59 |   10 |

|be-36021-cs02.1601milehigh.co.ibone.comcast.net -    3 |  274 |  266 |    6 |   11 |   21 |    6 |

|be-1212-cr12.1601milehigh.co.ibone.comcast.net -   11 |  216 |  193 |   10 |   11 |   20 |   10 |

| be-303-cr02.dallas.tx.ibone.comcast.net -    6 |  255 |  242 |   24 |   25 |   42 |   25 |

|be-3312-pe12.1950stemmons.tx.ibone.comcast.net -   16 |  192 |  163 |    0 |   24 |   36 |   24 |

|                          66.208.216.198 -    6 |  251 |  237 |   21 |   28 |   97 |   25 |

|              ae1-br01-eqda6.as57976.net -    9 |  227 |  207 |    0 |   42 |  148 |   38 |

|                   No response from host -  100 |   62 |    0 |    0 |    0 |    0 |    0 |

|         et-0-0-0-pe03-eqch2.as57976.net -   21 |  169 |  134 |    0 |   41 |  158 |   38 |

|                           24.105.62.129 -    5 |  259 |  247 |    0 |   39 |   48 |   40 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Hi Alrecht

This looks like the first Comcast hop outside your home network. We see 12% packet loss which seems to carry down the line of switches to Blizzard. Likely the problem is there.

Can you describe your connection. It is possible that may be the comcast modem.

Describe my connection? Uh, well. It’s just your standard comcast cable modem, it’s certainly an older router, could be the issue? Not on Wifi, direct ethernet.

Now that I think of it I did recently move a few things around and changed ethernet cables because the old one had a broken tab… maybe I need to double check cables and re-secure stuff - see if that makes any difference.

It’s very intermittent though, sometimes I log directly in… no problem. Other times it’s wonky. It wouldn’t surprise me if the modem was bad, it’s several years old.

I haven’t noticed any considerable connection issues whatsoever (aside from random ISP outages)

Try switching that cable - if you haven’t already unplug the router and or modem from wall power. Leave unplugged for 10 minutes or so - drains capacitors.

Welp, I don’t know whats happening. I tried the old cable and it was just flat out refusing to let me log in, it would stall and disconnect after the character select/waiting to enter world screen.

Unplugged the modem for another 10 minutes and put the new cable back in - and now I appear to be logging in and out successfully with no issues. I recorded another WinMTR during this time while I flipped around characters and it still shows packet loss, I don’t really know if this is fixed or just waiting to start breaking again?

I’ve watched several of my attempts logging in and it’s straight 0’s until it hits the 12 or 13th jump at “ae1-br01-eqda6.as57976.net” and then everything gets flooded with the packet loss you see below. I’ll wait and see if its better I guess.

|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

|                                10.0.0.1 -    0 |  627 |  627 |    0 |    0 |    5 |    0 |

|                           96.120.13.117 -   10 |  458 |  415 |    7 |    8 |   24 |    8 |

|ae-255-1276-rur102.cosprings.co.denver.comcast.net -    3 |  576 |  562 |    7 |    9 |   36 |    9 |

|ae-2-rur101.cosprings.co.denver.comcast.net -   10 |  458 |  415 |    8 |   10 |   50 |    8 |

|                          24.124.155.233 -    6 |  509 |  479 |    7 |    8 |   22 |    8 |

|                            96.216.22.45 -   10 |  458 |  415 |    9 |   12 |   48 |   10 |

|be-36021-cs02.1601milehigh.co.ibone.comcast.net -    6 |  509 |  479 |   10 |   11 |   39 |   10 |

|be-1212-cr12.1601milehigh.co.ibone.comcast.net -    9 |  478 |  439 |   10 |   11 |   27 |   12 |

| be-303-cr02.dallas.tx.ibone.comcast.net -    3 |  564 |  548 |   23 |   25 |   50 |   25 |

|be-3312-pe12.1950stemmons.tx.ibone.comcast.net -    6 |  517 |  489 |   24 |   25 |   64 |   25 |

|                          66.208.216.198 -    6 |  513 |  483 |   23 |   28 |  129 |   25 |

|              ae1-br01-eqda6.as57976.net -   14 |  415 |  361 |    0 |   42 |  113 |   39 |

|                   No response from host -  100 |  128 |    0 |    0 |    0 |    0 |    0 |

|         et-0-0-0-pe03-eqch2.as57976.net -   14 |  411 |  356 |    0 |   41 |  138 |   39 |

|                           24.105.62.129 -   19 |  364 |  296 |    0 |   39 |   55 |   39 |

|________________________________________________|______|______|______|______|______|______|

   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

VoiceError: 16 is telling you that WowVoiceProxy.exe is not running. if you don’t use that (i have it renamed to WowVoiceProxy.exe.bak) then you can safely ignore the error…

I didn’t know you could simply rename that Eel. Are you sure the Launcher isn’t installing a new one.

We still see that packet loss Aldrecht - it sure looks real. Let’s see if we can update your Ethernet adapter. Can you create a DXDiag system report.

The second section of page has DXDiag report instructions - we don’t require the MSinfo report.

That will be a wall of text. If you have issues pasting on the Forum here go ahead and put it up on pastebin.com. Provide the link code portion of the URL - example below.

(The green bold portion at the end of this example link: https://pastebin.com/Qk28Ed1P <=== this code)

Alternately you can place the link in a Preformatted Text box. Paste the link in the chatbox - then highlight it. Click the preformatted text button along the top of the chatbox - looks like this </>

Will look like this example afterwards:

https://pastebin.com/xxxxxxxx

the launcher will make a new WowVoiceProxy.exe file but keeps the renamed file. i only use the launcher if there’s an update to the game files. i use Wow.exe (shortcut) from the retail folder to bypass the launcher …

Driver Booster from iobit will find the latest drivers for your computer …