Disconnected every hour or 2

Here is another one. Looks even worse.

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
10.0.0.1 - 0 3184 3184 0 17 307 13
96.120.60.149 - 0 3184 3184 0 16 422 14
ae-109-rur102.vancouver.wa.bverton.comcast. net - 2 3183 3150 0 18 459 14
ae-53-ar01.troutdale.or.bverton.comcast. net - 0 3183 3183 0 18 173 16
be-33490-cr01.seattle.wa.ibone.comcast. net - 0 3183 3183 9 22 173 21
be-10846-pe01.seattle.wa.ibone.comcast. net - 0 3183 3183 13 21 167 18
66.208.229.226 - 0 3183 3183 14 25 188 18
ae1-br01-eqse2.as57976. net - 0 3183 3183 31 48 192 44
xe-0-0-0-1-br01-eqsv5.as57976. net - 0 3183 3183 32 49 239 44
xe-0-0-1-1-br02-eqla1.as57976. net - 0 3183 3183 40 60 2576 44
et-0-0-29-br01-eqla1.as57976. net - 0 3183 3183 31 66 2086 44
et-0-0-2-br01-swlv10.as57976. net - 0 3183 3183 31 85 7626 42
et-0-0-31-pe02-swlv10.as57976. net - 0 3183 3183 31 46 219 43
137.221.105.2 - 0 3183 3183 38 44 201 41
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis. com )

i still disconnect every hour or 2…

wheres the tech support?!?!?

Please read this thread as they had the same issue.

1 Like

i changed it to 30 days…hope this works!!

This particular line seems to be common for the lag spikes. Not sure where it is from.

To answer, you have a really high latency on your home network and first hop. For most connections, that first hop really shouldn’t be above 10 for the worst hop. Often it’s 1-2. Whatever is happening starts on your home network.

Are you wired or wireless?
What band if wireless?
Have you updated network drivers and router firmware?
If the ISP provided the modem/router can you have them check it or replace it?
The first network hop off your home network also has issues. You may need to contact your ISP.

I am using a broadband connection through Comcast. A direct HDMI connection. I just uped the bandwidth a few weeks ago and it doesn’t seem to be helping much. Game actually runs pretty fair except for the sudden disconnects.

But I will contact Comcast and see what they can do. I might need a new modem/router.

the dhcp lease timeout change seems to have worked…ive been playing for hours this am and no disconnects…so far lol !!

jahana : i dont know if you know much about your router but check the dhcp lease timeout…if its 3600 as mine was change it and see if that works

That link about the DCHP lease was the answer for me. It also explains why I was getting dc’ed every hour exactly as the lease expired. I am sure changing the lease timeout from 3600 (seconds) to a higher number helps but I managed to fix it without changing that number. The problem isn’t the number but that the computer is not auto-renewing it before the expiration like it should. For me, what did the trick was the following (hit enter after steps 2-5):

  1. open command prompt with admin rights
  2. type netsh winsock reset
  3. type netsh int ip reset
  4. type ipconfig release
  5. type ipconfig renew
  6. restart your computer

After the restart I had a new one hour lease when I looked at ipconfig /all, but now it auto-renews before the expiration like it should. I have no idea how that all got corrupted for people but this seems like a simple fix. Thanks for the link Kneanderthal.

A final note: the auto-renewing has been working fine for several hours but since I do not know what garbled the DCHP lease process in the first place, I have no idea if it might return at this point.

stupid arris router wont let me set an indefinte timeout but the max is a number that takes the lease to 2155 HAHA

how do you see it auto renews dont see that in ipconfig

i hope the techies at blizz see this post im sure we arent the only few that have this problem

I am also having an issue with disconnects starting a couple days ago.

Edit- wanted to mention that i am hard wired into the router.

WinMTR statistics |

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

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

| 192.168.1.1 - 0 | 1069 | 1069 | 0 | 0 | 4 | 0 |

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

