The results are in ....
It was the network switch! I replaced it with a new Netgear FS105 and everything just came alive. I can't tell you how relieved I am at this point.
Now, for the **full disclosure**
It probably wasn't the TP-Link switch's fault. It was entirely mine. I accidentally hooked the switch up to my 12v supply and it's a 5v switch. It may be salvageable but since I already sacrificed it's cable to the enclosure it was in and I don't have a spare 5v cable with the correct end on it, it could take a while before I know.
Doesn't matter now. It works and I'm on to the next thing, which in this case happens to be a mega-tree. I'm sure that will generate some more "wtf have I done wrong this time" questions!
Thanks for the help everybody.
Glad to know you got it working right.
For reference, the Fs105 switches come with a power supply that's something like 7 or 9v. But they do work fine on 12v power.they have an internal regulator that handles the 12v fine. I use these units(and their newer brother the gs105) all the time and regularly share a 12v DC supply to power them. They get very warm on 12v, that extra power needs to go somewhere. But I've yet to fry one or see any odd behavior.
--Jon Chuchla--
Sent from my iPhone using Tapatalk
I second what Jon said. The power supply can vary, for sure.
Under "normal use", these "green" switches can be fine in a non-critical environment (read "home") or a small office.
One thing I have noticed, but have not verified, is that some of the algorithms used to test if a port is being used require occasional bi-directional data to be present within a specific amount of time. A lot of what we use in DIYC is push only. Very little return data. This caused my green switches to close out the port, even if only for a few seconds, and therefore cutting the signal.
Troubleshooting can be a bear!!!
Glad to hear you found it.
