none
Windows 8 keeps losing connectivity

    Question

  • Hi, not sure if this is unique but for the past few weeks Windows 8 has been losing connectivity every few minutes when browsing web pages, playing games etc. I am sure it's windows 8 as I have another work laptop using XP that I can be on all day via a VPN and that does not drop at all (it would normally drop within a few seconds of losing connectivity). I've done a lot of searching on the net for the same issue, others seem to be having similar things happen such as slow speed but can't find anything that matches, hence this separate question.

    I have also tried swapping routers to no avail. The thing is, you wouldn't know anything had happened from the network connectivity. Suddenly a page won't load. The wireless connectivity at the bottom right of the screen shows a full 5 bars (not limited connectivity). The way to get it back again is to leave it for a few minutes or disconnect from the router and reconnect again. Even whilst typing this I have had to do that twice.

    I'd appreciate some suggestions!

    Many Thanks, Paul.

    PS... IPCONFIG/ALL shows...

    Microsoft Windows [Version 6.2.9200]
    (c) 2012 Microsoft Corporation. All rights reserved.

    Wireless LAN adapter Local Area Connection* 17:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft Hosted Network Virtual Adapter
    #3
       Physical Address. . . . . . . . . : 56-DE-2B-64-0B-25
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter WiFi 2:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Qualcomm Atheros AR5B125 Wireless Network
     Adapter
       Physical Address. . . . . . . . . : 74-DE-2B-64-0B-25
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       IPv4 Address. . . . . . . . . . . : 192.168.0.4(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : 11 May 2013 10:31:15
       Lease Expires . . . . . . . . . . : 12 May 2013 10:31:21
       Default Gateway . . . . . . . . . : 192.168.0.1
       DHCP Server . . . . . . . . . . . : 192.168.0.1
       DNS Servers . . . . . . . . . . . : 194.168.4.100
                                           194.168.8.100
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Ethernet adapter Local Area Connection:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Broadcom NetLink (TM) Ethernet
       Physical Address. . . . . . . . . : DC-0E-A1-07-A8-F0
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter isatap.{A319BEA5-A55C-4E0C-AF67-922BEBD4C7BB}:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Microsoft ISATAP Adapter
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 13:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:3483:1732:adda:66e3(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::3483:1732:adda:66e3%14(Preferred)
       Default Gateway . . . . . . . . . : ::
       DHCPv6 IAID . . . . . . . . . . . : 436207616
       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-28-39-CC-DC-0E-A1-07-A8-F0

       NetBIOS over Tcpip. . . . . . . . : Disabled


    • Edited by PaulDarken Saturday, May 11, 2013 10:09 AM
    Saturday, May 11, 2013 9:54 AM

Answers

  • I am sure it's windows 8 as I have another work laptop using XP that I can be on all day via a VPN

    Typically XP does not use IPv6.  See if disabling IPv6 on W8 changes your symptom?  Otherwise it sounds like you are hitting some kind of threshold which is then somehow being relieved until it is hit again.  Resource Monitor may give you some clues.  Otherwise there are supposedly some new PowerShell tools which let us help replace some old netsh commands (at least it seems so we are informed each time we try to use netsh commands <w>).   Otherwise you might spot a pattern by running a packet trace, e.g. using NetMon or WireShark.  In fact, if you're lucky just looking at  ProcMon's Network tab might help too but there is a lot less detail that way and what is there is not easily identifiable.

     
    Good luck

     
    Robert Aldwinckle
    ---

    Saturday, May 18, 2013 8:23 PM

All replies

  • Hi,

    Does this issue occur with both wireless and wired?

    I suggest to perform these tests to troubleshoot the issue:

    1 Update NIC card for your machine

    2 Temporary disable firewall and antivirus program

    3 Logon with Safe Mode with Networking

    4 Update framework for your router.


    Leo Huang
    TechNet Community Support

    Monday, May 13, 2013 6:45 AM
  • Thanks for the suggestions. I have done all of these but was already up to date on framework and nic card.

    Any other suggestions appreciated.

    Thursday, May 16, 2013 8:19 PM
  • I am sure it's windows 8 as I have another work laptop using XP that I can be on all day via a VPN

    Typically XP does not use IPv6.  See if disabling IPv6 on W8 changes your symptom?  Otherwise it sounds like you are hitting some kind of threshold which is then somehow being relieved until it is hit again.  Resource Monitor may give you some clues.  Otherwise there are supposedly some new PowerShell tools which let us help replace some old netsh commands (at least it seems so we are informed each time we try to use netsh commands <w>).   Otherwise you might spot a pattern by running a packet trace, e.g. using NetMon or WireShark.  In fact, if you're lucky just looking at  ProcMon's Network tab might help too but there is a lot less detail that way and what is there is not easily identifiable.

     
    Good luck

     
    Robert Aldwinckle
    ---

    Saturday, May 18, 2013 8:23 PM
  • Having the exact same issue. Several other computers (desktop, 3 laptops, and several tablets have no issues.) I have another network and router in my home and have the same issue on both networks. Let me know if you ever find a solution.
    Monday, May 05, 2014 7:01 PM