View original (French)

IPv4 Connectivity "No Internet Access" over Ethernet

PierreBol -  
brupala Posted messages 111124 Registration date   Status Member Last intervention   -

Hello,

For the past few days, my wired internet connection has been experiencing a big problem:

I am on a desktop PC, connected via Ethernet to the box (Freebox Revolution), but for the past few days, the IPv4 connectivity shows "No Internet Access". The IPv6, however, is connected. Moreover, I switched to Wi-Fi (which works), but the speed is much lower.

The reason I’m posting here is that I’ve tried everything:

- Restarted the box and the PC (done 50 times),

- Used another Ethernet cable, used another port on the box,

- Enabled/disabled the connection,

- Diagnosed with the Windows help center, applied all the fixes it suggested, including resetting the network,

- Enabled/disabled the IPv4 protocol,

- Used DNS server addresses, used the automatic search function,

- Reset the protocol from the command prompt, reset the IP,

- Updated my network card, uninstalled and reinstalled it as well,

- Deleted programs that could interfere,

- Disabled the Windows firewall for a while.

In short, nothing works. I don't know how or why, but the connection worked again for a few hours before going back to this state. I don’t remember if it followed a personal action.

Important info, all of this happened right after I installed NordVPN on my PC; I don’t know if it’s related, but it all happened at that exact moment. I have obviously uninstalled the software since.

If you have any idea of a fix or where the problem could be coming from, I would appreciate it. I’m not convinced it’s the PC, but I don’t see how to resolve the issue from the box either.

Thank you very much!

