Solution Cannot Access the Internet when connecting an Archer AX6000/AX11000 to Starlink Gen 2
This Article Applies to:
Archer AX6000 V1
Archer AX11000 V1
Archer AX90 V1
Archer GX90 V1
Archer AX3200 V1
Issue Description/Phenomenon:
Starlink Gen 2 system generally includes a Starlink Terminal, a Starlink router, and an Ethernet adapter. This Ethernet adapter will give you the ability to hard-wire the system and use non Starlink equipment with the system, and it is a must when connecting a non-Starlink router. However, SpaceX/Starlink doesn't guarantee performance with a non-Starlink router, the FAQ notes:
If you want to connect our TP-Link router like Archer AX6000/AX11000 to the Starlink Gen 2 system but unfortunately fail to connect to the internet, please go through this article to figure it out.
Available Solutions:
Solution 1
For Archer AX11000/AX6000
Upgrade and install the below beta firmware on the Archer AX11000/AX6000, then connect the WAN/Internet port to the Starlink Ethernet adapter to observe if the internet works. Download and unzip the firmware file, then you will see the “.bin” firmware file, launch a web browser and go to the Advanced > System Tools > Firmware Upgrade page to upload the firmware file:
Archer AX11000_V1.0_221209 (Updated on Dec 12, 2022)
Archer AX6000_V1.0_230303 (Updated on Mar 15, 2023)
Note:
1. Please be sure you have read the Terms and Conditions for TP-Link Beta Firmware before proceeding!
2. This beta version can be applied to the EU and US versions.
For Archer AX90/GX90/AX3200
Step 1 Connect the Starlink Gen 2 Ethernet Adapter to the 1 Gbps WAN/LAN Port on the Archer AX90/GX90/AX3200 instead of the 2.5 Gbps WAN/LAN Port, then check if the internet will work.
Step 2 Visit http://tplinkwifi.net and log into the web GUI of the router, go to Internet, and select 1 Gbps WAN/LAN as the WAN/Internet port.
Note: The 2.5 Gbps WAN/LAN port and 1 Gbps WAN/LAN port cannot be used as the WAN port at the same time. Once we choose to use the 1 Gbps WAN/LAN port as the WAN port for internet service, the 2.5 Gbps WAN/LAN port will be used as the LAN port by default.
Solution 2
Try modifying the Internet Negotiation Speed to 100 Mbps Full Duplex, then save and reboot the system to determine if the internet works.
For Archer AX6000, go to Advanced > System Tools > System Parameters page, scroll down to the bottom of the page, you see find Internet Port Negotiation Speed Setting, change it to 100 Mbps Full Duplex:
For Archer AX11000, go to Advanced > Network > Internet page, scroll down to the bottom of the page, you see find Internet Port Negotiation Speed Setting, change it to 100 Mbps Full Duplex:
Solution 3
If you happen to have a network switch, try to plug the switch between the Starlink Ethernet Adapter and the Archer AX6000/AX11000 WAN, that is Starlink router --- Ethernet Adapter --- Switch --- Archer AX6000/AX11000, then confirm if the internet works.
Feel free to comment below whether the issue gets fixed with the above solutions. We will also investigate further and update the thread when there is a final solution, welcome to subscribe!
More Articles:
How to Connect and Set up a TP-Link Router to Starlink Internet
-------------------------------------------------
Have other off-topic issues to report?
Welcome to > Start a New Thread < and elaborate on the issue for assistance.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Not very tech savvy
I'm trying to connect my Archer AX6000 to our new starlink but not having any luck.
When I try solution 1 and try to unzip the file it comes back saying its an unvalid zip file...I downloaded the newest Winzip and no sucess.
When I try solution 2 for some reason my AX6000 does not have "Internet Port Negotiation Speed Setting" option...not sure why that is.
I don't have a network switch to see if it works with that.
I do know that the cat cable connection from the starlink adapter to the computer is providing LAN internet connection.
Any other suggestions?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
When you tried to install the beta firmware on the AX6000, did you unzip it first? Please check and ensure you downloaded the firmware successfully, try to download it one more time, and unzip it again.
When changing the Internet Negotiation Speed to 100M, please try to start both the Starlink and the AX6000, then monitor again.
If none works, I would like to escalate your case to our support engineers to investigate further, please check your registered email and follow it up, thank you.
- Copy Link
- Report Inappropriate Content
V1 = V1.6, you can find the explanation on the website:
https://www.tp-link.com/us/support/download/archer-ax11000/#Firmware
- Copy Link
- Report Inappropriate Content
@Kevin_Z
Guys you have got a seriously terrible consistency problem.
If I go to the firmware downloads page for the AX11000 V1 and choose hardware version, and select V1, then click the firmware button my top choice is as follows:
Header (presumably file name): Archer AX11000(US)_V1_220221
Published Date: 2022-04-29
File Size: 37.99MB
If I select hardware version V1.60, then click the firmware button my top choice is as follows:
Header (presumably file name): Archer AX11000(US)_V1.6_220221
Published Date: 2022-05-27
File Size: 37.99MB
The name and the published date would make one think this is indeed a different file yet clicking either download button gives me "Archer AX11000(US)_V1_220221.zip"
So which is it guys, are both hardware versions supposed to use the same firmware? If so why have the dropdown at all for the hardware version, this just adds to confusion? Why the different header on the site for the name of the download? Why the different publish date?
- Copy Link
- Report Inappropriate Content
Thank you very much for letting us know about the confusion caused by the AX11000 firmware versions.
There are both V1.0 and V1.6 versions in the United States, and the V1.6 version is only sold in the United States, so you can find them both when choosing firmware.
The Version Number that is listed on the bottom is indicative of where the product was manufactured or where the product is sold. This simply allows our vendors and company to better identify and track products if there were to ever be an issue with a specific version. There could be delays when uploading and publishing the firmware for different hardware versions, that's why you find the publish date is different for V1.0 and V1.6.
For your purposes, please install the latest firmware for Hardware V1.6 on yours.
- Copy Link
- Report Inappropriate Content
@Kevin_Z For anyone who has a Gen2 Starlink and AX-90...this totally works. I tried several other things, starting with the 2.5G connection and couldn't get it to work. Tried on and off with the bypass on the starlink router...and no luck. But just moved to the 1GB port and boom!
- Copy Link
- Report Inappropriate Content
Solution 2 (Force 100Mbps Full Duplex) works for my AX11000, but I'd really like to see a better solution that will allow me to take full advantage of my hardware. I'll wait hopefully for a non-beta firmware update.
Thanks for keep this thread alive! Please continue to do so until we know that there will (or won't) be any further motion towards a better solution.
- Copy Link
- Report Inappropriate Content
Thank you very much for updating us that your issue got resolved by forcing the Internet Negotiation to 100M.
Can I know what is the bandwidth you paid for the internet?
- Copy Link
- Report Inappropriate Content
@Kevin_Z It took me way too much troubleshooting before landing on a link to this page via Reddit.
I have the Archer AX6000 and initially was googling for resolutions around the DNS issue specifically. When the router is connected to the startlink gen 2, it does pick up an IP via DHCP along with the correct subnet, gateway, and starlink's DNS servers. But, as others have reported, only google.com was resolving with the DNS. I tried manually updating the DNS servers (they use 1.1.1.1 as the default) to other google DNS servers like 8.8.4.4 but that did not work from the router. I then tried updating my PC's local DNS for the ethernet adapter to use 8.8.4.4 directly and THAT also did not work. I could ping all of the DNS servers (and other IPs) directly but DNS just would not work. This is why I thought it was something to do with the DNS connectivity or configuration. I even backed up my current config and fully reset the router to factory settings just to make sure none of my config was messing it up. But alas, no dice. Nothing would work. I wanted to post this detail in case anyone else find's this troubleshooting beneficial.
With regard to the fixes on this page:
- I did not want to try the beta firmware for various reasons including some other's feedback on this post. Plus I was just about out of time to continue troubleshooting.
- Setting the WAN port to use 100Mbps did indeed work but, as expected, this limited the bandwidth to 100Mbps via a speedtest. I just invested all this money in Starlink to get OVER 100 Mbps in our rural area so this was not a good option. I also invested in the Archer AX6000 after reading a post that said it was one of the best routers FOR starlink in a somewhat complex home deployment. I tried the 1000Mbps setting and it no longer worked.
- I did have a TP-Link gigabit switch so I plugged that in, in between the router WAN port and the Starlink port and it did not work at that point. The router was not able to resolve an IP address via the Starlink DHCP. As a side note, when Starlink is NOT in bypass mode (i.e. it is working as a local router), then the AX6000 picks up a local IP without any issues when connected via the switch (i.e. 192.168.100.5). But when Starlink was put into bypass mode thus disabling the Starlink local router, it was NOT picking up the DHCP issued IP from Starlink. When I plugged the AX6000 WAN port directly back into the Starlink router port it DID get the IP from the Starlink DHCP (i.e. 100.113.73.X) but again the internet didn't work because of the DNS issues noted above. I then captured the DNS, subnet mask, gateway and DNS info being issued by Starlink and configured the router to use a static IP WAN setup utilizing this config information. I then reintroduced the TP-Link switch between the AX6000 and the Starlink port with the static IP info intact and everything worked as expected. I am able to clock speeds well above 100Mbps from various devices downstream from the the AX6000. Now, I understand DHCP and if Starlink decides to reissue IPs or my lease ends, etc. etc. I may be having to go through this exercise again. Therefore, I am REALLY hopeful that TP-Link can fix the firmware for this (very expensive) router so that the WAN port works correctly when directly connected to Starlink AND with DHCP enabled. Please keep working on this for us. Thx.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 10
Views: 14629
Replies: 64