Dead Port SG2016P v.1.20.9
Hi, I have with the SG2016P v1.20 exactly the same issue as described here:
https://www.reddit.com/r/HomeNetworking/comments/jmez6h/tlsg1016pe_switch_dead_port/?rdt=46162
Their solution is to reboot often the device or move to Unifi switches instead of TP-Link.
I somebody at TP-Link maybe looking into this issue? The original issue is 5 years old, i wonder why TP-Link is not adressing the issue? The device must be ablue to detect if the port is not working anymore.
Mor me also worked:
- Unplug / Plug Network Cable
- Disable and Enable again the Port
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @kidex
Thanks for posting in our business forum.
kidex wrote
Hi, I have with the SG2016P v1.20 exactly the same issue as described here:
https://www.reddit.com/r/HomeNetworking/comments/jmez6h/tlsg1016pe_switch_dead_port/?rdt=46162
Their solution is to reboot often the device or move to Unifi switches instead of TP-Link.
I somebody at TP-Link maybe looking into this issue? The original issue is 5 years old, i wonder why TP-Link is not adressing the issue? The device must be ablue to detect if the port is not working anymore.
Mor me also worked:
- Unplug / Plug Network Cable
- Disable and Enable again the Port
These are not the same model. I find it hard to relate them together. So, please stop integrating them into the same problem and saying that it is "5-year-old problem without a fix".
More facts to add, this SG2016 is a new product, and it is L2+.
And if you verify that the port is dead, physically, you can contact for RMA. The forum does not provide any support for RMA, but we can diagnose if you want to troubleshoot before the RMA.
And I find the word "dead" is not proper to describe it which makes it look like a hardware issue in the following description.
If you are using a third-party switch and that device got problems with ours, you should try other routers and switches before jumping to the conclusion that this is an issue with our switch.
Each switch got its own chipset and on-board controllers, which might have a problem in a million chance. But, you should try different devices at least.
And check the cable. I have iterated many times on the forum and in various troubleshooting guides.
- Copy Link
- Report Inappropriate Content
Hi @kidex
Thanks for posting in our business forum.
kidex wrote
Hi, I have with the SG2016P v1.20 exactly the same issue as described here:
https://www.reddit.com/r/HomeNetworking/comments/jmez6h/tlsg1016pe_switch_dead_port/?rdt=46162
Their solution is to reboot often the device or move to Unifi switches instead of TP-Link.
I somebody at TP-Link maybe looking into this issue? The original issue is 5 years old, i wonder why TP-Link is not adressing the issue? The device must be ablue to detect if the port is not working anymore.
Mor me also worked:
- Unplug / Plug Network Cable
- Disable and Enable again the Port
These are not the same model. I find it hard to relate them together. So, please stop integrating them into the same problem and saying that it is "5-year-old problem without a fix".
More facts to add, this SG2016 is a new product, and it is L2+.
And if you verify that the port is dead, physically, you can contact for RMA. The forum does not provide any support for RMA, but we can diagnose if you want to troubleshoot before the RMA.
And I find the word "dead" is not proper to describe it which makes it look like a hardware issue in the following description.
If you are using a third-party switch and that device got problems with ours, you should try other routers and switches before jumping to the conclusion that this is an issue with our switch.
Each switch got its own chipset and on-board controllers, which might have a problem in a million chance. But, you should try different devices at least.
And check the cable. I have iterated many times on the forum and in various troubleshooting guides.
- Copy Link
- Report Inappropriate Content
@Clive_A Thank you, I took now on the switch a different port, replaced the network cable, happend again. I will try if a exchange of the device is possible. - My assumption was, that, even if the hardware is newer, it might be a switch software issue. But lets see.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 479
Replies: 2
Voters 0
No one has voted for it yet.
