View original (French)

Router management page access blocked

XRZ_Kaner -  
brupala Posted messages 111122 Registration date   Status Member Last intervention   -
Hello,

for some time now, I've been having a very strange problem that I've never experienced before with my router.

I'm connected with an Ethernet cable to my router, my PC shows that I have internet access, everything seems normal.
Now I open cmd, type 'ipconfig' and check the default gateway for my Ethernet connection, and it shows '192.168.0.1', but when I try to access it on Firefox, it immediately shows me this message:

"""
Connection failed

Firefox cannot establish a connection to the server at address 192.168.0.1.

The site may be temporarily unavailable or overloaded. Please try again later;
If you cannot browse any sites, check your computer's network connection;
If your computer or network is protected by a firewall or proxy, make sure Firefox is allowed to access the web.
"""

What intrigues me is that the page doesn't even load, the message appears instantly, so I think my PC is blocking access to this address... Especially since it's connected to the internet since I can browse any other site...

I also think it's a problem with my PC and not my modem since I can perfectly connect to the home page (so 192.168.0.1) from my phone, and I can see that my computer is connected...

I have tried the following solutions:

Check that my PC is properly connected to the modem, check the green LED next to the Ethernet port connected to my computer.

Check the IP address in question (explained above with cmd)

Restart my PC
Restart my modem (and even reset it with factory settings)

Despite all these checks, it still doesn't work... I've searched on many sites, but I still haven't found how to fix my problem...

So I'm turning to this forum hoping that someone might have an idea of the source of my problem.

Thank you in advance

Configuration: Windows / Firefox 93.0

