Archer MR600 as access point

Hello, I've serious troubles configuring my old Archer MR600 as an access point, connected to my new main router Archer AX55!
The AX55 has an IP of 192 168.0.1, and an IP-range for clients from 192.168.0.10 to 192.168.0.254, DHCP enabled.
I switched the operation mode of the MR600 from 3G/4G to Router, configured an IP of 192.168.0.2, and disabled DHCP.
But every time I connect the MR600 with LAN to the AX55, the MR600 gets an IP within the configured range instead of using the static one.
What am I doing wrong? Any help very much appreciated! Cheers, Wolfgang
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi,
Verify that you have plugged the Ethernet cable into one of the pure LAN ports (LAN1 to 3) and not into the combined LAN/WAN port.
According to your description you configured the LAN Settings like shown in the screenshot below, right?
- Copy Link
- Report Inappropriate Content
Finally, I've got it to work as it should:
- disconnected the LAN connection between router and access point
- removed both from their power socket
- connected the access point to my PC and reset it to its initial settings
- switched the operation mode from 3G/4G to Router
- configured a static IP of 192.168.0.2
- disabled DHCP
- set subnet mask to 255.255.255.0
- connected LAN cable to LAN1 port of the access point
- powered the router on
- connected the LAN cable to LAN1 port of the router
The access point still has its static IP, and is also accessible via browser configuration again!
- Copy Link
- Report Inappropriate Content
Hi,
Verify that you have plugged the Ethernet cable into one of the pure LAN ports (LAN1 to 3) and not into the combined LAN/WAN port.
According to your description you configured the LAN Settings like shown in the screenshot below, right?
- Copy Link
- Report Inappropriate Content
Hi, thanks a lot, the wrong LAN/WAN port was the solution!
The connection works fine now, the only thing I can't do any more is to open the configuration site of my MR600 in the browser.
I get no response from IP 192.168.0.2 although I'm connected to this access point.
Is there any solution for this issue, or do I have to deal with it in this situation?
- Copy Link
- Report Inappropriate Content
If the MR600's LAN IP address is 192.168.0.2 and it is connected to your other router (to provide DHCP services to clients), then it should be accessible via 192.168.0.2.
But you have to be aware of one certain behavior of TP-Link routers.
If a TP-Link router senses a network on its WAN port that uses the same IP subnet as its own local network, then the router will automatically re-configure its own local network to another subnet.
Simply put, if LAN IP is 192.168.0.x and someone connects the WAN port to another network that also uses 192.168.0.x, then LAN IP automatically changes to something else, most likely 192.168.1.x. This might be what happened in your case
- Copy Link
- Report Inappropriate Content
Strange...!
Neither I can't find the MR600 in the AX55 childs list.
The only child that is "unknown" to me is an "IEEE Registration Authority" with an IP 192.168.0.53.
Maybe the MR600 is hidden behind this IP?
- Copy Link
- Report Inappropriate Content
If the LAN IP address of the MR600 is in another subnet than the AX55, then it won't show up on the AX55.
I am not aware of any logic that would change the router's LAN IP address to something random like 192.168.0.53.
As I mentioned previously, the logic that is implemented in TP-Link's routers is that it will automatically shift its own LAN subnet if there is a conflict between its LAN network and WAN network. I assume TP-Link implemented this to avoid inexperienced users running into network conflicts and then calling up their hotlines, complaining that their routers don't work.
- Copy Link
- Report Inappropriate Content
Anyway, as long as it works like it does now, I won't touch anything!
Thanks a lot for your support!!
- Copy Link
- Report Inappropriate Content
Hi@cwHome6768,
Thank you for contacting our community.
For details, you can refer to How to setup a TP-Link modem router as an Access Point
- Copy Link
- Report Inappropriate Content
Hi @Joseph-TP
Thanks for the hint! I referred to that link before, but I used the wrong LAN port (WAN/LAN instead of LAN1-3)
The picture under step 4 isn't clear at the point IMO.
I now have an internet connection now, but I would be glad if you could help me with the following points:
1. I configured my access point with a static IP 192.168.0.2, but I can't see this IP anywhere (IP scan, connected childs in router configuration)
2. Why can I no longer connect to 192.168.0.2 via the web interface?
3. What is a child "IEEE Registration Authority"?
- Copy Link
- Report Inappropriate Content
Finally, I've got it to work as it should:
- disconnected the LAN connection between router and access point
- removed both from their power socket
- connected the access point to my PC and reset it to its initial settings
- switched the operation mode from 3G/4G to Router
- configured a static IP of 192.168.0.2
- disabled DHCP
- set subnet mask to 255.255.255.0
- connected LAN cable to LAN1 port of the access point
- powered the router on
- connected the LAN cable to LAN1 port of the router
The access point still has its static IP, and is also accessible via browser configuration again!
- Copy Link
- Report Inappropriate Content
Hi@cwHome6768,
I am so glad to hear that you resolve the issue via yourself~!
It seems that there may be a conflict in the previous settings. Resetting and reconfiguring can sometimes save time and solve the problem quickly.
Your experience sharing will definitely be helpful to other users~!
- Copy Link
- Report Inappropriate Content

Information
Helpful: 0
Views: 862
Replies: 10
Voters 0
No one has voted for it yet.