Question Various devices disconnect

Toggle sidebar Toggle sidebar
M

matizami

Distinguished
Jun 7, 2013
87
0
18,630
Hi y'all,

For the past few weeks, I've been experiencing disconnections and bad connections on different devices at different times. I can be in a room with a PC, Smart TV, iPad, etc., and all of a sudden the PC gets disconnected, or is still connected but not able to surf, while the other devices work perfectly. And then later the TV keeps losing connection while everything else works.


Any ideas? Is it a faulty router or maybe settings?
 
Make and model modem? Make and model router? Or it could be one device (modem/router).

The router's logs (if available and enabled) may provide some clue. Who has full admin rights to the router? You will need help from that person.

Also: On your computer run "ipconfig /all" (without quotes via the Command Prompt.

Likewise run "ping 8.8.8.8"

(The ping is targeting Google's website.)

Post the results of both commands. You should be able to copy and paste the results without needing to retype everything.

My first thought is duplicate IP addresses or a limit on the number of allowed network devices.

Are any devices configured to use static IP addresses?
 
My router is 02 homebox 6741 (Germany). It's not possible to extract log.
I don't think there's a device that configured to use static IP address. I certainly didn't configured it, but if you read the log, it does mark DHCP as yes🙄

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-ADXXXXX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : localdomain

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : localdomain
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : 00-D8-61-A6-49-A1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-NordVPN Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-4A-54-0D-D4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Unknown adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-92-20-7C-57
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Unknown adapter Local Area Connection 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NordLynx Tunnel
Physical Address. . . . . . . . . : 00-FF-E9-AD-C6-B2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 96-A6-7E-58-26-C9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 94-A6-7E-58-26-C9
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : localdomain
Description . . . . . . . . . . . : NETGEAR A7000 WiFi USB3.0 Adapter
Physical Address. . . . . . . . . : 94-A6-7E-58-26-C9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.6(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, 17 November 2023 16:44:18
Lease Expires . . . . . . . . . . : Friday, 24 November 2023 16:53:56
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

-------------------------
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=38ms TTL=114
Reply from 8.8.8.8: bytes=32 time=30ms TTL=114
Reply from 8.8.8.8: bytes=32 time=31ms TTL=114
Reply from 8.8.8.8: bytes=32 time=31ms TTL=114

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 38ms, Average = 32ms
 
DHCP simply means that it IS NOT using a static IP address. That option would show as NO if it was and you would have had to configure it yourself.

So it appears that you are using a combo box (model and router together). If you are getting random disconnects where one device connects, loses connection and another gets it, you are likely hitting a device limitation. There isn't anything specified in the user manual for the modem but the sad part is they usually don't tell that part.
 
It being disconnected and just not being able to surf are different problems in general.

In the first you are losing the wifi connection itself. The second the wifi connection between you and the router is good but there is some communication issue at a higher level.

Does it stay disconnected long enough that you can do the IPCONFIG /all command while it is broken. What are you doing to "fix" it.

What you want to do is compare the IPCOFIG /all output when it broken to what you posted. In general you will see "media disconnected" if the wifi is broken. If it stays connected you might get lucky and something else changes like the ip address.
 
I know it sounds weird, but it comes and goes. I had it for a couple of weeks last month, and then I just unplugged/reset the router a couple of times until it worked fine. And now it's back again. Either it disconnects completely (I get a message on the TV and PC that the WiFi is not connected) or it stays connected but nothing really moves. (speedtest download at 0.11mb)

To fix it, I either unplug the router a few times or wait a few minutes until it works. Until next time.

Here's the resuilts I got when it is broken:
Windows IP Configuration



Host Name . . . . . . . . . . . . : DESKTOP-ADXXXXX

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : localdomain



Ethernet adapter Ethernet:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . : localdomain

Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller

Physical Address. . . . . . . . . : 00-D8-61-A6-49-A1

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes



Ethernet adapter Ethernet 2:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : TAP-NordVPN Windows Adapter V9

Physical Address. . . . . . . . . : 00-FF-4A-54-0D-D4

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes



Unknown adapter Local Area Connection 2:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : TAP-Windows Adapter V9

Physical Address. . . . . . . . . : 00-FF-92-20-7C-57

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes



Unknown adapter Local Area Connection 3:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : NordLynx Tunnel

Physical Address. . . . . . . . . : 00-FF-E9-AD-C6-B2

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes



Wireless LAN adapter Local Area Connection* 9:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter

Physical Address. . . . . . . . . : 96-A6-7E-58-26-C9

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes



Wireless LAN adapter Local Area Connection* 10:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2

Physical Address. . . . . . . . . : 94-A6-7E-58-26-C9

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes



Wireless LAN adapter Wi-Fi:



Connection-specific DNS Suffix . : localdomain

Description . . . . . . . . . . . : NETGEAR A7000 WiFi USB3.0 Adapter

Physical Address. . . . . . . . . : 94-A6-7E-58-26-C9

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 192.168.1.82(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Friday, 17 November 2023 18:55:50

Lease Expires . . . . . . . . . . : Friday, 24 November 2023 18:55:50

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DNS Servers . . . . . . . . . . . : 192.168.1.1

NetBIOS over Tcpip. . . . . . . . : Enabled







Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=32ms TTL=112

Reply from 8.8.8.8: bytes=32 time=265ms TTL=112

Reply from 8.8.8.8: bytes=32 time=50ms TTL=112

Reply from 8.8.8.8: bytes=32 time=38ms TTL=112



Ping statistics for 8.8.8.8:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 32ms, Maximum = 265ms, Average = 96ms

p.s
When I started writing this comment, the WIFI on the PC wasn't working. Turned on the TV, everything was fine, including the PC. A few seconds later, not working again. Here are more results when the TV was on and it worked fine:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-ADXXXX
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : localdomain

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : localdomain
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : 00-D8-61-A6-49-A1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-NordVPN Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-4A-54-0D-D4
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Unknown adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TAP-Windows Adapter V9
Physical Address. . . . . . . . . : 00-FF-92-20-7C-57
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Unknown adapter Local Area Connection 3:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NordLynx Tunnel
Physical Address. . . . . . . . . : 00-FF-E9-AD-C6-B2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 96-A6-7E-58-26-C9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Local Area Connection* 10:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 94-A6-7E-58-26-C9
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : localdomain
Description . . . . . . . . . . . : NETGEAR A7000 WiFi USB3.0 Adapter
Physical Address. . . . . . . . . : 94-A6-7E-58-26-C9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.1.82(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Friday, 17 November 2023 18:55:50
Lease Expires . . . . . . . . . . : Friday, 24 November 2023 18:55:50
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 192.168.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Users\davek>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=31ms TTL=112
Reply from 8.8.8.8: bytes=32 time=31ms TTL=112
Reply from 8.8.8.8: bytes=32 time=32ms TTL=112
Reply from 8.8.8.8: bytes=32 time=31ms TTL=112

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 32ms, Average = 31ms
 
Very short outages are a huge pain to find.

So what i would do instead is open a couple CMD windows and run continuous ping. That way you should see the outage and the see it recover if it does.

I would run 3 ping windows at the same time.

Run tracert 8.8.8.8. This will show no issues the goal is to get the IP of the routers in the path. What you want to do is run 1 ping to 8.8.8.8. The second one to hop 1 which should be 192.168.1.1 in your case. The third window you want to ping hop 2 which should be the first router in your ISP network.

In many ways what you are hoping to see is no loss to hop 1 which means your wifi and router are likely fine. You kinda want to see the loss in hop 2. This represent the connection between your house and the ISP. It is the easiest to get the ISP to fix. If both hop1 and hop 2 are good but you still show loss to 8.8.8.8 then it is more complex. If all 3 are good then you suspect a DNS issue.....I would then change the DNS in your pc to 8.8.8.8
 
I hope I got it right. I run 3 pings at the same time:

1. tracert 8.8.8.8
2. ping 192.168.1.1 continuously
3. ping 8.8.8.8 continuously.

I run it for a minute or two. How long should I run it?

Ping statistics for 192.168.1.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 32ms, Average = 4ms

Ping statistics for 8.8.8.8:
Packets: Sent = 128, Received = 128, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 58ms, Average = 32ms

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

1 3 ms 3 ms 3 ms o2.box [192.168.1.1]
2 18 ms 19 ms 17 ms loopback1.0003.acln.01.ber.de.net.telefonica.de [62.52.201.186]
3 18 ms 18 ms 19 ms bundle-ether8.0001.cord.01.ber.de.net.telefonica.de [62.53.2.110]
4 24 ms 24 ms 27 ms ae10-0.0002.corx.02.ber.de.net.telefonica.de [62.53.25.243]
5 30 ms 22 ms 22 ms ae11-0.0001.corx.06.ham.de.net.telefonica.de [62.53.0.46]
6 23 ms 23 ms 23 ms bundle-ether2.0002.cord.01.ham.de.net.telefonica.de [62.53.14.233]
7 36 ms 38 ms 24 ms ae1-0.0001.prrx.01.ham.de.net.telefonica.de [62.53.25.59]
8 32 ms 31 ms 32 ms 74.125.48.102
9 33 ms 32 ms 32 ms 108.170.253.49
10 35 ms 35 ms 35 ms 209.85.240.161
11 31 ms 31 ms 31 ms dns.google [8.8.8.8]

Trace complete.
 
You want to add 62.52.201.186 to your ping cmds. This is likely the most important one.

Pretty much you want to run them constantly until you see the disconnect problem you talked about in the first post. This should let you determine where it is breaking even if the outage is very short. It really doesn't hurt your machine to run these. I have left them run for many weeks on my machines.
 
I let it run all night, and in the morning I saw that some requests had timed out. I can run it again of course.

Ping statistics for 62.52.201.186:
Reply from 192.168.1.1: Destination net unreachable.
Request timed out.

Packets: Sent = 19554, Received = 16235, Lost = 3319 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 409ms, Average = 18ms

Ping statistics for 192.168.1.1:

Packets: Sent = 37950, Received = 37936, Lost = 14 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 393ms, Average = 4ms

Ping statistics for 8.8.8.8:
Reply from 192.168.1.1: Destination net unreachable.
Request timed out
Packets: Sent = 24737, Received = 21410, Lost = 3327 (13% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 359ms, Average = 33ms
 
So you do see some random loss on the local port like the ethernet went down which is strange. If that happened and everything else was fine you would spend the time to look at it.

What you are seeing is a problem with the internet connection to your house.

If we ignore the 14 packets you get no loss in your house . You see 16% packet loss on your internet connection and you see the about the same loss 13% to the end node. This means the packet loss is real and not a testing error.

Packet loss of even 1% causes massive issues and if they occur many in row it will cause session to drop.

What I would do is show your ISP these 2 numbers...tell them a little lie and say your router get no loss technically it is 0%. They will get distracted trying to blame things in your house if they see even 1 packet lost.

This very clearly shows there is some fairly major issue with the line coming to your house. The ISP should be able to see this even from their main office because it is so large. There is a tiny chance it is a modem issue but most times it is something about the wires outside your house. It only takes a tiny bit of dirt or water to mess things up.
 
  • Like
Reactions: matizami
I have spoken to O2 and they will send a new router. Only if the new one doesn't work properly will they check the cables.

Thank you guys so much for the help, especially #bill001g, appreciate it! I will keep you posted,

​

 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom