Hi, I have a new Dell Inspiron 17-3721 with Windows 8. It is connected to a Linksys WRT160NL Wifi router.

The laptop occasionally loses its internet connection (approx. once per hour, even as I type this), and can't even connect to the router (neither ping nor its web page). When I look at the network settings, everything seems to be OK (IP address, DNS and gateway settings), except that it reports no internet connectivity.

Other computers in the network running Win XP, Vista or Android don't have any problems at all, so I am dead sure it's not a problem with the router or my ISP.

Sometimes the problem goes away after a few minutes, but usually it persists for a long time.

What is odd: When Internet Explorer times out it shows me a troubleshoot button. When I click it, usually connectivity is restored after a few seconds, while troubleshooter is trying to find a problem. I believe it pulls something straight while analyzing the network. I only wish I knew what.

I uninstalled McAfee security center because someone suggested it might be the root of the problem, but it didn't help.

Windows is up to date, also the BIOS has the latest version (from 3 days ago).

Any other hints?

Any other hints?

In circumstances like that I find it useful to do a tracert to the DNS server, seems to give it a kick that it needs or at least a clearer diagnostic about what may be wrong.

In the case of your router you could try using its diagnostics (e.g. from the other computer you say is not affected).

Otherwise you could use NetMon to see what is going on.   So far I would suspect a blockage in the router.

 
HTH

 
Robert Aldwinckle
---

I bought a new Lenovo laptop about 2 weeks ago and have the same problem.  I have a total of 4 laptops in the house.  The other 3 connect and stay connected without any problem.  I am suing a belkin wireless router.  I have searched the internet for a solution, to no avail.  I am hoping someone can come up with a solution.  None of the other computers have Win 8 they are all XP and Win 7.  I asked when purchasing the computer if I could put Win 7 on it and take 8 off but got a reply that it was not suggested, but would much rather have 7.  I find it much easier to use and much more user friendly.

I have a total of 4 laptops in the house.  The other 3 connect and stay connected without any problem.  I am suing a belkin wireless router.

 Then you could try the same diagnostics too.

None of the other computers have Win 8 they are all XP and Win 7.

One difference, especially with XP, could be no IPv6.

 
---

This kind of issues are caused by the device driver. Also in some cases, antivirus may cause this issue. Temporarily disable antivirus and make test. Also please contact the device manufacturer for Windows 8 compatible drivers.

A small update: I disabled IPv6 because somewhere it was suggested that this might be the problem, but it didn't help.

I compared the output of ipconfig/all between working and non-working network, but there is no difference. Everything looks the same.

Tracert to the DNS server doesn't help. Since not even the wifi router (which is also the DHCP server and the default gateway) is available (ping 192.168.1.1 times out), tracert stops there. I'm using my ISP's DNS servers which are assigned via DHCP.

Maybe it's not necessary to mention that again, but: All other hosts connected to the wifi router can always ping it, and they can always query the DNS servers and they can always open web pages and they can always send emails and whatnot. It is unbelievable that the latest version of windows has a problem with such a basic issue.

I installed Ubuntu on the same laptop today. So far it didn't have a problem with the network. I do admit that the installation of wifi was a little less out of the box.

I haven't found the time to use netmon yet. I wonder what it would tell me. I have never used netmon before. Is it comparable to wireshark?

In case someone wants to look at the output of  ipconfig, here it is:

C:\>ipconfig/all

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : Delle
   Primres DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein

