Constant DC

Support Technical Support
1

Hello, I am posting here for my friend as he now can’t use any blizzard services without disconnecting which means he can’t open a ticket.
When he launches WoW from the battle.net launcher, he will disconnect within 15 seconds or disconnect on the loading screen that follows selecting a character.
He says he has done everything in the troubleshooting thing but nothing has worked. When he disconnects, he gets the WOW51300319 error.

Is there anything he can do?

Thanks.

2

Do they happen you have a Killer Network Adapter? If so, can you try the following:
Open Killer Control Center (can be done from windows search)
Click the settings cogwheel in the bottom left
Disable Advanced Stream Detect
Retest


Lets also run a winMTR please

WinMTR

  1. Download WinMTR
  2. Extract the contents of the .zip file to your desktop.
  3. Open the WinMTR folder, then open the folder that matches your version of Windows (32-bit or 64-bit) and run WinMTR.exe.
  4. Enter the IP address you want to test in the Host field. Select a game from the dropdown below for a list of IP addresses.
    Note : If multiple IPs are listed, run a WinMTR test for each IP address.
  5. Click Start , then launch the game you’re testing. If no connection issue is found in the first 5 minutes, restart the test.
  6. When a connection error occurs, play for at least 5 more minutes, then click Stop in WinMTR.
  7. Click " Export Text " and save the .txt file to your desktop. Name this file WinMTR.
  8. open the file above select all copy and past to this thread
    You can include the WinMTR in a reply to the forum post. Place it between rows of ticks (`) for formatting:

```
Like this.

```

The Americas
137.221.105.2 (US West)
24.105.62.129 (US Central)
Oceania
103.4.115.248

3 
WinMTR US West 
|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

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

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

|                             192.168.0.1 -   18 |  202 |  167 |    0 |    3 |   20 |    2 |

|                         142.254.236.137 -   21 |  186 |  147 |    0 |   11 |   27 |   21 |

|          agg60.pldlcabl01h.socal.rr.com -   21 |  186 |  147 |    0 |   13 |   30 |   21 |

|          agg33.lsancarc01r.socal.rr.com -   20 |  190 |  152 |    0 |   18 |   42 |   32 |

|bu-ether16.lsancarc0yw-bcr00.tbone.rr.com -   18 |  202 |  167 |    0 |   18 |   41 |   27 |

|bu-ether45.chctilwc00w-bcr00.tbone.rr.com -   20 |  194 |  157 |    0 |   21 |   38 |   32 |

|            0.ae2.pr1.lax10.tbone.rr.com -   19 |  198 |  162 |    0 |   18 |   67 |   27 |

|                            66.109.9.161 -   20 |  190 |  152 |    0 |   18 |   46 |   32 |

|              ae1-br01-eqla1.as57976.net -   19 |  198 |  162 |    0 |   29 |  193 |   27 |

|        et-0-0-2-br01-swlv10.as57976.net -   20 |  194 |  157 |    0 |   25 |   98 |   26 |

|       et-0-0-31-pe02-swlv10.as57976.net -   20 |  190 |  152 |    0 |   22 |   41 |   30 |

|                           137.221.105.2 -   20 |  190 |  152 |    0 |   22 |   46 |   25 |

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

WinMTR US Central
|------------------------------------------------------------------------------------------|

|                                      WinMTR statistics                                   |

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

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

|                             192.168.0.1 -   24 |  258 |  198 |    1 |    3 |   31 |    3 |

|           Destination host unreachable. -   26 |  250 |  186 |    9 |   12 |   36 |   12 |

|          agg60.pldlcabl01h.socal.rr.com -   24 |  258 |  198 |   11 |   14 |   40 |   15 |

|          agg33.lsancarc01r.socal.rr.com -   25 |  250 |  188 |   12 |   18 |   39 |   20 |

|           Destination host unreachable. -   25 |  262 |  198 |   12 |   19 |   44 |   19 |

|bu-ether45.chctilwc00w-bcr00.tbone.rr.com -   26 |  246 |  183 |   15 |   20 |   47 |   20 |

|            0.ae3.pr1.lax10.tbone.rr.com -   24 |  258 |  198 |   13 |   18 |   73 |   15 |

|                            66.109.9.161 -   25 |  254 |  193 |   13 |   18 |   45 |   15 |

|              ae1-br01-eqla1.as57976.net -   25 |  254 |  193 |   56 |   64 |  129 |   89 |

|        et-0-0-2-br01-swlv10.as57976.net -   24 |  258 |  198 |   56 |   63 |  142 |   59 |

|                          137.221.65.133 -   25 |  254 |  193 |   61 |   73 |  605 |   63 |

|              be1-pe02-eqch2.as57976.net -   24 |  258 |  198 |   61 |   65 |   92 |   62 |

|        chi-eqch2-ia-bons-04.as57976.net -   25 |  250 |  188 |   57 |   60 |   84 |   57 |

|                           24.105.62.129 -   24 |  258 |  198 |   58 |   61 |   86 |   58 |

|________________________________________________|______|______|______|______|______|______|
4

Hey Lünas,

It looks like there’s some packet loss to the modem:
192.168.0.1 - 18 | 202 | 167 | 0 | 3 | 20 | 2 |
192.168.0.1 - 24 | 258 | 198 | 1 | 3 | 31 | 3 |

This is often due to wireless interference, so if your friend is connecting wirelessly, have them try testing the connection while hardwired into the modem with an ethernet cable.

5

Is there anything else they could try? They don’t currently have an ethernet cable

6

The could update their wireless drivers, make sure that the router is on current firmware, check for competing wireless signals on the same channel and change to a less congested channel, or change from 2.4 to 5ghz or from 5 to 2.4ghz depending on what the situation is.

Otherwise, no.

7

I would echo this as well. I recently had a friend with a similar issue. Constant d/cs started. When she wasn’t d/cing the lag was nearly unplayable.

After looking at everything I could think of…a simple network card driver update solved the issue.

8

I updated my wireless adapter and it worked! Thanks guys!