logo elektroda
logo elektroda
X
logo elektroda

Blocked access and website - I can't access the router settings page

yodam 7545 6
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 16300480
    yodam
    Level 10  
    Hello!

    All in all, it's hard for me to name this topic because it's so unusual that I can't find a similar case anywhere on the web. To the point, for several days I have had a strange problem with access to the router configuration page and to the website wykop.pl. Oddly enough, I also have the same problem on my phone, i.e. no access to both places, in addition, I can not connect to wykop.pl even via data transmission (i.e. there is no problem with the wifi network and router, and this is a problem on my devices) .
    - On the phone and on the PC I have Firefox with AdBlock and Norton installed, but after turning off, hopefully nothing changes and the attempt to connect to the above places on other browsers fails.
    - I have probably done everything possible from the console level, I upload a few logs here, maybe someone will know something more.

    nslookup debug
    Spoiler:
    C: \ WINDOWS \ system32> nslookup
    Default Server: NB604N.Home
    Address: 192.168.1.1

    > set debug
    > wykop.pl
    Server: NB604N.Home
    Address: 192.168.1.1

    ------------
    Got answer:
    HEADER:
    opcode = QUERY, id = 2, rcode = NXDOMAIN
    header flags: response, want recursion, recursion avail.
    questions = 1, answers = 0, authority records = 1, additional = 0

    QUESTIONS:
    wykop.pl.Home, type = A, class = IN
    AUTHORITY RECORDS:
    -> (root)
    ttl = 81208 (22 hours 33 mins 28 secs)
    primary name server = a.root-servers.net
    responsible mail addr = nstld.verisign-grs.com
    serial = 2017022300
    refresh = 1800 (30 mins)
    retry = 900 (15 mins)
    expire = 604800 (7 days)
    default TTL = 86400 (1 day)

    ------------
    ------------
    Got answer:
    HEADER:
    opcode = QUERY, id = 3, rcode = NXDOMAIN
    header flags: response, want recursion, recursion avail.
    questions = 1, answers = 0, authority records = 1, additional = 0

    QUESTIONS:
    wykop.pl.Home, type = AAAA, class = IN
    AUTHORITY RECORDS:
    -> (root)
    ttl = 81208 (22 hours 33 mins 28 secs)
    primary name server = a.root-servers.net
    responsible mail addr = nstld.verisign-grs.com
    serial = 2017022300
    refresh = 1800 (30 mins)
    retry = 900 (15 mins)
    expire = 604800 (7 days)
    default TTL = 86400 (1 day)

    ------------
    ------------
    Got answer:
    HEADER:
    opcode = QUERY, id = 4, rcode = NOERROR
    header flags: response, want recursion, recursion avail.
    questions = 1, answers = 0, authority records = 0, additional = 0

    QUESTIONS:
    wykop.pl, type = A, class = IN

    ------------
    ------------
    Got answer:
    HEADER:
    opcode = QUERY, id = 5, rcode = NOERROR
    header flags: response, want recursion, recursion avail.
    questions = 1, answers = 0, authority records = 0, additional = 0

    QUESTIONS:
    wykop.pl, type = AAAA, class = IN

    ------------
    *** No internal type for both IPv4 and IPv6 Addresses (A + AAAA) records available for wykop.pl



    Ipconfig / all

    Spoiler:
    Windows IP Configuration

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

    Wireless LAN adapter Połączenie lokalne* 11:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Microsoft Hosted Network Virtual Adapter #2
    Physical Address. . . . . . . . . : 54-2A-A2-85-FE-83
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes

    Wireless LAN adapter Wi-Fi:

    Connection-specific DNS Suffix . : Home
    Description . . . . . . . . . . . : D-Link DWA-131 Wireless N Nano USB Adapter(rev.E)
    Physical Address. . . . . . . . . : 54-2A-A2-85-FE-83
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    Link-local IPv6 Address . . . . . : fe80::715f:4d7:5f0f:fe5%9(Preferred)
    IPv4 Address. . . . . . . . . . . : 192.168.1.4(Preferred)
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Lease Obtained. . . . . . . . . . : czwartek, 23 lutego 2017 05:44:39
    Lease Expires . . . . . . . . . . : piątek, 24 lutego 2017 17:28:23
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DHCPv6 IAID . . . . . . . . . . . : 156510882
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-E0-65-A7-4C-CC-6A-61-1C-3D
    DNS Servers . . . . . . . . . . . : 192.168.1.1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter isatap.Home:

    Media State . . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix . : Home
    Description . . . . . . . . . . . : Microsoft ISATAP Adapter
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

    Connection-specific DNS Suffix . :
    Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No
    Autoconfiguration Enabled . . . . : Yes
    IPv6 Address. . . . . . . . . . . : 2001:0:1760:e3e7:28e2:862:f134:3e27(Preferred)
    Link-local IPv6 Address . . . . . : fe80::28e2:862:f134:3e27%5(Preferred)
    Default Gateway . . . . . . . . . : ::
    DHCPv6 IAID . . . . . . . . . . . : 234881024
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-E0-65-A7-4C-CC-6A-61-1C-3D
    NetBIOS over Tcpip. . . . . . . . : Disabled



    Ping wykop.pl
    Spoiler:
    C:\WINDOWS\system32>ping wykop.pl
    Ping request could not find host wykop.pl. Please check the name and try again.


    To co robiłem to flushdns, próbowałem ustawić manualnie dnsy, przeinstalowałem sterowniki do wifi (próbowałem dwóch wersji, starszej i najnowszej), skanowałem PC w poszukiwaniu malware, wirusów, etc i nic nie znalazłem,I checked the firewall (system off, Norton firewall turned off for 15 minutes and then the same).
    Interestingly, when I ping the router's address it responds and everything is ok, but when trying to get to it from the browser there is a problem.
    The rest of the pages, programs, etc work properly and normally, there is only a problem with this one page and access to the router.
    The issue of the phone remains a big mystery to me, I would not be surprised if the phone had this problem after connecting to Wifi, but when it does not load the page being connected to mobile data, it is something wrong.
    I am asking for help and thank you in advance.
  • ADVERTISEMENT
  • #2 16300525
    Darek A.
    Level 20  
    There are several options for getting rid of this behavior:

    - connect to the router with a cable, go to its configuration page and reset, remove the firewall;
    - check and change the wifi access password of your network, maybe someone is treating you, or reset it completely and re-enter its settings by giving different passwords;
    - check if you enter the excavation with Norton turned off, maybe he has some blocking rule;
    Must work.
  • ADVERTISEMENT
  • #3 16304403
    yodam
    Level 10  
    Darek A. wrote:
    There are several options for getting rid of this behavior:

    - connect to the router with a cable, go to its configuration page and reset, remove the firewall;
    - check and change the wifi access password of your network, maybe someone is treating you, or reset it completely and re-enter its settings by giving different passwords;
    - check if you enter the excavation with Norton turned off, maybe he has some blocking rule;
    Must work.


    So yes, I reset the router to factory settings, I also checked the excavation with norton turned off and nothing else. But...
    - I was able to fix the mobile data connection on the phone. It turned out that I had a changed access point, but there was no specific data there, e.g. in the user's place only "*", same with the password field and several options thrown out. Strange thing.
    - After restarting the router to the default settings, I can access it again via WiFi
  • #4 16305285
    Darek A.
    Level 20  
    Mainly I meant to get into the router now, if there are any specific pages, then this is:
    - or a restriction on the computer;
    - or blocked address (IP) on the router;
    - or the internet provider (broker) is blocking something;
    - or enter the wrong website address;
    - or the site is down
    and there is no other option.
    Can another (foreign) laptop, phone, etc. be connected by connecting to the net via your router to the excavation site or another blocked address?
    You need to specify where the lock is.
  • ADVERTISEMENT
  • #5 16305325
    yodam
    Level 10  
    Darek A. wrote:
    Mainly I meant to get into the router now, if there are any specific pages, then this is:
    - or a restriction on the computer;
    - or blocked address (IP) on the router;
    - or the internet provider (broker) is blocking something;
    - or enter the wrong website address;
    - or the site is down
    and there is no other option.
    Can another (foreign) laptop, phone, etc. be connected by connecting to the net via your router to the excavation site or another blocked address?
    You need to specify where the lock is.


    Already works but probably not entirely, because as pinguuje wykop.pl it loses all packages. But when I connect through a browser it works normally. What I did to solve the problem was:
    - After rebooting the router to factory settings flush dns
    - Checking the host file (I had about two entries there, but one on my local IP address and the other on address "1" - I threw both out)
    - Manually setting dnsów to 8888 and 8884
    - Computer restart

    From what I read on the network, my provider has had some DNS problems for several days and maybe this is a problem, I hope they solve it in some time. But I'm still worried that I can't ping wykop.pl. I have a problem with this portal for some time, sometimes in the morning when I start the computer and enter the excavation, after a few minutes the site becomes unavailable, I have to wait a few minutes to refresh and live again. At first I thought the administration was doing some work on the server or something and shut down the site for a while, but it happened too often, I checked if the excavation works on an independent device and worked. Does windows 10 have any hidden options, firewalls or anything that can block connections?
  • ADVERTISEMENT
  • #6 16305341
    Darek A.
    Level 20  
    Does this independent device on which the excavation works connect to the net via your router?
    Of course, the site kick is normal for others, only what is considered dangerous, because the login details are not protected (absurd warning), maybe just here a firewall establishes an access rule for you.
  • #7 16305348
    yodam
    Level 10  
    Darek A. wrote:
    Does this independent device on which the excavation works connect to the net via your router?

    Yes, all my devices at home (several people live with me) connect to the same router if they use WiFi

    Darek A. wrote:
    Of course, the site kick is normal for others, only what is considered dangerous, because the login details are not protected (absurd warning), maybe just here a firewall establishes an access rule for you.

    Well, that's interesting, because the only firewall I know about, which is my Norton, does not block this site because I looked through the logs of what was working there. Windows is disabled and the one on the router should not block anything if the page works properly on other devices.

    I had a laptop recently and there was no problem there (windows 7).

Topic summary

The user experienced issues accessing their router settings and the website wykop.pl on both PC and mobile devices. Initial troubleshooting included disabling Norton and AdBlock, resetting the router to factory settings, and checking DNS configurations. The user resolved mobile data access by correcting the access point settings. Despite regaining WiFi access to the router, they continued to face packet loss when pinging wykop.pl, suspecting DNS issues with their internet provider. Further investigation revealed that the Norton firewall was not blocking the site, and other devices connected to the same router were functioning normally.
Summary generated by the language model.
ADVERTISEMENT