Ethernet-Adapter Bluetooth-Netzwerkverbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Bluetooth-Gert (PAN)
   Physische Adresse . . . . . . . . : 9C-2A-70-BD-FC-E8
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter LAN-Verbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Broadcom Virtual Wireless Adapter
   Physische Adresse . . . . . . . . : 9E-2A-70-BD-7C-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Virtueller Microsoft-Adapter fr direktes
 WiFi
   Physische Adresse . . . . . . . . : 9E-2A-70-BD-FC-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter WiFi:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Dell Wireless 1704 802.11b/g/n (2,4 GHz)
   Physische Adresse . . . . . . . . : 9C-2A-70-BD-FC-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   IPv4-Adresse  . . . . . . . . . . : 192.168.1.106(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Lease erhalten. . . . . . . . . . : Dienstag, 12. Mrz 2013 21:48:24
   Lease luft ab. . . . . . . . . . : Mittwoch, 13. Mrz 2013 23:04:27
   Standardgateway . . . . . . . . . : 192.168.1.1
   DHCP-Server . . . . . . . . . . . : 192.168.1.1
   DNS-Server  . . . . . . . . . . . : 195.50.140.180
                                       195.50.140.114
   NetBIOS ber TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter Ethernet:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Realtek PCIe FE Family Controller
   Physische Adresse . . . . . . . . : B8-CA-3A-C9-8F-EF
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter isatap.{2B228D4A-0A46-4C64-9645-387B7EFEFBE2}:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter LAN-Verbindung* 4:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-6zu4-Adapter
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter Teredo Tunneling Pseudo-Interface:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   IPv6-Adresse. . . . . . . . . . . : 2001:0:9d38:6ab8:1098:3e3d:3f57:fe95(Bevo
rzugt)
   Verbindungslokale IPv6-Adresse  . : fe80::1098:3e3d:3f57:fe95%20(Bevorzugt)
   Standardgateway . . . . . . . . . : ::
   DHCPv6-IAID . . . . . . . . . . . : 637534208
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-18-9C-7E-AD-B8-CA-3A-C9-8F-EF

   NetBIOS ber TCP/IP . . . . . . . : Deaktiviert

A small update: I disabled IPv6 because somewhere it was suggested that this might be the problem, but it didn't help.

I compared the output of ipconfig/all between working and non-working network, but there is no difference. Everything looks the same.

Tracert to the DNS server doesn't help. Since not even the wifi router (which is also the DHCP server and the default gateway) is available (ping 192.168.1.1 times out), tracert stops there. I'm using my ISP's DNS servers which are assigned via DHCP.

Maybe it's not necessary to mention that again, but: All other hosts connected to the wifi router can always ping it, and they can always query the DNS servers and they can always open web pages and they can always send emails and whatnot. It is unbelievable that the latest version of windows has a problem with such a basic issue.

I installed Ubuntu on the same laptop today. So far it didn't have a problem with the network. I do admit that the installation of wifi was a little less out of the box.

I haven't found the time to use netmon yet. I wonder what it would tell me. I have never used netmon before. Is it comparable to wireshark?

In case someone wants to look at the output of  ipconfig, here it is:

C:\>ipconfig/all

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : Delle
   Primres DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein

Ethernet-Adapter Bluetooth-Netzwerkverbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Bluetooth-Gert (PAN)
   Physische Adresse . . . . . . . . : 9C-2A-70-BD-FC-E8
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter LAN-Verbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Broadcom Virtual Wireless Adapter
   Physische Adresse . . . . . . . . : 9E-2A-70-BD-7C-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Virtueller Microsoft-Adapter fr direktes
 WiFi
   Physische Adresse . . . . . . . . : 9E-2A-70-BD-FC-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter WiFi:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Dell Wireless 1704 802.11b/g/n (2,4 GHz)
   Physische Adresse . . . . . . . . : 9C-2A-70-BD-FC-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   IPv4-Adresse  . . . . . . . . . . : 192.168.1.106(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Lease erhalten. . . . . . . . . . : Dienstag, 12. Mrz 2013 21:48:24
   Lease luft ab. . . . . . . . . . : Mittwoch, 13. Mrz 2013 23:04:27
   Standardgateway . . . . . . . . . : 192.168.1.1
   DHCP-Server . . . . . . . . . . . : 192.168.1.1
   DNS-Server  . . . . . . . . . . . : 195.50.140.180
                                       195.50.140.114
   NetBIOS ber TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter Ethernet:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Realtek PCIe FE Family Controller
   Physische Adresse . . . . . . . . : B8-CA-3A-C9-8F-EF
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter isatap.{2B228D4A-0A46-4C64-9645-387B7EFEFBE2}:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter LAN-Verbindung* 4:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-6zu4-Adapter
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter Teredo Tunneling Pseudo-Interface:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   IPv6-Adresse. . . . . . . . . . . : 2001:0:9d38:6ab8:1098:3e3d:3f57:fe95(Bevo
rzugt)
   Verbindungslokale IPv6-Adresse  . : fe80::1098:3e3d:3f57:fe95%20(Bevorzugt)
   Standardgateway . . . . . . . . . : ::
   DHCPv6-IAID . . . . . . . . . . . : 637534208
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-18-9C-7E-AD-B8-CA-3A-C9-8F-EF

   NetBIOS ber TCP/IP . . . . . . . : Deaktiviert

• Edited by Dr. Hok Tuesday, March 12, 2013 11:09 PM added ipconfig output

A small update: I disabled IPv6 because somewhere it was suggested that this might be the problem, but it didn't help.

I compared the output of ipconfig/all between working and non-working network, but there is no difference. Everything looks the same.

Tracert to the DNS server doesn't help. Since not even the wifi router (which is also the DHCP server and the default gateway) is available (ping 192.168.1.1 times out), tracert stops there. I'm using my ISP's DNS servers which are assigned via DHCP.

Maybe it's not necessary to mention that again, but: All other hosts connected to the wifi router can always ping it, and they can always query the DNS servers and they can always open web pages and they can always send emails and whatnot. It is unbelievable that the latest version of windows has a problem with such a basic issue.

I installed Ubuntu on the same laptop today. So far it didn't have a problem with the network. I do admit that the installation of wifi was a little less out of the box.

I haven't found the time to use netmon yet. I wonder what it would tell me. I have never used netmon before. Is it comparable to wireshark?

In case someone wants to look at the output of  ipconfig, here it is:

C:\>ipconfig/all

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : Delle
   Primres DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein

Ethernet-Adapter Bluetooth-Netzwerkverbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Bluetooth-Gert (PAN)
   Physische Adresse . . . . . . . . : 9C-2A-70-BD-FC-E8
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter LAN-Verbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Broadcom Virtual Wireless Adapter
   Physische Adresse . . . . . . . . : 9E-2A-70-BD-7C-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Virtueller Microsoft-Adapter fr direktes
 WiFi
   Physische Adresse . . . . . . . . : 9E-2A-70-BD-FC-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter WiFi:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Dell Wireless 1704 802.11b/g/n (2,4 GHz)
   Physische Adresse . . . . . . . . : 9C-2A-70-BD-FC-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   IPv4-Adresse  . . . . . . . . . . : 192.168.1.106(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Lease erhalten. . . . . . . . . . : Dienstag, 12. Mrz 2013 21:48:24
   Lease luft ab. . . . . . . . . . : Mittwoch, 13. Mrz 2013 23:04:27
   Standardgateway . . . . . . . . . : 192.168.1.1
   DHCP-Server . . . . . . . . . . . : 192.168.1.1
   DNS-Server  . . . . . . . . . . . : 195.50.140.180
                                       195.50.140.114
   NetBIOS ber TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter Ethernet:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Realtek PCIe FE Family Controller
   Physische Adresse . . . . . . . . : B8-CA-3A-C9-8F-EF
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter isatap.{2B228D4A-0A46-4C64-9645-387B7EFEFBE2}:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter LAN-Verbindung* 4:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-6zu4-Adapter
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter Teredo Tunneling Pseudo-Interface:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   IPv6-Adresse. . . . . . . . . . . : 2001:0:9d38:6ab8:1098:3e3d:3f57:fe95(Bevo
rzugt)
   Verbindungslokale IPv6-Adresse  . : fe80::1098:3e3d:3f57:fe95%20(Bevorzugt)
   Standardgateway . . . . . . . . . : ::
   DHCPv6-IAID . . . . . . . . . . . : 637534208
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-18-9C-7E-AD-B8-CA-3A-C9-8F-EF

   NetBIOS ber TCP/IP . . . . . . . : Deaktiviert

• Edited by Dr. Hok Tuesday, March 12, 2013 11:09 PM added ipconfig output

A small update: I disabled IPv6 because somewhere it was suggested that this might be the problem, but it didn't help.

I compared the output of ipconfig/all between working and non-working network, but there is no difference. Everything looks the same.

Tracert to the DNS server doesn't help. Since not even the wifi router (which is also the DHCP server and the default gateway) is available (ping 192.168.1.1 times out), tracert stops there. I'm using my ISP's DNS servers which are assigned via DHCP.

Maybe it's not necessary to mention that again, but: All other hosts connected to the wifi router can always ping it, and they can always query the DNS servers and they can always open web pages and they can always send emails and whatnot. It is unbelievable that the latest version of windows has a problem with such a basic issue.

I installed Ubuntu on the same laptop today. So far it didn't have a problem with the network. I do admit that the installation of wifi was a little less out of the box.

I haven't found the time to use netmon yet. I wonder what it would tell me. I have never used netmon before. Is it comparable to wireshark?

In case someone wants to look at the output of  ipconfig, here it is:

C:\>ipconfig/all

Windows-IP-Konfiguration

   Hostname  . . . . . . . . . . . . : Delle
   Primres DNS-Suffix . . . . . . . :
   Knotentyp . . . . . . . . . . . . : Hybrid
   IP-Routing aktiviert  . . . . . . : Nein
   WINS-Proxy aktiviert  . . . . . . : Nein

Ethernet-Adapter Bluetooth-Netzwerkverbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Bluetooth-Gert (PAN)
   Physische Adresse . . . . . . . . : 9C-2A-70-BD-FC-E8
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Ethernet-Adapter LAN-Verbindung:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Broadcom Virtual Wireless Adapter
   Physische Adresse . . . . . . . . : 9E-2A-70-BD-7C-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter LAN-Verbindung* 1:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Virtueller Microsoft-Adapter fr direktes
 WiFi
   Physische Adresse . . . . . . . . : 9E-2A-70-BD-FC-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Drahtlos-LAN-Adapter WiFi:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Dell Wireless 1704 802.11b/g/n (2,4 GHz)
   Physische Adresse . . . . . . . . : 9C-2A-70-BD-FC-E7
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja
   IPv4-Adresse  . . . . . . . . . . : 192.168.1.106(Bevorzugt)
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Lease erhalten. . . . . . . . . . : Dienstag, 12. Mrz 2013 21:48:24
   Lease luft ab. . . . . . . . . . : Mittwoch, 13. Mrz 2013 23:04:27
   Standardgateway . . . . . . . . . : 192.168.1.1
   DHCP-Server . . . . . . . . . . . : 192.168.1.1
   DNS-Server  . . . . . . . . . . . : 195.50.140.180
                                       195.50.140.114
   NetBIOS ber TCP/IP . . . . . . . : Aktiviert

Ethernet-Adapter Ethernet:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Realtek PCIe FE Family Controller
   Physische Adresse . . . . . . . . : B8-CA-3A-C9-8F-EF
   DHCP aktiviert. . . . . . . . . . : Ja
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter isatap.{2B228D4A-0A46-4C64-9645-387B7EFEFBE2}:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter LAN-Verbindung* 4:

   Medienstatus. . . . . . . . . . . : Medium getrennt
   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Microsoft-6zu4-Adapter
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja

Tunneladapter Teredo Tunneling Pseudo-Interface:

   Verbindungsspezifisches DNS-Suffix:
   Beschreibung. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP aktiviert. . . . . . . . . . : Nein
   Autokonfiguration aktiviert . . . : Ja
   IPv6-Adresse. . . . . . . . . . . : 2001:0:9d38:6ab8:1098:3e3d:3f57:fe95(Bevo
rzugt)
   Verbindungslokale IPv6-Adresse  . : fe80::1098:3e3d:3f57:fe95%20(Bevorzugt)
   Standardgateway . . . . . . . . . : ::
   DHCPv6-IAID . . . . . . . . . . . : 637534208
   DHCPv6-Client-DUID. . . . . . . . : 00-01-00-01-18-9C-7E-AD-B8-CA-3A-C9-8F-EF

   NetBIOS ber TCP/IP . . . . . . . : Deaktiviert

• Edited by Dr. Hok Tuesday, March 12, 2013 11:09 PM added ipconfig output

Tracert to the DNS server doesn't help. Since not even the wifi router (which is also the DHCP server and the default gateway) is available (ping 192.168.1.1 times out), tracert stops there. I'm using my ISP's DNS servers which are assigned via DHCP.

What about the idea of using the router's diagnostics from another computer?   Or perhaps using another computer's diagnostics concerning the problem computer.

I haven't found the time to use netmon yet. I wonder what it would tell me. I have never used netmon before. Is it comparable to wireshark?

Yes.  It's Microsoft's tool.   The other is third-party.  In either case it would probably help to have a trace of it working normally to use for comparison purposes unless you really understand what you are looking at.

 

Actually I suppose you would probably do better trying a W8 troubleshooter and invoking one of W8's traces but I am only aware that they exist and don't know how to use them.  Perhaps that would be via  netsh  trace  /?   Again, you would undoubtedly want to see two traces, one of something working normally (such as your ping if that normally works) and then the identical procedure during the problem state.

 

Hopefully Arthur has some ideas for diagnostics, e.g. ones which would support or disprove his driver problem hypothesis.

 

Good luck

 
Robert
---

same problem with me...... but only diffrence is that my torrent never stop....... all browser and messenger stop working expect torrent. after half an hour i dnt knw how all messenger connect automatcly.....

What about the idea of using the router's diagnostics from another computer?   Or perhaps using another computer's diagnostics concerning the problem computer.

I checked the router's status when the computer's network connection failed. It is listed in the router'S DHCP client list (which is not a surprise as the lease expires only after a few hours), but otherwise the router doesn't provide any useful information (except that everything is fine; please forgive my if I reiterate this detail). I can't ping the computer (nor connect otherwise) from the outside.

Actually I suppose you would probably do better trying a W8 troubleshooter and invoking one of W8's traces but I am only aware that they exist and don't know how to use them.  Perhaps that would be via  netsh  trace  /?   Again, you would undoubtedly want to see two traces, one of something working normally (such as your ping if that normally works) and then the identical procedure during the problem state.

I tried a wireshark trace from the failed computer: All I see are many ARP requests per second (and a few SSDP broadcasts), and no reply to either.

When I started troubleshooting, wireshark reported at some point that the interface was disconnected (I guess the interface was reset) and stopped capturing.

I'll try with netmon next. I have no shortage of failure situations...

I will also try to re-install the wireless driver from Dell. I haven't done that yet because the installed version is the same as on Dell's website (6.30.59.74), but maybe it'll will help anyway.

I tried a wireshark trace from the failed computer: All I see are many ARP requests per second (and a few SSDP broadcasts), and no reply to either.

When I started troubleshooting, wireshark reported at some point that the interface was disconnected (I guess the interface was reset) and stopped capturing.

I'll try with netmon next. I have no shortage of failure situations...

I will also try to re-install the wireless driver from Dell. I haven't done that yet because the installed version is the same as on Dell's website (6.30.59.74), but maybe it'll will help anyway.

OK, so re-installing the driver doesn't help. (The funny thing is that the installer only installs the bluetooth driver for the combined wifi-bluetooth device. You need to find the wifi installer somewhere in the zip file and run it. But as I said it didn't help anyway.)

Next I captured with netmon. During the 'disconnection', I observed these messages:

• lots of "WiFi: [Management Beacon]" from all routers around.
• occasional "ICMPv6:Router Solicitation" messages which come from my laptop (to be more precise from the teredo tunneling pseudo interface, according to the IPv6 address) followed by "ICMPv6: Router Advertisement" from my WiFi router.
• "NbtNs:Query Request for WPAD" from my local IPv4 address
• LLMNR and IGMP messages also from my local IPv4 address
• "SSDP Request: M-SEARCH" also from my local IPv4 address
• HTTP requests from my local IPv4 address to emeahp.rendering.glbdns.microsoft.com with replies
• The laptop sends occasional ARP requests to the router, which doesn't reply as such, but the router immediately sends an ARP request to the laptop afterwards, to which the laptop replies.
• Occasionally the laptop sends DNS requests which are not answered.

That's about it. I am reluctant to post the entire capture as it seems to contain some confidential data.

When troubleshooting proceeds to a certain point, suddenly DNS requests receive answers, and everything is fine again. I can't see anything in the trace which looks like a wake-up call.

So something is going on on the wireless interface, just my browsers (Firefox and IE) can't use it. What I find strange is that this teredo pseudo interface sends IPv6 messages, even though I disabled IPv6 on the wifi interface. What is the purpose of the teredo interface anyway? Should I try to disable it?

I have the same problem.  I have several Windows 8 PC's (some upgraded to 8, some new) and "some" of them lose internet connectivity and other network functionality after sitting idle for a while.  The upgraded ones didn't do it before the upgrade, and nothing else has changed on them.  Some of the PC's stay connected all day.  Looking around other places, I see references for Windows 7 about registry settings for "Keep Connected" times, etc., but they don't apply to Windows 8. Very annoying!  I, too, turned off IPv6 - no help.  Nothing on the network (router, etc.) has changed - I'm thinking it's a Windows 8 issue.

Some more info: I visited relatives over Easter and spent quite some time using their wifi, which is a FritzBox (made by AVM in my home town!), and it never failed.

So it seems I nailed it down to a problem in the interplay of Windows 8 and the Linksys WRT160NL, as either of them works fine with different devices. The open question is what exactly goes wrong and how to solve it.

Some more info: I visited relatives over Easter and spent quite some time using their wifi, which is a FritzBox (made by AVM in my home town!), and it never failed.

So it seems I nailed it down to a problem in the interplay of Windows 8 and the Linksys WRT160NL, as either of them works fine with different devices. The open question is what exactly goes wrong and how to solve it.

• Edited by Dr. Hok Tuesday, April 09, 2013 8:10 PM

Some more info: I visited relatives over Easter and spent quite some time using their wifi, which is a FritzBox (made by AVM in my home town!), and it never failed.

So it seems I nailed it down to a problem in the interplay of Windows 8 and the Linksys WRT160NL, as either of them works fine with different devices. The open question is what exactly goes wrong and how to solve it.

• Edited by Dr. Hok Tuesday, April 09, 2013 8:10 PM

Some more info: I visited relatives over Easter and spent quite some time using their wifi, which is a FritzBox (made by AVM in my home town!), and it never failed.

So it seems I nailed it down to a problem in the interplay of Windows 8 and the Linksys WRT160NL, as either of them works fine with different devices. The open question is what exactly goes wrong and how to solve it.

• Edited by Dr. Hok Tuesday, April 09, 2013 8:10 PM

same problem with me...... but only diffrence is that my torrent never stop....... all browser and messenger stop working expect torrent. after half an hour i dnt knw how all messenger connect automatcly.....

I guess that's because a running torrent doesn't require a DNS lookup, only when it is started. And DNS is what fails, at least for me.

Linksys WRT160NL

What firmware level?   There were some DNS problems with Linksys...

http://support.linksys.com/en-ca/support/routers/WRT160NL

Supposedly there is a Release Notes available there but I only was able to get a EULA.pdf from it.   YMMV.

C.f.

http://community.linksys.com/t5/Wireless-Routers/WRT160N-V3-has-serioius-DNS-issues/td-p/280327/page/12?view=by_date_ascending

 
FYI

 
Robert
---

Linksys WRT160NL

What firmware level?   There were some DNS problems with Linksys...

Supposedly there is a Release Notes available there but I only was able to get a EULA.pdf from it.   YMMV.

Hm.. I do have the latest firmware version 1.0.03 build 2, but with a different release date (May 9, 2011 instead of July 25, 2011). Maybe I accidentally picked a hidden intermediate release. I will try to re-flash the router. Let's see if it helps.

I found the release note for that version, but it mentions one fix for UPnP only.

BTW: I am not sure, but the WRT160NL is not the same as the WRT160N despite similar name, so whats valid for one doesn't necessarily apply to the other.

I have had 2 Dell Inspiron 17-3721's, both with Windows 8 and both have been constantly losing the connection to my wireless router, which is a netgear router. I have 5 other laptops and 2 ipads connected to my network wirelessly and they never lose connection. None of the other systems are running Windows 8. They're running a combination of windows 7, windows vista, windows 2003 and windows xp... I've reinstalled the wireless driver and it hasn't fixed the issue. I'm seriously thinking about switching the 3721 to windows 7, to see if the issue goes away. I found online that other people have had issues with losing wireless connection with the dell 3721'a, but just not sure if the issue is with the dell or with windows 8 - or maybe a combination of both... any help would be appreciated! BTW, it lost connection twice in the few minutes that I've spent typing this...

I have same issues, but with a bit diff hardware, almost narrow down issue to particular hardware.

My setup is HP pavilion dm4-1010tu, using Broadcom wireless-N 1x1 chipsets.

Linksys/Cisco RVS4000 router, + linksys WRT54GL, 

other setup tried changing router to Trendnet TEW-633GR, and Engenius ESR9850,

Also tried multiple Broadcom driver version from old to new on station-drivers, to no available.

The strange thing is, there were quite a few access point on other sites works fine with the laptop. So I think we can rule out that wifi card is broken.

I bought dlink DWA-182 USB wifi adapter, and plugged that in seems there were less issue, but cannot be sure, this past several days my cable provider have issues but it fixed now, I'll report back tomorrow if that helps.

I seriously despise Broadcom wireless chips now, their Win 8 driver is terrible, on Win 7 it works fine. IT should already be a sign that it need updated driver on default Win 8 installation otherwise it really really slow. 

Its resolved.

dlink DWA-182 works fine for hours and hours.

Also purhased Ralink wireless -N 1x1 mini card, also works fine,

I'm throwing Broadcom wireless N card out.

Again... Its not that broadcom wireless card broken, it works fine in Win 7. 

Broadcom Windows 8 driver is terrible, I'm done waiting them to fix it.

Its resolved.

dlink DWA-182 works fine for hours and hours.

Also purhased Ralink wireless -N 1x1 mini card, also works fine,

I'm throwing Broadcom wireless N card out.

Again... Its not that broadcom wireless card broken, it works fine in Win 7. 

Broadcom Windows 8 driver is terrible, I'm done waiting them to fix it.

• Proposed as answer by SIRKEEN75 Friday, July 19, 2013 4:50 PM

Its resolved.

dlink DWA-182 works fine for hours and hours.

Also purhased Ralink wireless -N 1x1 mini card, also works fine,

I'm throwing Broadcom wireless N card out.

Again... Its not that broadcom wireless card broken, it works fine in Win 7. 

Broadcom Windows 8 driver is terrible, I'm done waiting them to fix it.

• Proposed as answer by SIRKEEN75 Friday, July 19, 2013 4:50 PM

Its resolved.

dlink DWA-182 works fine for hours and hours.

Also purhased Ralink wireless -N 1x1 mini card, also works fine,

I'm throwing Broadcom wireless N card out.

Again... Its not that broadcom wireless card broken, it works fine in Win 7. 

Broadcom Windows 8 driver is terrible, I'm done waiting them to fix it.

• Proposed as answer by SIRKEEN75 Friday, July 19, 2013 4:50 PM

Have you tried going into device properties -> Power management, and turning off "Allow the computer to turn off this device to save power"?

Hi guys,

Hope this is not too late, as topic ain't closed, let me contribute. :)

Il also own a Dell Inspiron 3721 with Windows 8 x64 pre-installed and damn wifi connection drops every couple of minutes.

After hours suffering hells, I finally fixed the issue: no router matters or whatever =>installing Broadcom's 1704 drivers for Windows 7x64 (v6.20.55.51 available on Dell's FTP) did the trick for me.

Hope this helps.

• Proposed as answer by Tickums 2 hours 33 minutes ago

Hi guys,

Hope this is not too late, as topic ain't closed, let me contribute. :)

Il also own a Dell Inspiron 3721 with Windows 8 x64 pre-installed and damn wifi connection drops every couple of minutes.

After hours suffering hells, I finally fixed the issue: no router matters or whatever =>installing Broadcom's 1704 drivers for Windows 7x64 (v6.20.55.51 available on Dell's FTP) did the trick for me.

