AX73 v2 automatically assigns an IP address(DHCP) not working for LACP firmware 1.0.8 Build 20230616
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.AX73 v2 automatically assigns an IP address(DHCP) not working for LACP firmware 1.0.8 Build 20230616
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello!
Today I upgraded my router with the latest firmware 1.0.8 Build 20230616 rel.65817 and i discovered that my windows server using LACP no longer gets assigned an ipv4 address. I tried to manually set an ip form my subnet but i have not internet acces. Neither ipv6 works. Neither factory resetting my router works.
I downgraded to an older version and it is working fine. It is a 1.0.8 Build 20230616 problem.
I am stuck with 1gbps link. :(
Is there any solution to this problem?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, glad to share with you the solution to the LACP issue after updating firmware to 1.0.8 build 20230616, please test and let us know if the issue can be resolved in your case.
LACP of Archer AX73 V2 doesn't work after upgrading firmware to 1.0.8 Build 20230616
- Copy Link
- Report Inappropriate Content
Bump!
- Copy Link
- Report Inappropriate Content
Hi, thank you very much for posting on TP-Link Community.
For testing purpose, could you please share with us the screenshots of your LACP settings on your Windows Server? You could refer to the instruction below to share the screenshots:
https://portal.novoserve.com/index.php?rp=/knowledgebase/73/Configuring-LACP-on-Windows-Server-2016-or-Windows-Server-2019.html
In addition, we would like to escalate your case to the support engineers, and they will help follow it up, if you are willing to do further analysis, please check your inbox and respond.
- Copy Link
- Report Inappropriate Content
@Sunshine Thank you for your reply! I sent a reply to support.forum@tp-link.com with my .bin file as requested in the email.
- Copy Link
- Report Inappropriate Content
@Shai_Hulud I'm having the same issue with the Brazilian Version >>> Firmware Version: 1.0.8 Build 20230616 rel.65817(5553) >>> Hardware Version:Archer AX73 v2.20
Sad that TP-Link got us that broken update... I'm my case, not even my HP managed switch is able to get an IP address...
- Copy Link
- Report Inappropriate Content
Thank you very much for the reply, our senior engineer will continue to follow up your case via email, if there is any update, please also let us know.
- Copy Link
- Report Inappropriate Content
Hi, do you mean the version displayed on your product label is BR version?
The HP Switch is connected to Archer AX73 LAN port and all the wired devices connected to the HP Switch cannot obtain IP address?
If you connect those wired client directly to Archer AX73 LAN port, will they still work fine? and are you also using LAG or LACP?
In addition, please let us know the model number of your HP Switch and your wired client devices.
- Copy Link
- Report Inappropriate Content
@Sunshine Yes, I'm from Brazil and this is my product page: ( https://www.tp-link.com/br/home-networking/wifi-router/archer-ax73/ ) and my support page: ( https://www.tp-link.com/br/support/download/archer-ax73/ ) .
Sadly, I can't find an older firmware file do downgrade...
Yes, the HP Switch is directly connected to the AX73, but only the HP Switch can't get an IP address, all other device works fine, but they can't connect to the AX73 since it is my DHCP server. if I turn off LACP in the AX73 and in the HP Switch, then things get back to normal...
I'm using LACP, not Static LAG.
Everything was working fine before the update, my HP Server was connected to my HP Switch using LACP (that is still working fine), and then the HP Switch was connected to the AX73 using LACP (that stopped working in the latest update). HP switch is :
| HPE OfficeConnect Switch |
| 1820 8G |
| J9979A |
Thanks in advance, please let me know of an solution.
- Copy Link
- Report Inappropriate Content
@Fearlipe Yea, there is definitely a problem with link aggregation. I tried today to use Static LAG insted of LACP but that doesn't work either. I am patiently waiting for a hotfix or a new firmware.
- Copy Link
- Report Inappropriate Content
Hi, thank you very much for the detailed information.
To assist you efficiently, I've forwarded your case to the TP-Link support engineers, who will contact you with your registered email address later. Please pay attention to your email box for follow-up.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 1438
Replies: 11
Voters 0
No one has voted for it yet.