Are the random ports failing on the server switch, and could this pose a safety risk?
Are the random ports failing on the server switch, and could this pose a safety risk?
The person in charge at my job allowed me to collect some items he wanted to discard. One of the things I took was a Dell PowerConnect 2716 switch, which I had only used with three ports and everything functioned properly. Later, I tried adding another cable and realized it wasn’t working. After inspecting other ports, some didn’t perform well either. Could this indicate an issue that might lead to a fire? Perhaps loose wires creating short circuits? Ty
It will begin a fire by using the switch’s ports, giving you many options for sockets if the connection isn’t working. The signal comes from where you’re plugging in, which devices you’re linking to, and whether the cables are intact.
The Ethernet cables have been reliable for a while, performing well. The power cable is a C13, 220V, with the switch having its own PSU that connects to two computers—one cable goes from the router and the other two go to the PCs. The signal quality is decent on the active ports. I’m a bit cautious after hearing news about people getting burned from phone chargers or electrical bike batteries, so I assume Dell should be solid against such issues.
First assess whether those ports are genuinely broken or simply set to disable by default. They might be placed in a VLAN or configured to reject your network card. It’s likely the switch supports web management—check the manual on page 33 for instructions on accessing the interface: https://dl.dell.com/manuals/all-products...716_user's guide_en-us.pdf.
The device runs in Unmanaged Mode and needs to switch to Managed Mode before any configuration. Ensure the switch is fully functional in that mode (LED should stop blinking). To activate Managed Mode, wait for the LED to cease blinking, then press the corresponding button. The switch will restart and display the LED for about 90 seconds before stabilizing. Once it remains lit, configuration can proceed.
The default IP is 192.168.2.1 with 'admin' as username and an empty password. Consider adding another IP (e.g., 192.168.2.2) within the same range and subnet (255.255.255.0). Connect your Ethernet cable to both devices, then open a browser and enter 192.168.2.1 to test connectivity.
Visually check the ports: all eight contacts should be aligned, not touching or shorted. Clean any dirt or oxidation from the contacts. The port may have an isolation transformer behind it—some switches include multiple transformers for protection. If a transformer appears faulty (possibly damaged by a power surge), replacing it might restore functionality. A video showing internal components is available at 1:20 in the referenced guide.
If the issue persists, faulty ports could stem from hardware damage or configuration errors. When you can, consider purchasing an unmanaged switch with more ports for better value (around $20–30).
Great discovery! It was indeed in managed mode, but even after turning it off, those ports still aren’t functioning. It might be worth purchasing it for $14 if you’re comfortable soldering. Since I’m not very skilled at that, I’d skip the repair attempt. If it’s safe to use with damaged ports, I’d just keep using it—I don’t need all those connections anyway.
In my view, managed mode activates the management interface for configuration purposes. After saving settings, the system reverts to unmanaged mode, though those changes stay active only when you can no longer reach the management panel. The button essentially serves as a request to enable access, not a true switch between modes. It’s designed to let you verify port status and connections without affecting the device’s operation. The guide I referenced confirms this interpretation. Overall, it’s safe to use, though any issues would likely be hardware-related.
It's strange I'm having trouble accessing the web interface. I disconnected all cables from the switch and then connected directly between the PC and the switch, but the connection to 192.168.2.1 remains broken. I attempted to hold the Managed Mode button for 30 seconds to reset it, yet I still can't establish a connection.
Also set your network card to receive an IP in the same range. It’s likely it’s getting an automatic IP from the router’s DHCP server, but when you plug it directly into the switch, no such server is present. That’s why manual assignment is necessary. The recommended default is 192.168.2.1; you can try 192.168.2.2 or 192.168.2.100 (avoid .1 at the end) with a subnet mask of 255.255.255.0. Consult the manual to confirm if this IP can be changed—some devices have updated defaults. If not, check the switch for a reset jumper or internal reset button. The linked video isn’t detailed enough to see these steps. Refer to the manual, though it may not advise altering defaults. Proceed carefully. Wait until the indicator stops flashing, then press the button and wait up to about 90 seconds for it to stabilize before trying access. Also note there’s a firmware update available for this model: https://www.dell.com/support/home/en-us/...nnect-2716 You should be able to install it via the web interface or using a free TFTP client if needed.
I configured a fixed IP address of 192.168.2.100 with the gateway at 192.168.2.1, yet the switch isn't reaching 192.168.2.1. I'll reset it again and then try opening it if it doesn't work. Subnet is set to 255.255.255.0. Updated: I forgot to return it to managed mode. Now it functions properly, and it includes a built-in cable test. The ports appear dead in a square shape—ports 9, 10, 11, and 12 seem affected, possibly due to a burnt G4P109 behind them.
With a solid soldering station or iron, you can desolder two and swap them to test if the remaining four ports work. This helps identify whether the issue lies with the transformer. If it fails, it’s likely the transformer itself; otherwise, it might be a faulty custom IC inside the heatsinks—leave it as is. Alternatively, you could repurpose it as a 12-port switch without major concern.