logo elektroda
logo elektroda
X
logo elektroda

Laptop with windows 7 does not connect to the internet despite wifi connection.

pawelik2013 10008 19
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 17372259
    pawelik2013
    Level 10  
    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
  • ADVERTISEMENT
  • #2 17372318
    aachi
    Level 24  
    Maybe the antenna cable is broken? Windows may show full range, but the adapter has trouble sending data. Check if by placing your laptop next to the router the network will work a little better.
  • ADVERTISEMENT
  • #3 17372332
    pawelik2013
    Level 10  
    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
  • #4 17372406
    aachi
    Level 24  
    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.
  • #5 17372588
    pawelik2013
    Level 10  
    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
  • #6 17373141
    KOCUREK1970
    Network and Internet specialist
    Since it's W7, you can boot the system in safe mode with networking - test it.
  • ADVERTISEMENT
  • #7 17373577
    pawelik2013
    Level 10  
    And in safe mode the wifi works. But I noticed that MBAM was showing a message saying that protection is disabled. How to find out what is blocking wifi in normal boot?
  • #8 17373757
    KOCUREK1970
    Network and Internet specialist
    pawelik2013 wrote:
    And in safe mode the wifi works.

    pawelik2013 wrote:
    Actually, I rather re-install the system,

    The most reliable and effective solution.
    Just remember to get the necessary drivers for this hardware now.

    pawelik2013 wrote:
    I noticed that MBAM was showing the message that protection is disabled.

    Uninstall the program, scan it with some anti-virus.
  • #9 17373771
    jprzedworski
    Network and Internet specialist
    pawelik2013 wrote:
    is some error with DNS
    And more specifically?
  • #10 17373880
    pawelik2013
    Level 10  
    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
  • #11 17376035
    aachi
    Level 24  
    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 8.8.8.8
    Then paste the result here.
  • #12 17376167
    pawelik2013
    Level 10  
    Generally, it is nothing special, what was unnecessary I turned off in autostart. The network shows less than 1% load.
    Quote:
    C: \ Windows \ system32> tracert -d 8.8.8.8

    Tracking route up to 8.8.8.8 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 193.251.249.15
    9 * 3675 ms 3488 ms 193.251.252.246
    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 8.8.8.8

    Tracking complete.

    C: \ Windows \ system32>
  • ADVERTISEMENT
  • #13 17376692
    aachi
    Level 24  
    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 8.8.8.8", if this command does not work then try "traceroute -n 8.8.8.8". Paste the result.
  • #14 17377248
    pawelik2013
    Level 10  
    Normally on the computer it enters the address of the router 192.168.8.1. IP settings 4 and 6 are automatic
    Quote:
    Microsoft Windows [Version 6.1.7601]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C: \ Windows \ system32> ipconfig / all

    Windows IP configuration

    Host name. . . . . . . . . . . : User-Computer
    Primary DNS suffix. . :
    Node type. . . . . . . . . . . . : Hybrid
    IP routing enabled. . . . . . . : No
    WINS Proxy server enabled. . . . : No

    Wireless LAN adapter Wireless LAN connection:

    Connection-specific DNS Suffix:
    Description. . . . . . . . . . . . . . . : Qualcomm Atheros AR5007EG Wireless Networ
    k Adapter
    Physical address. . . . . . . . . . : 00-15-AF-E9-0E-FD
    DHCP enabled. . . . . . . . . . : No
    Auto configuration enabled. . . . : Yes
    Local connection IPv6 address. : fe80 :: 412d: d7b9: 3ca3: d0bf% 12 (Preferred)

    IPv4 address. . . . . . . . . . . . . : 192.168.8.100 (Preferred)
    Subnet mask. . . . . . . . . . : 255.255.255.0
    The lease was obtained. . . . . . . . : August 10, 2018 5:52:19 PM
    The lease expires. . . . . . . . . : August 11, 2018 5:52:19 p.m.
    Deafult Gateway. . . . . . . . . . : 192.168.8.1
    The DHCPv6 IAID. . . . : 218109359
    DHCPv6 Client DUID: 00-01-00-01-1D-C4-8E-FF-00-90-F5-8E-27-B8

    DNS servers. . . . . . . . . . . : 192.168.8.1
    192.168.8.1
    NetBIOS over Tcpip. . . . . . . : Activated

    Ethernet adapter Local connection:

    Condition of the media. . . . . . . . . . .: Media disconnected
    Connection-specific DNS Suffix:
    Description. . . . . . . . . . . . . . . : Realtek PCIe GBE Family Controller
    Physical address. . . . . . . . . . : 00-90-F5-8E-27-B8
    DHCP enabled. . . . . . . . . . : No
    Auto configuration enabled. . . . : Yes

    Teredo Tunneling Pseudo-Interface Card:

    Condition of the media. . . . . . . . . . .: Media disconnected
    Connection-specific DNS Suffix:
    Description. . . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical address. . . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP enabled. . . . . . . . . . : No
    Auto configuration enabled. . . . : Yes

    Isatap tunnel card. {98956DE8-EBE4-4DE7-8E7A-BDE5860B39E5}:

    Condition of the media. . . . . . . . . . .: Media disconnected
    Connection-specific DNS Suffix:
    Description. . . . . . . . . . . . . . . : Microsoft ISATAP # 3 tab
    Physical address. . . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP enabled. . . . . . . . . . : No
    Auto configuration enabled. . . . : Yes

    Tunnel card Local connection * 11:

    Condition of the media. . . . . . . . . . .: Media disconnected
    Connection-specific DNS Suffix:
    Description. . . . . . . . . . . . . . . : Microsoft ISATAP # 6 tab
    Physical address. . . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP enabled. . . . . . . . . . : No
    Auto configuration enabled. . . . : Yes

    Reusable ISATAP Interface Tunnel Card {4694DD60-BF3A-443D-A773-C1E3FA268758}:


    Condition of the media. . . . . . . . . . .: Media disconnected
    Connection-specific DNS Suffix:
    Description. . . . . . . . . . . . . . . : Microsoft ISATAP # 5 tab
    Physical address. . . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP enabled. . . . . . . . . . : No
    Auto configuration enabled. . . . : Yes

    Tunnel card Local connection * 12:

    Condition of the media. . . . . . . . . . .: Media disconnected
    Connection-specific DNS Suffix:
    Description. . . . . . . . . . . . . . . : Microsoft ISATAP # 7 tab
    Physical address. . . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP enabled. . . . . . . . . . : No
    Auto configuration enabled. . . . : Yes

    C: \ Windows \ system32> netstat -e -s
    Interface statistics

    Received Sent

    Bytes 39 110 238 151071576
    Unicast packets 405,960 1639068
    Packets other than unicast 6906 3996
    Rejected 0 0
    Errors 0 0
    Unknown protocols 0

    IPv4 Statistics

    Packets received = 334172
    Received header errors = 8
    Received address errors = 0
    Transferred datagrams = 286858
    Unknown protocols received = 175
    Packets received then discarded = 32008
    Packets Received Then Delivered = 18257
    Output requests = 6805
    Routing rejects = 0
    Output packets discarded = 3594
    Output packet without route = 6
    Reassembly required = 0
    Successful reassembly = 0
    Reassembly failures = 0
    Datagrams successfully fragmented = 6
    Unfragmented datagrams = 0
    Fragments created = 12

    IPv6 Statistics

    Packets received = 325
    Received header errors = 1
    Received address errors = 105
    Datagrams passed = 0
    Received unknown protocols = 0
    Packets received then discarded = 140
    Packets Received Then Delivered = 314
    Output requests = 409
    Routing rejects = 0
    Output packets discarded = 12
    Output packet without route = 2
    Reassembly required = 0
    Successful reassembly = 0
    Reassembly failures = 0
    Datagrams successfully fragmented = 0
    Unfragmented datagrams = 0
    Fragments created = 0

    ICMPv4 statistics

    Received Sent
    Messages 2188 1867
    Errors 0 0
    Destination unreachable 84 738
    Time exceeded 2104 1129
    Problems with parameters 0 0
    Source screensavers 0 0
    Forwardings 0 0
    Echo responses 0 0
    Echoes 0 0
    Timestamps 0 0
    Timestamp replies 0 0
    Address masks 0 0
    Address mask responses 0 0
    Router Requests 0 0
    Router announcements 0 0

    ICMPv6 statistics

    Received Sent
    Messages 63 71
    Errors 0 0
    Destination unreachable 3 3
    Package too large 0 0
    Timeout 0 0
    Problems with parameters 0 0
    Echoes 0 0
    Echo responses 0 0
    MLD 0 0 queries
    MLD reports 0 0
    BILL Done 0 0
    Router Requests 0 3
    Router announcements 0 0
    Neighbor's demands 29 36
    Neighbor's announcements 31 29
    Forwardings 0 0
    Router renumbering 0 0

    TCP statistics for IPv4

    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)
    Quote:
    root @ PartedMagic: ~ # traceroute -d 8.8.8.8
    traceroute is 8.8.8.8 (8.8.8.8), 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 80.50.105.25 (80.50.105.25) 21,342 ms 30,582 ms 24,278 ms
    7 195.205.0.25 (195.205.0.25) 23,680 ms 370,980 ms 124,740 ms
    8 ae104-10.ffttr6.frankfurt.opentransit.net (193.251.249.15) 175.244 ms 69.087 ms 112.616 ms
    9 google-13.gw.opentransit.net (193.251.252.246) 144.896 ms 72.14.214.52 (72.14.214.52) 130.306 ms 45.853 ms
    10 * 108.170.252.1 (108.170.252.1) 46.225 ms *
    11 108.170.232.241 (108.170.232.241) 50.352 ms 108.170.236.83 (108.170.236.83) 51.041 ms 216.239.47.246 (216.239.47.246) 61.344 ms
    12 google-public-dns-a.google.com (8.8.8.8) 54.096 ms 209.85.242.147 (209.85.242.147) 46.553 ms google-public-dns-a.google.com (8.8.8.8) 55.380 ms
  • #15 17377512
    aachi
    Level 24  
    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 8.8.8.8". I wonder if anything will change.
  • #16 17377693
    pawelik2013
    Level 10  
    w folderze etc znajdują sie :
    hosts
    Quote:
    # 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
    # space.
    #
    # Additionally, comments (such as these) may be inserted on individual
    # lines or following the machine name denoted by a '#' symbol.
    #
    # For example:
    #
    # 102.54.94.97 rhino.acme.com # source server
    # 38.25.63.10 x.acme.com # x client host

    # localhost name resolution is handled within DNS itself.
    # 127.0.0.1 localhost
    # ::1 localhost


    hosts
    Quote:
    # 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.
    #

    192.168.8.100 User-Komputer.mshome.net # 2023 8 3 9 19 25 5 462


    imhosts.sam
    network
    protocol
    services

    Quote:
    C:\Windows\system32>route print -4
    ===========================================================================
    Lista interfejsów
    12...00 15 af e9 0e fd ......Qualcomm Atheros AR5007EG Wireless Network Adapter

    11...00 90 f5 8e 27 b8 ......Realtek PCIe GBE Family Controller
    1...........................Software Loopback Interface 1
    14...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
    17...00 00 00 00 00 00 00 e0 Karta Microsoft ISATAP #3
    18...00 00 00 00 00 00 00 e0 Karta Microsoft ISATAP #6
    19...00 00 00 00 00 00 00 e0 Karta Microsoft ISATAP #5
    23...00 00 00 00 00 00 00 e0 Karta Microsoft ISATAP #7
    ===========================================================================

    Tabela tras IPv4
    ===========================================================================
    Aktywne trasy:
    Miejsce docelowe w sieci Maska sieci Brama Interfejs Metryka
    0.0.0.0 0.0.0.0 192.168.8.1 192.168.8.100 25
    127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
    127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
    127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
    192.168.8.0 255.255.255.0 On-link 192.168.8.100 281
    192.168.8.100 255.255.255.255 On-link 192.168.8.100 281
    192.168.8.255 255.255.255.255 On-link 192.168.8.100 281
    224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
    224.0.0.0 240.0.0.0 On-link 192.168.8.100 281
    255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
    255.255.255.255 255.255.255.255 On-link 192.168.8.100 281
    ================================================== =========================
    Permanent routes:
    Lack

    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 224.0.0.0/4 1 Loopback Pseudo-Interface
    1
    No Manual 256 224.0.0.0/4 11 Local connection
    No Manual 256 224.0.0.0/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
    Quote:
    C: \ Windows \ system32> tracert -d 8.8.8.8.

    Tracking your route until 8.8.8.8. [8.8.8.8]
    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
  • #17 17378560
    aachi
    Level 24  
    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.
  • #18 17378670
    KOCUREK1970
    Network and Internet specialist
    KOCUREK1970 wrote:
    pawelik2013 wrote:


    Actually, I rather re-install the system,



    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.
  • #19 17378813
    myszkoscielna
    Level 23  
    pawelik2013 wrote:
    How to find out what is blocking wifi in normal boot?


    transfer the post to the Antivirus Emergency Service, scan FRST there and place FRST logs and wait for FRST specialists for further steps.

    If you do not have any problems with putting the system up again, it will be the fastest solution as advised by its predecessors.
  • #20 17378841
    pawelik2013
    Level 10  
    I reinstalled the system and everything returned to normal. Thank you for your help

Topic summary

A user reported issues with a Windows 7 laptop that connects to Wi-Fi but fails to access the internet. The laptop successfully connected to a Huawei modem but experienced problems with a Huawei HG8245H router. Various troubleshooting steps were attempted, including driver updates, DNS configuration changes, and using a rescue USB drive, which indicated that the issue might not be hardware-related. Safe mode allowed for a functional connection, suggesting potential software conflicts. Further diagnostics revealed unusual network behavior, including high ping and strange routing. Ultimately, the user reinstalled the operating system, which resolved the connectivity issues.
Summary generated by the language model.
ADVERTISEMENT