8 answers

  1.
    brucine Posted messages 24767 Registration date   Status Member Last intervention   4 160
     
    Hello,

    It seems that it's either your firewall (disable it for testing) or your PC that doesn't have a local address in the same range.

    Go to network connections for the corresponding Ethernet adapter, right-click, properties, IPv4, properties: set a fixed address in the same range (for example 192.168.0.10), mask 255.255.255.0, gateway 192.168.0.1.

    Sometimes you also need to specify your provider's DNS to connect, which can be found online (ISP DNS or equivalent).
    0
  2. XRZ_Kaner
     
    Good evening,
    I just tried your solution of setting a fixed address, and specifying the mask and gateway, but it still doesn't work...

    I also forgot to mention that when I ping 192.168.0.1 there is no response (it shows general failure)...

    Recently I've been having strange problems with my computer, I think it has been infected...
    Sometimes I'm disconnected from my network out of nowhere.

    I also tried disabling the firewall of my antivirus, but that didn't work either.

    Do you know of any methods to determine if there is a virus attacking my network? Other than running a scan on the antivirus, because that did not yield any results...

    Thank you in advance.
    0
  3. brupala Posted messages 111122 Registration date   Status Member Last intervention   14 437
     
    Hello,
    can you run the command:
    tracert 1.1.1.1
    to see if 192.168.0.1 is really your default gateway.
    route print
    might be interesting too.

    --
    and ... There you go!
    0
  4. XRZ_Kaner
     
    Hello,

    here are the results of your commands:

    tracert 1.1.1.1
    """
    Determining the route to one.one.one.one [1.1.1.1]
    with a maximum of 30 hops:

    1 1 ms 1 ms 1 ms compalhub.home [192.168.0.1]

    2 17 ms 16 ms 16 ms CH-NAX01A-RT1.aorta.net [84.116.251.239]

    3 21 ms 24 ms 20 ms ch-nax01a-rc1-ae-20-0.aorta.net [84.116.204.53]

    4 20 ms 71 ms 19 ms ch-otf01b-rc1-ae-1-0.aorta.net [84.116.130.14]

    5 18 ms 20 ms 19 ms ch-zrh01b-ra1-ae-9-0.aorta.net [84.116.134.22]

    6 23 ms 22 ms 23 ms 213.46.171.222

    7 31 ms 20 ms 20 ms cloudflare-svc079353-ic369102.c.telia.net [213.248.94.81]

    8 20 ms 20 ms 19 ms one.one.one.one [1.1.1.1]

    Route determined.
    """
    And route print

    """
    IPv4 Routing Table
    ========================================================
    Active routes:
    Network Destination Subnet Mask Gateway Address Interface Address Metric

    0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.122 25

    127.0.0.0 255.0.0.0 On-link 127.0.0.1 331

    127.0.0.1 255.255.255.255 On-link 127.0.0.1 331

    127.255.255.255 255.255.255.255 On-link 127.0.0.1 331

    192.168.0.0 255.255.255.0 On-link 192.168.0.122 281

    192.168.0.122 255.255.255.255 On-link 192.168.0.122 281

    192.168.0.255 255.255.255.255 On-link 192.168.0.122 281

    192.168.56.0 255.255.255.0 On-link 192.168.56.1 281

    192.168.56.1 255.255.255.255 On-link 192.168.56.1 281

    192.168.56.255 255.255.255.255 On-link 192.168.56.1 281

    224.0.0.0 240.0.0.0 On-link 127.0.0.1 331

    224.0.0.0 240.0.0.0 On-link 192.168.56.1 281

    224.0.0.0 240.0.0.0 On-link 192.168.0.122 281

    255.255.255.255 255.255.255.255 On-link 127.0.0.1 331

    255.255.255.255 255.255.255.255 On-link 192.168.56.1 281

    255.255.255.255 255.255.255.255 On-link 192.168.0.122 281
    ========================================================
    Persistent routes:
    None
    0
  6. brupala Posted messages 111122 Registration date   Status Member Last intervention   14 437
     
    OK,
    So your box is indeed at 192.168.0.1, no doubt about it, and you can access the internet through it.
    It may be locked for pings, which is not smart on the part of the ISP because it seriously complicates diagnostics; fortunately, traceroute is allowed.
    For access to the interface,
    have you tried using https?
    For example:
    https://192.168.0.1:443

    --
    and ... There you go!
    0
  7. XRZ_Kaner
     
    Yes, I just tried it and it's not working...
    It's very strange, because this has never happened to me before
    At a certain point, I no longer had access to this page...

    What intrigues me the most is that I am now randomly disconnected from my wifi...

    All these strange actions never happened to me before, so I suspect that a virus has infected my network...
    0
  8. XRZ_Kaner
     
    Oh...

    I went on Microsoft Edge, it suggested I perform a network diagnostic

    When I looked at the details of the diagnosis (which clearly stated that my connection was blocked) I saw the name NordVPN

    I launched the app and in the settings I saw that I had enabled the "LAN INVISIBILITY" option...

    I disabled it

    I refreshed the page and it worked...

    I'm sharing the details of the solution in case this problem comes up for someone else...
    0
    1. brupala Posted messages 111122 Registration date   Status Member Last intervention   14 437
       
      Nordvpn messes with your PC...
      Not very clean that :-(
      Because it doesn't appear in the routing table, the VPN is therefore not active.
      If it's fiddling with the ICMP requests and messing around with local traffic, it's not clean at all, I would never trust such a product, it's not its role to be a "VPN" / remote NAT.
      PS,
      your connection wasn't blocked since it was working, including the traceroute.
      Fed up with these tools that overstep their role.
      0
  9. XRZ_Kaner
     
    Yes, it's true that I didn't expect the problem to come from NordVPN, and I don't know what it's doing in my local traffic...

    Moreover, now the tracert 1.1.1.1 is completely different.

    I think I won't use NordVPN for a little while...(especially since I don't use it much to begin with)

    Anyway, thanks for all the advice and have a good evening!!
    0
    1. brupala Posted messages 111122 Registration date   Status Member Last intervention   14 437
       
      ah ?
      what is tracert?
      isn't it a Dutch ISP anymore?
      I should have asked you for an arp -a too, to see if it was really a box as the gateway.
      Because if the VPN was active, it becomes the default gateway and it's normal that your box is no longer on the route at the internet level.
      0