1 answer

  1.
    brupala Posted messages 111124 Registration date   Status Member Last intervention   14 437
     

    Hello,

    if ipv6 is working, it means you don't have a physical connectivity issue.

    Start by checking that your ipv4 on the ethernet card is set to automatic.

    Then, paste here the result of the ipconfig/all command so we can check if Windows is giving you wrong information or not.

    And there you go....

    But goodness, those line breaks are so annoying!!

    0
    1. PierreBol
       

      Hello, I just saw the response, thank you!

      So yes, the IPv6 is connected to the internet, and the IPv4 is set to automatic.

      The result of ipconfig/all:

      Windows IP Configuration

         Host Name . . . . . . . . . . : DESKTOP-OA1CCUF
         Primary DNS Suffix . . . . . . :
         Node Type . . . . . . . . . .  : Hybrid
         IP Routing Enabled . . . . . . . : No
         WINS Proxy Enabled . . . . . . . : No

      Ethernet Ethernet Adapter:

         Connection-specific DNS Suffix . . . :
         Description. . . . . . . . . . . . . . : Realtek Gaming GbE Family Controller
         Physical Address . . . . . . . . . . . : F0-2F-74-1A-C3-1E
         DHCP Enabled . . . . . . . . . . . . . : Yes
         Autoconfiguration Enabled . . . : Yes
         IPv6 Address. . . . . . . . . . . . . .: 2a01:e34:ec06:7e0:b0c6:8995:387:422d(preferred)
         Temporary IPv6 Address . . . . . . . .: 2a01:e34:ec06:7e0:45c0:c2ed:4fa5:4ae9(preferred)
         Link-local IPv6 Address. . . . .: fe80::5723:9148:616b:5a4e%8(preferred)
         IPv4 Address. . . . . . . . . . . . . .: 192.168.0.102(preferred)
         Subnet Mask. . . . . . . . . . . . . : 255.255.255.0
         Lease Obtained. . . . . . . . . . . . . : Thursday, August 3, 2023 10:34:38
         Lease Expires. . . . . . . . . . . . . : Thursday, August 3, 2023 12:34:38
         Default Gateway. . . . . . . . . . . . : fe80::f6ca:e5ff:fe43:a3b0%8
                                             192.168.0.254
         DHCP Server . . . . . . . . . . . . . : 192.168.0.254
         DHCPv6 IAID . . . . . . . . . . . : 519057268
         DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-A4-33-31-F0-2F-74-1A-C3-1E
         DNS Servers. . .  . . . . . . . . . . : 192.168.0.254
         NetBIOS over Tcpip. . . . . . . . . . . : Enabled
       

      Hoping this says something interesting :D

      Thank you

      0
    2. brupala Posted messages 111124 Registration date   Status Member Last intervention   14 437 > PierreBol
       

      Everything seems fine, you appear to be well connected to your Freebox both in ipv4 (current DHCP lease) and in ipv6 (Freebox fe80::f6ca:e5ff:fe43:a3b0 as the default gateway).

      Try setting 1.1.1.1 as the ipv4 DNS server and 2602:4700:4700::1111 for ipv6, just to see, because your Windows is talking nonsense about ipv4, NordVPN seems to have messed something up in there, check if you have a restore point before the NordVPN installation.

      On Wi-Fi, is the default gateway really 192.168.0.254 too?

      Paste the result of tracert 1.1.1.1 if you can.

      0
    3. PierreBol > brupala Posted messages 111124 Registration date   Status Member Last intervention  
       

      I tried with 1.1.1.1, no difference, the IPv4 still says "no internet access".

      Result of the tracert 1.1.1.1 :

      Determining the route to 1.1.1.1 with a maximum of 30 hops.

        1     *        *        *     Request timed out.
        2     *        *        *     Request timed out.
        3     *        *        *     Request timed out.
        4     *     192.168.0.254  reports: Unable to reach the destination network.

      Route determined.
       

      The wifi gateway seems different :

      Wireless network card Wi-Fi :

         DNS suffix specific to the connection . . . :
         Description. . . . . . . . . . . . . . : TP-Link Wireless USB Adapter
         Physical address . . . . . . . . . . . : 28-EE-52-1A-EE-D6
         DHCP enabled. . . . . . . . . . . . . . : Yes
         Automatic configuration enabled. . . : Yes
         IPv6 address. . . . . . . . . . . . . .: 2a01:e34:ec06:7e0:dc9e:8c2f:bb06:d7e4(preferred)
         Temporary IPv6 address . . . . . . . .: 2a01:e34:ec06:7e0:4436:a6f3:d447:8089(preferred)
         Link-local IPv6 address. . . . . . . . .: fe80::1ed9:f2cb:b67a:3305%20(preferred)
         IPv4 address. . . . . . . . . . . . . .: 192.168.2.45(preferred)
         Subnet mask. . . . . . . . . . . . . . : 255.255.255.0
         Lease obtained. . . . . . . . . . . . . . : Thursday, August 3, 2023 11:03:29
         Lease expiring. . . . . . . . . . . . . : Thursday, August 3, 2023 11:09:56
         Default gateway. . . . . . . . . : fe80::f6ca:e5ff:fe43:a3b0%20
                                             192.168.2.254
         DHCP server . . . . . . . . . . . . . : 192.168.2.254
         DHCPv6 IAID . . . . . . . . . . . : 304672338
         DHCPv6 client DUID. . . . . . . . : 00-01-00-01-28-A4-33-31-F0-2F-74-1A-C3-1E
         DNS servers. . .  . . . . . . . . . . : 192.168.2.254
                                             fd0f:ee:b0::1
         NetBIOS over Tcpip. . . . . . . . . . : Enabled

      A restore point like a backup to back up the PC? Because in that case, I’m one of those irresponsible people who don’t do this kind of backup...

      0
    4. brupala Posted messages 111124 Registration date   Status Member Last intervention   14 437 > PierreBol
       

      OK, thanks,

      64:66:B3 Tp-Link Technologies Co., Ltd.

      that's the one messing up your ethernet.

      try to disconnect it if it's not the switch you're connected to.

      If it's the switch you're connected to, try connecting your cable directly to the box.

      it's possible your landlord has plugged in an old router in access point mode without disabling the DHCP server, or for some reason (crash, pressing the reset button) the thing has reverted to factory settings and is messing up the network.

      If you want to identify it better, try connecting to http://192.168.0.254 when you're on ethernet; if it's in factory config, you might be able to get in and disable the DHCP server.

      1
    5. brupala Posted messages 111124 Registration date   Status Member Last intervention   14 437 > PierreBol
       

      Well done :-))

      OK,

       I uninstalled the TP Link driver, which is the one for the wifi dongle. It didn't work,

      No, the problem is not in your PC; you can reinstall the tplink adapter, the issue is external.

      Have you seen what the TPlink hardware in question is on its interface?

      I don't know what you've done regarding its LAN config, but you must have changed its IP address, which would explain why you no longer have access to it; you could probably find it through a scan or on the box if you have the admin password.

      I hope you have properly disabled its DHCP server; if it's working, that should be the case.

      In any case,

      If its DHCP server took over, do the same; connect to the IP address of your default gateway in that case, and you should be able to access its interface.

      1