Hello I know that there are plenty of similar topics, but I haven't found any advice anywhere and my case is a bit different. I have a friend's laptop, her laptop connected to the huawei HG8245H (INEA) router for some time, all other devices connect without any problems. However, a connection error has been popping up for several days. At my home (orange lte huawei modem), this laptop supposedly connects, but after opening any browsers, no connection. And here is a curiosity, because I have asus nano wifi at home Link . When I connected, this connection was no problem. There is some DNS bug on built-in wifi in laptop but all methods: forget network, typing commands in cmd, ccleaner, malwarebytes, adwcleaner, google dns typing don't help. Sometimes the connection is strange, but after restarting Windows it is the old way. Actually, I rather re-install the system, unless someone has an idea
The router I have has a good range. The distance is maybe 60cm. But what does a wifi cable have to do with wireless connectivity? I will add that the cable connects normally too. I updated the drivers (atheros). According to one advice, entries in the registry were also deleted. No improvement
I'll try again then. There is a wifi card in the laptop (for wireless connectivity) and a cable or two is connected to that card. These cables usually lead to the hatch above the screen. There they are connected to a tiny antenna.
If the cable is broken, it means that the card is not connected to this antenna. Because laptops are energy-efficient, the card in this laptop without this antenna is not able to send a signal with enough power for the router to receive it well. The router, on the other hand, has so much power that the card is able to receive its signals even without an antenna. The laptop is supposed to connect to the network and shows full signal strength, but in fact, communication is almost impossible. Since these cables often run through the hinge in the hatch, each opening and closing the hatch bends them a bit. They may break after some time.
Place the laptop about 3 cm (three centimeters) from the router and check if the network works in the laptop on the built-in card, although a little better. If so, it is evidently the fault of the cable - the one connecting the wifi card in the laptop with this tiny antenna.
I did not write because there were so many options that I missed. I plugged the rescue drive to the USB. On it, wifi connected normally. That's why I doubt the physical damage to the wifi, because I also took such options, but the test with the usb system ruled out it
during the diagnosis made by the system, a message related to dns appeared, and exactly the DNS server may not be available. I read a lot of topics with this type of problem and there is always a problem in DNS. An interesting thing happened. After starting safe mode with network and then restarting Windows, the pages are loading normally, wifi connects but the speed is around 0.5 mb / s. For several hours of such a slow connection, even updates were downloaded. However, after installing it, the problem came back
Without loading the computer in Task Manager (Left Ctrl + Left Shift + Esc) check: - in the "Processes" tab, if something is not overloading your processor - in the "Network" tab, if something is not using the wifi network
Fire up the command prompt and enter the command: tracert -d 188.8.131.52 Then paste the result here.
Generally, it is nothing special, what was unnecessary I turned off in autostart. The network shows less than 1% load.
C: \ Windows \ system32> tracert -d 184.108.40.206
Tracking route up to 220.127.116.11 with a maximum of 30 hops.
1 227 ms 1092 ms 1305 ms 192.168.8.102 2 2207 ms 2209 ms 1107 ms 192.168.8.102 3 3073 ms 3024 ms 2765 ms 192.168.8.102 4 2875 ms 2164 ms 2242 ms 192.168.8.102 5 3289 ms 3296 ms 3140 ms 192.168.8.102 6 * * * Request timed out. 7 * * 2941 ms 192.168.8.102 8 3130 ms 2943 ms 2743 ms 18.104.22.168 9 * 3675 ms 3488 ms 22.214.171.124 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 1233 ms 651 ms 842 ms 192.168.8.102 19 1140 ms 791 ms 847 ms 192.168.8.102 20 645 ms 1816 ms 3539 ms 126.96.36.199
You have a giant ping, and packets are going some strange way. Can you confirm you have such a strange router address (192.168.8.102)?
Run the command line, run the commands and paste the results here: ipconfig / all netstat -e -s
The laptop should download the network card settings automatically. Go to "Network and Sharing Center" -> "Change network adapter settings" -> right-click on "Wireless Network Connection" and select "Properties". Then in the new window, select "Internet Protocol Version 4 (TCP / IPv4)" and click "Properties". Nothing should be entered here, and "automatic settings" should be selected. Same on the "Alternative Configuration" tab.
Similarly, check for "Internet Protocol Version 6 (TCP / IPv6)" that the download of settings is automatic.
Boot the laptop from the rescue disk and run this command "tracert -d 188.8.131.52", if this command does not work then try "traceroute -n 184.108.40.206". Paste the result.
Active openings = 49 Passive openings = 4 Unsuccessful connection attempts = 40 Reset connections = 12 Current Connections = 1 Segments received = 14765 Segments sent = 3102 Retransmitted Segments = 125
TCP statistics for IPv6
Active openings = 1 Passive openings = 3 Unsuccessful connection attempts = 3 Reset connections = 2 Current Connections = 0 Received segments = 55 Segments sent = 48 Retransmitted Segments = 16
UDP statistics for IPv4
Received datagrams = 2352 No ports = 29767 Reception errors = 54 Datagrams sent = 1688
UDP statistics for IPv6
Received datagrams = 194 No ports = 134 Reception errors = 4 Datagrams sent = 240
C: \ Windows \ system32>
Here from the USB system (linux)
root @ PartedMagic: ~ # traceroute -d 220.127.116.11 traceroute is 18.104.22.168 (22.214.171.124), 30 hops max, 38 byte packets 1 homerouter.cpe (192.168.8.1) 0.585 ms 0.534 ms 0.494 ms 2 172.18.130.201 (172.18.130.201) 18.130 ms 23.608 ms 18.285 ms 3 172.18.40.67 (172.18.40.67) 23.420 ms 20.880 ms 27.016 ms 4 172.18.40.41 (172.18.40.41) 18.036 ms 28.077 ms 20.050 ms 5 172.18.40.6 (172.18.40.6) 29.673 ms 23.728 ms 172.18.40.2 (172.18.40.2) 23.582 ms 6 126.96.36.199 (188.8.131.52) 21,342 ms 30,582 ms 24,278 ms 7 184.108.40.206 (220.127.116.11) 23,680 ms 370,980 ms 124,740 ms 8 ae104-10.ffttr6.frankfurt.opentransit.net (18.104.22.168) 175.244 ms 69.087 ms 112.616 ms 9 google-13.gw.opentransit.net (22.214.171.124) 144.896 ms 126.96.36.199 (188.8.131.52) 130.306 ms 45.853 ms 10 * 184.108.40.206 (220.127.116.11) 46.225 ms * 11 18.104.22.168 (22.214.171.124) 50.352 ms 126.96.36.199 (188.8.131.52) 51.041 ms 184.108.40.206 (220.127.116.11) 61.344 ms 12 google-public-dns-a.google.com (18.104.22.168) 54.096 ms 22.214.171.124 (126.96.36.199) 46.553 ms google-public-dns-a.google.com (188.8.131.52) 55.380 ms
ipconfig has confirmed that the basic configuration of the wireless card is correct. However, the data provided by netstat is already strange: for example "Forwarded datagrams (ipv4) = 286858" as if this laptop worked as a router. Also a bit weird "ICMPv4 Statistics".
tracert under windows is completely gone into space and I do not know how to explain the garbage that he spat out. As if it was connected to some computer instead of your router ... although that doesn't explain the trash either.
I wonder if you have any entries in the windows \ system32 \ drivers \ etc \ hosts file Could you paste its contents?
At the command prompt, run the commands and paste what they generate. route print -4 netsh interface ipv4 show route
There are a few things you can try later. Now I'm shooting blind, but maybe it'll help: 1) - Disconnect the laptop from the wifi network. - Go to "Network and Sharing Center" -> "Manage Wireless Networks" and delete all items as are. Log in to the network.
Rather, it won't change anything, but it will make sure that you are not automatically logging in somewhere you don't want to. Maybe some hacker is hacking you :)
2) Fire up the command prompt in administrator mode and run the commands:
netsh int tcp reset netsh int ip reset netsh winsock reset
Then you need to reset your computer. After rebooting, fire again at the command prompt: "tracert -d 184.108.40.206". I wonder if anything will change.
# Copyright (c) 1993-2009 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 220.127.116.11 rhino.acme.com # source server
# 18.104.22.168 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
# Copyright (c) 1993-2001 Microsoft Corp.
# This file has been automatically generated for use by Microsoft Internet
# Connection Sharing. It contains the mappings of IP addresses to host names
# for the home network. Please do not make changes to the HOSTS.ICS file.
# Any changes may result in a loss of connectivity between machines on the
# local network.
C: \ Windows \ system32> netsh interface ipv4 show route
Publish Met Type Prefix Idks Gateway / Interface Name ------- -------- --- ------------------------ --- ----- ------------------- No Manual 0 0.0.0.0/0 12 192.168.8.1 No Manual 256 127.0.0.0/8 1 Loopback Pseudo-Interface 1 No Manual 256 127.0.0.1/32 1 Loopback Pseudo-Interface 1 No Manual 256 127.255.255.255/32 1 Loopback Pseudo-Interface 1 No Manual 256 192.168.8.0/24 12 Wireless Network Connection odowa No Manual 256 192.168.8.100/32 12 Wireless Network Connection odowa No Manual 256 192.168.8.255/32 12 Wireless Network Connection odowa No Manual 256 22.214.171.124/4 1 Loopback Pseudo-Interface 1 No Manual 256 126.96.36.199/4 11 Local connection No Manual 256 188.8.131.52/4 12 Wireless Network Connection odowa No Manual 256 255.255.255.255/32 1 Loopback Pseudo-Interface 1 No Manual 256 255.255.255.255/32 11 Local connection No Manual 256 255.255.255.255/32 12 Wireless Network Connection odowa
I did network removal at the beginning, several times
C: \ Windows \ system32> tracert -d 184.108.40.206.
Tracking your route until 220.127.116.11. [18.104.22.168] with a maximum of 30 hops:
1 531 ms 636 ms 319 ms 192.168.8.100 2 121 ms 150 ms 107 ms 192.168.8.100 3 185 ms 5 ms 9 ms 192.168.8.100 4 8 ms 11 ms 10 ms 192.168.8.100 5 11 ms 5 ms 10 ms 192.168.8.100 6 6 ms 5 ms 3 ms 192.168.8.100 7 9 ms 10 ms 9 ms 192.168.8.100 8 20 ms 22 ms 8 ms 192.168.8.100 9 10 ms 8 ms 13 ms 192.168.8.100 10 23 ms 8 ms 16 ms 192.168.8.100 11 8 ms
I do not know. If only all interfaces on windows did not work, but you wrote that on asus nano it works without any problems. I'm leaving. Tracert returns the laptop's address all the time - as if some NAT was running in the background. Maybe some modified or damaged card drivers, but you also wrote that you reinstalled them. Corrupted or replaced card firmware? Even if I have never seen it before .... otherwise it works fine on Linux.
Maybe some super spec will come in and try to explain what happened here ... I can't explain it. I would also try to reinstall the system. Write later if that fixes the problem.
The most reliable and effective solution. Just remember to get the necessary drivers for this hardware now.
Tip from 08/08 and today 11/08 and the author is still in the forest. What is to blame is looking for a needle in a haystack and when the needle is found, it turns out to be so deeply stuck in the system that only the format.