| 96-34-58-57.static.unas.mo.charter. com - 1 | 1045 | 1039 | 8 | 13 | 30 | 12 |

| crr01olvemo-bue-60.olve.mo.charter. com - 1 | 1045 | 1039 | 9 | 14 | 33 | 15 |

| bbr01olvemo-bue-70.olve.mo.charter. com - 1 | 1045 | 1039 | 9 | 16 | 33 | 15 |

| bbr02chcgil-bue-2.chcg.il.charter. com - 1 | 1045 | 1039 | 15 | 23 | 45 | 24 |

| prr01chcgil-bue-4.chcg.il.charter. com - 1 | 1045 | 1039 | 14 | 19 | 36 | 20 |

| eqix-ix-ch1.blizzard. com - 1 | 1045 | 1039 | 14 | 20 | 55 | 15 |

| ae1-br01-eqch2.as57976. net - 1 | 1045 | 1039 | 15 | 31 | 768 | 17 |

| be1-pe02-eqch2.as57976. net - 1 | 1045 | 1039 | 15 | 20 | 40 | 18 |

| chi-eqch2-ia-bons-04.as57976. net - 1 | 1045 | 1039 | 16 | 21 | 39 | 19 |

| 24.105.62.129 - 1 | 1045 | 1039 | 15 | 19 | 39 | 21 |

Edit - Another test that i ran right after a Disconnect.

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

| WinMTR statistics |

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

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

| 192.168.1.1 - 0 | 751 | 751 | 0 | 0 | 4 | 0 |

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

| 96-34-58-57.static.unas.mo.charter. com - 1 | 736 | 732 | 0 | 15 | 993 | 13 |

| crr01olvemo-bue-60.olve.mo.charter. com - 1 | 736 | 732 | 0 | 16 | 993 | 14 |

| bbr01olvemo-bue-70.olve.mo.charter. com - 1 | 736 | 732 | 0 | 21 | 996 | 13 |

| bbr02chcgil-bue-2.chcg.il.charter. com - 1 | 736 | 732 | 0 | 25 | 1005 | 21 |

| prr01chcgil-bue-4.chcg.il.charter. com - 1 | 736 | 732 | 0 | 22 | 997 | 20 |

| eqix-ix-ch1.blizzard. com - 1 | 739 | 736 | 14 | 22 | 554 | 17 |

| ae1-br01-eqch2.as57976. net - 1 | 739 | 736 | 15 | 26 | 555 | 21 |

| be1-pe02-eqch2.as57976. net - 1 | 739 | 736 | 15 | 22 | 554 | 20 |

| chi-eqch2-ia-bons-04.as57976. net - 1 | 736 | 732 | 0 | 23 | 1002 | 20 |

| 24.105.62.129 - 1 | 739 | 736 | 15 | 21 | 554 | 19 |

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

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

the disconnect for a dhcp renewal is fast enough not to be noticed by streaming service much…however it causes wow to disconnect. when i disconnected i did notice a hiccup in youtube and that was all but wow would completely disconnect. have you checked the 2 recommendations made earlier in post? the netsh commands or the dhcp lease timeout in your router

Yes sir i just tried that and it did not work. Also I just noticed that I am getting disconnected on things like Discord now just very briefly. @Helethia

Also, my renewal is 24hr long which seems to be the default.

Apparently my fix was only temporary. The problem was gone all day but it is back now. I have no idea what is causing this issue - whether it is a wow thing or whether it is a microsoft thing. Helethia is right I believe in that many people could have this issue and not really notice if they weren’t playing a Blizzard game or something similar. By the way Helethia, to see if it auto renews you have to check ipconfig /all. If you see an expire time at 1 am for example, you need to check ipconfig /all just before 1 am. If auto-renew is working correctly, you will see a new expire at some point before 1 am so everything continues to work smoothly.

It would be nice to find out what was causing this issue so the responsible party can take responsibility for fixing it. My solution posted earlier or the other solution to increase the lease time so it happens less often are both bandaid fixes for a deeper problem. If tech support or anyone else has some insight into a proper fix, that would be much appreciated. This problem has not been around for long so clearly someone made changes recently at some level - OS, ISP, software, …

