Shielded network cable is worthless and can actually make things worse if you don't have proper support for shielding and grounding across the board, from one end to the other with the cable and all equipment supporting it. Sticking a shielded cable into plastic network ports is basically going to turn the shielding into an antenna. Regular CAT5e/CAT6 will be plenty. Flat cables are garbage for anything longer than about 2-3 feet.
Good to know. I'll avoid shielded. The run is probably only 3 feet, but the cable is ~6.
The twisted pairs are needed to keep the little pixies from getting out of line. And if the flat cable has the little clips on the jacks on the same flat side of the cable, it's not even a poorly made network cable, it's a shoddy USOC cable where they reversed polarity on the tip and ring... but that's unlikely given it's already worked upstairs, so technically known good, but potentially dodgy.
As you said unlikely as it is working. It came with the routers and has been working for years. It still works back in the old location. Speed test and latency tests have alway been acceptable, so why mess with it. Until now.
As for testing WHY? You need to cut the wireless elements out of the equation when testing wired connections.
There are literally none. We've got a couple cell phones, a couple kindles, a couple chromebooks, a usb/wifi printer a few smart devices/IOTs.
Wait I take that back, there is one network port its on the wall mounted TV ... but is isn't connected. I did pull an ethernet wire to the basement when I added the TV outlet just incase.
These ridiculous 100% WiFi only setups are awful, no matter how good they're set up and easy to configure.
I agree that wired is objectively better. But, sometimes good enough is good enough; we aren't gaming, we aren't running high resolution high refresh rate webcams.
Wiring the house for Cat cable now would be a real PITA ... unless I could commandeer the phone lines. It was something I looked into to doing when we moved in ... and if everything else on my to do list gets done I still might. But right now it would only function as a wired backhaul for wifi mesh networking.
I've been in and out of building computers and gaming over my life and always prefered to hardwire stationary items and if I ever build there will be at least 1 drop in each room.
This said, relocating the cable modem, even though you connected it closer to the cable DMARC, there could be line quality issues with the coax and connectors you're using to change the wired location.
There are exactly zero new components added, some are relocated and some are removed.
On one hand, it's better to keep the cable modem closest to the point into the house, and ideally keep any (or as many) splitters or extension adapters out of the service line. Your cable modem should have a diagnostics page, you should check the modem status at both locations and compare.
I have used that before for other purposes I didn't think of it this time for some reason. No clue why. Perhaps I will try it the next time I move the modem back downstairs, though I suspect with a wired connected it would not do any good (if as I suspect the issue is electrical interference preventing a connection b/t the modem and the router).
As far as troubleshooting the wireless end, I'd try a wireless setup with everything in the new locations, but the cable modem in the known good old location and a known good cable (either coax or network) to bridge the new distance.
That sounds good on paper and might be practical with an IT department with those cables on hand. I would have to procure a cable that can not only stretch across the house but down and around 2 flights of stairs to link the new location and the old
... I would be left with a 100 foot cable in inventory. And these days buying something that the final disposition of is "in inventory" is a hard sell with the storage space police.
Thanks for the ideas. I'll probably ask the DW to grab a spare cable from her desk at work and see if a decent cable works.