Hello,
My MacBook Pro M1 never detects my ethernet cable without me using a lot of effort as you'll read below. When I plug the cable in my old Asus laptop it works flawlessly.
I use a cheap AliExpress hub as a medium between the ethernet cable and the MacBook, but the hub works flawless. How do I know that? When at work, I plugged an ethernet cable with my cheap hub into my MBP and I saw in the network section that the ethernet cable is detected and it worked perfectly. Furthermore the hub detects the ethernet cable by showing a constant orange light and a flashing green light.
The weird thing is, after I tried the above at work and I took the MBP home, my own ethernet cable was automatically detected too.
I formatted the MBP (for other reasons) and tried to connect my ethernet cable and again, it couldn't find it. I visited work again and forgot my own cheap hub. I used a new Satechi hub to connect an ethernet cable to my MBP. At first, it didn't work, but after replugging it, the MBP detected a network(USB 10/100/1000 LAN, a different one than the network I had with my own cheap hub, which had something in the line of IPv6 or something). Now I'm home and my own ethernet cable is (again) not detected through my cheap hub by my network. Also not through the USB 10/100/1000 LAN that was automatically created when using the Satechi hub at work.
Now I suspect that my own cheap hub uses a different network (name) than the Satechi hub but that shouldn't be the problem. I don't understand why I need to plug my hub in at the job for it to work at home. Does someone have the answer? As you can understand, I don't want to take my MBP to work every time I reset the network settings/format the MBP for it to be able to work at home again using the ethernet. I would like to just plug it in at home through my own hub and to work directly. I think it is an issue in the default network settings but I can't figure it out.
This happened from the moment I had the MBP with Big Sur. I'm updated to the latest version of Monterey and I still have the same problem.
My MacBook Pro M1 never detects my ethernet cable without me using a lot of effort as you'll read below. When I plug the cable in my old Asus laptop it works flawlessly.
I use a cheap AliExpress hub as a medium between the ethernet cable and the MacBook, but the hub works flawless. How do I know that? When at work, I plugged an ethernet cable with my cheap hub into my MBP and I saw in the network section that the ethernet cable is detected and it worked perfectly. Furthermore the hub detects the ethernet cable by showing a constant orange light and a flashing green light.
The weird thing is, after I tried the above at work and I took the MBP home, my own ethernet cable was automatically detected too.
I formatted the MBP (for other reasons) and tried to connect my ethernet cable and again, it couldn't find it. I visited work again and forgot my own cheap hub. I used a new Satechi hub to connect an ethernet cable to my MBP. At first, it didn't work, but after replugging it, the MBP detected a network(USB 10/100/1000 LAN, a different one than the network I had with my own cheap hub, which had something in the line of IPv6 or something). Now I'm home and my own ethernet cable is (again) not detected through my cheap hub by my network. Also not through the USB 10/100/1000 LAN that was automatically created when using the Satechi hub at work.
Now I suspect that my own cheap hub uses a different network (name) than the Satechi hub but that shouldn't be the problem. I don't understand why I need to plug my hub in at the job for it to work at home. Does someone have the answer? As you can understand, I don't want to take my MBP to work every time I reset the network settings/format the MBP for it to be able to work at home again using the ethernet. I would like to just plug it in at home through my own hub and to work directly. I think it is an issue in the default network settings but I can't figure it out.
This happened from the moment I had the MBP with Big Sur. I'm updated to the latest version of Monterey and I still have the same problem.
Last edited:
