AX3000 can not access docker containers on LAN
I can no longer access my Docker containers on LAN after changing my router - if I put back my old one, it works.
I have a "server" (192.168.1.40) where I host Docker containers with Docker for Windows, and I used to be able to access the containers on it from my LAN with ip and port (e.g. access Portainer on 192.168.1.40:9000). I tried to use telnet to check for the port, but it does not work with my new router, but if I change the router back to my old one, it successfully connects: telnet 192.168.1.40 9000
I can use Remote Desktop to connect to the server, but I can not access my Docker containers.
What setting should I modify to be able to access my containers? I even tried to factory reset the router and connect to the container on teh default DHCP IP, but it did not work.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Are you able to ping 192.168.0.40 from another PC/laptop in this network? Please check and confirm the firewall on Windows is disabled, I understand that there is nothing changed on Windows but there are cases that the firewall and network permission will change when you connect to a new network.
You can follow this guide to change the network to be private then confirm:
https://www.tp-link.com/support/faq/3072/
- Copy Link
- Report Inappropriate Content
Please login to the web GUI of the AX3000 and confirm what is the LAN IP address, if it is 192.168.0.1, then you can try changing it to be in the same IP subnet as the Docker containers:
https://www.tp-link.com/support/faq/2013/
If you are sure the IP address of the Docker containers is 192.168.1.40, then change the LAN IP of the AX3000 to 192.168.1.1, then reboot to confirm.
- Copy Link
- Report Inappropriate Content
Thank you for your response!
I am using 192.168.0.1 as my router IP, and 192.168.0.100-255 as my DHCP range (under 100 I am using static IPs).
The Docker containers are running on the 192.168.0.40 server in bridge network mode, so I am using its ports to reach the containers, but it only works with my old router.
- Copy Link
- Report Inappropriate Content
Are you able to ping 192.168.0.40 from another PC/laptop in this network? Please check and confirm the firewall on Windows is disabled, I understand that there is nothing changed on Windows but there are cases that the firewall and network permission will change when you connect to a new network.
You can follow this guide to change the network to be private then confirm:
https://www.tp-link.com/support/faq/3072/
- Copy Link
- Report Inappropriate Content
Thank you so much! The problem was that Windows set the network profile to public, setting it to private solved my issue!
- Copy Link
- Report Inappropriate Content
Good job.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 803
Replies: 5
Voters 0
No one has voted for it yet.