When I set the time for the release it is usually when I am not on the computer to stop the hiccup with wow. That way it can release/renew during a time when I am not on the computer or wow.

I cannot pinpoint when this all started unfortunately but I do remember I was complaining to guildies about the disconnects and how weird they were because I could log back in immediately with no other problems. I also had other issues going on at the same time with my ISP.

You can reproduce this error by having wow open in the background and going into your command prompt as admin and typing ipconfig /release and ipconfig /renew it will disconnect you immediately from wow but you can log back in immediately which is the same thing that the lease is doing.

I have another piece of information to add. It seems to be that the DCHP auto-renew fails each night in the hour between 12 am and 1 am. All day I will have no issues and then it will fail to auto-renew after midnight. Once it fails to auto-renew I do my fix from above. It is another thing that I find puzzling. Does the OS or software or ?? get confused by the system date change at midnight? Is my fix for this after midnight what allows me to go the whole day without issues until midnight rolls around again?

Another thing I finally noticed is that ipconfig /all actually shows two lease expirations - one for ipv6 and one for ipv4? The ipv6 one always seems to be a minute or two away from expiration while the ipv4 seems to go by the one hour windows. I just toggled the option to enable ipv6 under wow/system/network to see if that has some impact on this.

Does the possible timing of the DHCP issue make sense to anyone?

I have concluded that my issues is not anything to do with the DCHP renew fail. Just experienced a DC and saw that my “renew” isn’t up for another 6 hours.

Edit - Just did a geolocation search on the 96-34-58-57.static.unas.mo.charter. com where i’m seeing packet loss and it shows that this is my local charter (my ISP) office. Looks like I will be calling them and doing some complaining to get them to do something.

~~|------------------------------------------------------------------------------------------|

| WinMTR statistics |

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

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

| 192.168.1.1 - 0 | 6812 | 6812 | 0 | 0 | 6 | 0 |

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

| 96-34-58-57.static.unas.mo.charter. com - 1 | 6800 | 6797 | 7 | 12 | 80 | 20 |

| crr01olvemo-bue-60.olve.mo.charter. com - 1 | 6800 | 6797 | 8 | 14 | 47 | 15 |

| bbr01olvemo-bue-70.olve.mo.charter. com - 1 | 6800 | 6797 | 9 | 18 | 48 | 31 |

| bbr02chcgil-bue-2.chcg.il.charter. com - 1 | 6800 | 6797 | 14 | 23 | 56 | 26 |

| prr01chcgil-bue-4.chcg.il.charter. com - 1 | 6800 | 6797 | 14 | 19 | 46 | 27 |

| eqix-ix-ch1.blizzard. com - 1 | 6800 | 6797 | 14 | 20 | 70 | 24 |

| ae1-br01-eqch2.as57976. net - 1 | 6800 | 6797 | 15 | 26 | 415 | 20 |

| be1-pe02-eqch2.as57976. net - 1 | 6800 | 6797 | 14 | 20 | 53 | 17 |

| chi-eqch2-ia-bons-04.as57976. net - 1 | 6800 | 6797 | 15 | 21 | 121 | 33 |

| 24.105.62.129 - 1 | 6800 | 6797 | 15 | 20 | 47 | 17 |

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

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

Thank you for finding that post! I think this was the issue I was having as well. I just changed my DHCP timeout on my router and am hoping that fixes it. Time will tell :slight_smile:

Also, for the duration of it, in between hop 5-6 there was a “No Response from Host” that had a 100 Packet loss that disappeared after I stopped. I also used 137.221.69.72 is my destination. What it looks like to me is something internally withing your servers is flipping me the bird.

Seems to be similar to me, ae1-br01-eqse2.as57976. net

Edited by Blizzard - this topic is being locked as this is an old post which was bumped. Please create your own thread or contact support.