logo elektroda
logo elektroda
X
logo elektroda

TP-Link TL-WR802Nv2 Configuration Screen Access Issues: Switching Modes and WiFi Connection

Seljuck 8112 11
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 16723054
    Seljuck
    Level 9  
    Hello,

    I have a problem accessing the title router's configuration screen. I need to change its working mode from Router to Client and connect it to an existing WiFi network. I have already checked different versions of tips found on the internet but I still can't access the router.

    The router normally creates its own wifi network, but the "tplinkwifi.net" page does not respond, I can't get to the IP addresses, but I do not know what is correct, because I checked several versions of the Internet. I have changed the TCP / IPv4 settings

    Here ip config / all
    Spoiler:
    Microsoft Windows [Version 10.0.15063]
    (c) 2017 Microsoft Corporation. All rights reserved.

    C: \ Users \ Sel> ipconfig / all

    Windows IP Configuration

    Host Name. . . . . . . . . . . . : Sel-Komputer
    Primary Dns Suffix. . . . . . . :
    Node Type. . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No.
    WINS Proxy Enabled. . . . . . . . : No.

    Wireless LAN adapter Local connection * 2:

    Media state. . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix. :
    Description. . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
    Physical Address. . . . . . . . . : 08-62-66-9C-30-D0
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled. . . . : Yes

    Ethernet adapter Local connection:

    Connection-specific DNS Suffix. :
    Description. . . . . . . . . . . : Intel (R) 82579V Gigabit Network Connection
    Physical Address. . . . . . . . . : F4-6D-04-3C-45-C7
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled. . . . : Yes
    Link-local IPv6 Address. . . . . : fe80 :: 92c: eeb6: 8075: 792c% 13 (Preferred)
    Autoconfiguration IPv4 Address. . : 169.254.121.44 (Preferred)
    Subnet Mask. . . . . . . . . . . : 255.255.0.0
    Default Gateway. . . . . . . . . :
    DHCPv6 IAID. . . . . . . . . . . : 401894660
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-B1-81-AC-08-62-66-9C-30-D6
    DNS Servers. . . . . . . . . . . : fec0: 0: 0: ffff :: 1% 1
    FEC0: 0: 0: ffff :: 2% 1
    FEC0: 0: 0: ffff :: 3% 1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Wireless LAN adapter Wireless network connection:

    Connection-specific DNS Suffix. :
    Description. . . . . . . . . . . : ASUS USB-N14 802.11n Wireless USB Adapter
    Physical Address. . . . . . . . . : 08-62-66-9C-30-D6
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled. . . . : Yes
    Link-local IPv6 Address. . . . . : fe80 :: 1ed: 337e: dd0e: 2726% 16 (Preferred)
    Autoconfiguration IPv4 Address. . : 169.254.39.38 (Preferred)
    Subnet Mask. . . . . . . . . . . : 255.255.0.0
    Default Gateway. . . . . . . . . :
    DHCPv6 IAID. . . . . . . . . . . : 235430502
    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1E-B1-81-AC-08-62-66-9C-30-D6
    DNS Servers. . . . . . . . . . . : fec0: 0: 0: ffff :: 1% 1
    FEC0: 0: 0: ffff :: 2% 1
    FEC0: 0: 0: ffff :: 3% 1
    NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Teredo Tunneling Pseudo-Interface:

    Media state. . . . . . . . . . . : Media disconnected
    Connection-specific DNS Suffix. :
    Description. . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
    Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-00-E0
    DHCP Enabled. . . . . . . . . . . : No.
    Autoconfiguration Enabled. . . . : Yes


    TP-Link TL-WR802Nv2 Configuration Screen Access Issues: Switching Modes and WiFi Connection

    Any advice?

    PS. I tested on 2 laptops and a desktop computer with a wifi card on usb. It's the same everywhere.
  • ADVERTISEMENT
  • ADVERTISEMENT
  • #3 16723116
    Seljuck
    Level 9  
    I do not know if you paid attention to what was in the spoiler, but during the test it was connected with a cable and via wifi ...

    I tested both forms of connection both separately and together, with the same poor effect.
  • ADVERTISEMENT
  • #4 16723128
    Anonymous
    Level 1  
  • ADVERTISEMENT
  • #6 16723158
    Seljuck
    Level 9  
    Erbit wrote:
    The address of your network card has not been assigned by the router. As a result, your network card and router are in a different class and therefore you cannot access it.

    In fact, your router is a gateway for your network card and you should look for it under this IP address (under the gateway address). As you can see the "gateway" is empty.


    How can this be fixed? Is it a matter of your router or computer settings?

    I will add that I did a 30-30-30 reset.
  • #7 16723190
    Anonymous
    Level 1  
  • #8 16723210
    Seljuck
    Level 9  
    Erbit wrote:
    Seljuck wrote:
    ... I did a 30-30-30 reset.


    What is a 30-30-30 reset?
    The instructions include:
    Quote:
    Reset : It is used to reset the Router to its factory defaults. With the Router powered on, use a
    pin to press and hold the Reset button (about 5 seconds) until the LED becomes quick-flash
    from slow-flash.
    And then release the button and wait the Router to reboot to its factory
    default settings.


    Did you do the reset like that?


    The 30-30-30 reset
    If the above instructions don't work you can always try the 30-30-30 reset as follows:
    
        When router is powered on, press the reset button and hold for 30 seconds. (Use a paper clip or something sharp)
        While holding the reset button pressed, unplug the power of the router and hold the reset button for 30 seconds
        While still holding the reset button down, turn on the power to the unit again and hold for another 30 seconds.
    
    This process usually works for resetting any router to it's factory setting. If that doesn't work be sure to check out the questions and answers incase someone else has had similar problems resetting their router.
    Note: It is worth reading more about how to reset routers with the 30 30 30 reset and what the risks and considerations are when resetting your router this way, instead of just rebooting it. 


    I did so, what you wrote also I did.

    When you try to connect your phone to a wifi network with tp the link pops up saying that you can't get the IP .. it looks like the router configuration is lying. The question is, is there a way to get to it and improve the configuration?
  • #9 16723253
    Anonymous
    Level 1  
  • #10 16723270
    Seljuck
    Level 9  
    Erbit wrote:
    Quote:

    The default IP addresses of the TL-WR802N have two: 192.168.0.254 for AP mode, Range
    Extender mode and Client mode, and 192.168.0.1 for Wireless Router mode and Hotspot Router
    mode. And the default Subnet Mask is 255.255.255.0. These values can be changed as you
    desire. In this guide, we use all the default values for description. Here we also take "192.168.0.254"
    as an example.


    It is true that the lack of DHCP suggests that you are right but .... I would set a static network card address to the same class (e.g. 192.168.0.2) and tried to call 192.168.0.1 and 192.168.0.254 on both ports, i.e. 80 and 8080.
    I would do it on both network adapters (WiFi, LAN) with only WiFi connected or only LAN (configuring the IP for both adapters).



    It helped :) It turns out that the router has off. DHCP: / After setting the static address for wifi TCP / IPv4 as you specified, i.e. 192.168.0.2 and calling 192.168.0.254, the configuration page fired up :)

    I hope this will help others :)
  • #11 16723277
    Anonymous
    Level 1  
  • #12 16723291
    Seljuck
    Level 9  
    3h setup attempts and success! :P Thanks for the advice, I don't know if I'd figure it out myself. :)

Topic summary

The discussion revolves around issues accessing the configuration screen of the TP-Link TL-WR802Nv2 router to switch its mode from Router to Client and connect to an existing WiFi network. The user faced difficulties accessing the router's interface via "tplinkwifi.net" and IP addresses, despite attempts to connect through both wired and wireless methods. Responses highlighted the importance of ensuring the network card receives an IP address from the router, suggesting a static IP configuration (e.g., 192.168.0.2) when DHCP was disabled. A successful 30-30-30 reset was also discussed, which ultimately led to resolving the access issue after setting the static address. The user confirmed that the configuration page became accessible after these adjustments.
Summary generated by the language model.
ADVERTISEMENT