TL-SG1016DE Dropping DHCP for Clients
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I have a TL-SG1016DE Ver 3 with the latest firmware. It keeps dropping connectivity to cabled clients that turn off. The clients get the 169 default address. The only way to clear it is to drop the power and repower the switch. Have never had this happen on any other 1016's I have had. Switch power is connected to a Tripp-Lite rack mount UPS. Using the management tool to reboot doesn't clear it. Switch is connected to a Netgear which is connected to an Xfinity Xfi router. Clients that are on 24/7 keep their addresses. Only machines that turn off cannot get back on. There are all connected by Cat 8 Ethernet cables which I have switched out. Also, machines on the same network disappear from Windows 10 network. Wi-Fi from the Xfi always works so the problem lies in either the TP switch or the Netgear but clients I connect to the netgear do not have that problem and bouncing the Netgear doesn't clear it. Any suggestions?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @malda,
malda wrote
I've got the same issue with TL-SG1024DE 3.0, FW 1.0.1 Build 20180629 Rel.58591. After some time (days to weeks), DHCP for cable clients connected into this switch stops working. Reboot from web mgmt does not solve the issue, only unplugging the switch from electricity.
Here is a beta firmware that may fix the issue. If you are willing to try it, follow the link below to download the beta firmware for upgrading.
Note: copy the whole link below and paste in the address bar of your web browser for downloading
For TL-SG1024DE 3.0:
https://static.tp-link.com/2020/202012/20201222/TL-SG1024DEv3_en_1.0.1_%5b20201218-rel49852(Beta)%5d_up.rar
For TL-SG1016DE 3.0:
https://static.tp-link.com/2020/202011/20201111/TL-SG1016DEv3_en_1.0.1_%5b20201110-rel40807(Beta)%5d_up.rar
For TL-SG1016PE 1.0:
https://static.tp-link.com/beta/2021/202101/20210119/TL-SG1016PEv1_en_1.0.1_%5b20210114-rel37936%5d_up.zip
Edit: add beta firmware for TL-SG1016DE 3.0, TL-SG1016PE 1.0. It can be downgraded if the beta firmware doesn't help.
We'd encourage you to give us feedback on the case so that we can be confident of the solution here. Thank you!
- Copy Link
- Report Inappropriate Content
Dear @Da_Gunny_USMC,
It keeps dropping connectivity to cabled clients that turn off. The clients get the 169 default address. The only way to clear it is to drop the power and repower the switch.
So the issue is that the cable clients connected to the SG1016DE would be unable to get valid IP addresses from DHCP every time when they are restarted (powered off and then powered back on). As long as you restart the SG1016DE switch, these cable clients would obtain valid IP addresses at once. Correct?
When the issue happens, if you don't restart the SG1016DE switch, but just plug these cable clients directly to the Netgear switch or the Xfinity router, would they obtain IP addresses from DHCP properly? Is the setup like this: Xfinity WiFi router ------ one Netgear Switch ------ One SG1016DE switch ------ cable clients such as Windows 10 PCs?
To address the problem, it would be appreciated if you could help to capture the packets by referring to the following steps:
1) have two cable PCs (say PC1 and PC2) connected to the DHCP server through the SG1016DE, and install Wireshark on PC1 that is on 24/7
2) configure Port Mirror on the SG1016DE, you may refer to this instruction.
Note: select the port connecting to PC1 as Mirroring Port, while the uplink port connecting to the router and the port connecting to PC2 as Mirrored Port (enable both Egress and Ingress).
3) when the issue occurs on PC2, run Wireshark on the PC1 to capture all packets and then save the capture file for analysis.
Thank you for your cooperation and patience. Please feel free to let us know if you need any further assistance.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @Da_Gunny_USMC,
I'll have to get wireshark down and set that up.
Please feel free to contact us if you have any updates on this case. Thank you.
- Copy Link
- Report Inappropriate Content
Dear @Kongressman,
I have 1:1 the same trouble! DHCP in my case from pfSense. Anybody have working solution for this ?
We're interested in this issue, would you mind our senior engineer contacting you via the email address you registered in the community?
Or if you prefer to contacting us by yourself, please feel free to file a ticket to contact TP-Link support.
Thank you in advance for your time. Do let us know if you need any further assistance, we'll be glad to assist you.
- Copy Link
- Report Inappropriate Content
Hi,
I have a similar setup and am experiencing the same issue with a TL-SG1016DE (v3 with latest firmware); Client devices that power off are unable to obtain an IP from DHCP server, unless the TL-SG1016DE is power cycled (rebooting the TL-SG1016DE does not resolve the issue, switch has to be powered off and back on!).
Has a resolution to the issue been identified? Or is it a hardware fault?
Thanks.
- Copy Link
- Report Inappropriate Content
Dear @FireDZ,
I have a similar setup and am experiencing the same issue with a TL-SG1016DE (v3 with latest firmware); Client devices that power off are unable to obtain an IP from DHCP server, unless the TL-SG1016DE is power cycled (rebooting the TL-SG1016DE does not resolve the issue, switch has to be powered off and back on!).
Do your client devices run into sleep mode and they will be unable to obtain an IP after they recover from sleep mode?
Would that work if you unplug the client devices and then plug into other spare ethernet ports on the switch?
If you manually configure an IP on the client device, would the client device be able to access the switch and get an Internet connection?
Has a resolution to the issue been identified? Or is it a hardware fault?
Not yet, still trying to figure out the problem. It would be helpful if you could give us the chance to follow up with your case.
- Copy Link
- Report Inappropriate Content
Confirming the described behavior on v3 with an RTL8125B chip integrated on a TUF B550-Plus motherboard. Didn't have any issues before on the same port with an Intel I217-V on an Asus Z87-Plus. Also, it's quite rare, but I'm getting the same issue with my SONY KD-55XG8096 from time to time (not sure which NIC it uses). One common thing of these client devices is that tend to have a few errors in the RxBadPkt column (usually a single digit), while other devices have no errors at all.
Waiting for the issue to occur again, so I can try static IPs.
- Copy Link
- Report Inappropriate Content
So - just had another issue. I retired the whole rack to the garage and used TP-Link AV2000 powerline adapters to reach it. As soon as I plug the TL-SG1016DE in it takes down my entire network of 3 switches. Unplug the Ethernet cable (Cat 8) from the 1016DE and the network come back up. Using a DLink switch in place of the 1016DE works OK. Something is majorly wrong with the1016DE switch. Won't buy any of those again. Just ordered some QNAP 2.5GbE switches to replace the slower links since xFinity just upgraded their router to 2.5GbE. I had two of the 1016DE's previously and they worked great. Too bad quality control isn't there.
- Copy Link
- Report Inappropriate Content
Hello,
I've got the same issue with TL-SG1024DE 3.0, FW 1.0.1 Build 20180629 Rel.58591. After some time (days to weeks), DHCP for cable clients connected into this switch stops working. Reboot from web mgmt does not solve the issue, only unplugging the switch from electricity.
I can provide support & debug data, please contact me via mail.
Thank you & best regards,
Jan
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 5383
Replies: 21
Voters 0
No one has voted for it yet.