Hope this helps.

• Proposed as answer by Tickums Thursday, October 31, 2013 8:15 AM

Hi guys,

Hope this is not too late, as topic ain't closed, let me contribute. :)

Il also own a Dell Inspiron 3721 with Windows 8 x64 pre-installed and damn wifi connection drops every couple of minutes.

After hours suffering hells, I finally fixed the issue: no router matters or whatever =>installing Broadcom's 1704 drivers for Windows 7x64 (v6.20.55.51 available on Dell's FTP) did the trick for me.

Hope this helps.

• Proposed as answer by Tickums Thursday, October 31, 2013 8:15 AM
• Marked as answer by Michael_MartinModerator Friday, March 14, 2014 3:48 PM

This sounds exactly like my situation.  My computer skills are marginal.  Could you explain to me how to access the driver that you describe?  My Dell is the same as yours, with Windows 8 pre-installed (Grrrrr!). 

Thanks.

I had the same issue. A few weeks of frustration and updates, checking network settings, etc. All to no avail. I finally uninstalled the driver and management tools that came with the wifi adapter. I then downloaded the DRIVER ONLY version of the driver with no management tools. I installed the driver and let Windows handle the connections. Been smooth sailing since.

Hope this helps.

I have the same Dell Inspiron also with Windows 8 and have the same problem. I have other devices in my home using the same network and they do not lose connectivity.  I have also looked at my settings and all appears to be okay.  I keep Windows up to date and I don't have McAfee installed.   Any other suggestions?

Can you please explain this a little more for someone who doesn't understand much in the way of network technology? Is it something you need to download? It sounds like it's for Windows 7 from your description though.