
It seems all of this hasn't yet proven that this is an issue on the PC. I wonder if I should try giving the PC a static IP. Out of curiosity, when it was still working, I tried renewing and releasing the DHCP lease via Command Prompt and it had no issues. As soon as I turned on the wifi, it connected and got an address immediately. Then I fired up a game and when I quit back to the desktop, I didn't have a IP address anymore. For the first while, everything was working beautifully. It also worked well with the MacBook but the PC rarely got an ethernet address through it.

FWIW, before I had this setup, I had a Powerline adapter.
/internet-speed-test-sites-2626177-d7cb37ea9e644605981049ffe09d2357.png)
Yes, connecting the MacBook directly to the outdoor ethernet cable works like a charm. but it's probably worth buying better shielded cables for that as the gear's expensive enough that connecting it with a $1 cable is a false economy if it ever drops due to EM noise in the cabinet. The basic network cable testers show each pin, it's frustratingly easy to get a rj45 crimped that looks fine but one pin isn't working:Īlso - as most people say, premade cables are so cheap it's not worth the time of making them, just have a bag of 15cm, 30cm, 50cm and 100cm and various colours, and they always just work. On long cables, getting the correct 568 a or b standard matters, on very short cables you should but it'll probably work anyway as there's so little cable there will be less crosstalk anyway. 10/100 uses pins 3-mbit requires all 8 pins - so a duff pin sometimes results in a cable doing 10/100 but not gigabit.

Check your cables with a individual pin tester - it sounds like cable build issues to me.
