I figured this out too. However after some time it still drops out, says connected but wont load any webpages is this the same for you? i really wish this was fixed already. im personally going to an apple store to just bounce ideas with one of the techies to see if we come up with something..... i'm not hopeful.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
macOS Monterey 12.1 Thunderbolt Ethernet problems
- Thread starter sirozha
- Start date
- Sort by reaction score
I don't think that DHCP makes any difference in a MacBook Pro running Big Sur. I'm using an Apple Thunderbolt/Gb Ethernet dongle for a port that is exclusively a static IP. By deleting all the adapters and letting the OS re-add them on a reboot it worked...until the next reboot which happened to be on the occasion of a live, multi-camera stream event featuring our college president and city mayor. The system is back on the bench as I try to figure this out. I was using a Anker USB Ethernet Dongle/hub (DHCP) for our streaming and that seems not to have a problem.
[follow-up] Going back and re-adding Thunderbolt Ethernet allowed the dongle to connect correctly. Disclaimer: this may have to be done after each reboot.
Ric
Last edited:
I was using the Caldigit Thunderbolt 3 Mini Dock. i figured it would be a good one to go with as it was sold in apple stores.
In Big Sur, Thunderbolt-based Network adapters worked fine - using DHCP or static IP. They even worked fine with Monterey 12.01. The issue started with Monterey 12.1.
I prefer using Thunderbolt-based network adapters to USB-based ones. It seems there is no issue in Monterey 12.1 and 12.2 with USB-based network adapters. The DHCP issue in 12.1 and 12.2 is only with Thunderbolt-based Network adapters. This is such an esoteric edge case that most people reading this have no earthly idea what we are talking about. Apple support can’t even understand what the issue at hand is. I’m not hopeful this will ever be fixed.
I know it’s a thunderbolt dock, but is the Ethernet adapter in it USB-based or Thunderbolt based? You can pull up the system hardware in macOS and see if the network adapter is listed under Thunderbolt or under USB.
it is Definitely a Thunderbolt and not USB. However i also have a USB dock and that also sufferes from the same issues.
I have a USB-C based dock and two USB-C network adapters. None of them suffers from the DHCP issue in macOS 12.2
I recently upgraded to 16" MBP M1 Max from 16" 2019 intel based and ethernet isn't being detected. I am using Caldigit Usb C Pro dock. anyone able to figure out what's the issue?
it doesn't even connect via static IP as well. I tried that!
Update: restarted my Mac 3 times and now its working with DHCP! I did update the firmware for the dock though!
Last edited:
Hi quick update for my Issue, I found out that My Antivirus was creating a Firewall that was causing the Connection created through the Ethenet Port on the thunderbolt dock to drop out. since removing that firewall it has Worked Perfectly. So if any of you are having similar issues to what i was having possibly try that.
It looks like the macOS 12.2.1 update has fixed the Thunderbolt Ethernet adapter issues. My Apple 27" Thunderbolt LED display's Ethernet adapter (showing as Display Ethernet in macOS Network properties) has been working for 3 days straight with DHCP enabled without having disconnected after the 14" MacBook Pro goes to sleep. Hopefully, the issue has been fixed.
I'm still having occasional flashing of the Apple's 27" Thunderbolt LED display (picture on / picture off) after the Mac wakes up from sleep, which I first noticed in macOS 12.1, but a simple disconnect of the Thunderbolt cable between the Mac and the Thunderbolt 4 dock and then reconnecting of the cable fixes that problem. That screen flashing problem doesn't occur every time after the Mac wakes up from sleep, but it's annoying.
Overall, I think I'm going to change my approach to upgrading macOS going forward. Apple seems to be incapable of releasing stable major macOS versions, with something breaking after every early dot release. The only reason I went with Monterey was that the 14" MacBook Pro came with Monterey. If the obvious bugs in Monterey get fixed by next summer/fall, I will stick with Monterey and not upgrade to the next macOS version next fall. I think I will start upgrading to the next major macOS release one year behind the release of the .0 version. It seems to me that the new macOS gets pretty stable with most bugs squashed right before the scheduled release of the next major version (which is usually in early fall).
I'm still having occasional flashing of the Apple's 27" Thunderbolt LED display (picture on / picture off) after the Mac wakes up from sleep, which I first noticed in macOS 12.1, but a simple disconnect of the Thunderbolt cable between the Mac and the Thunderbolt 4 dock and then reconnecting of the cable fixes that problem. That screen flashing problem doesn't occur every time after the Mac wakes up from sleep, but it's annoying.
Overall, I think I'm going to change my approach to upgrading macOS going forward. Apple seems to be incapable of releasing stable major macOS versions, with something breaking after every early dot release. The only reason I went with Monterey was that the 14" MacBook Pro came with Monterey. If the obvious bugs in Monterey get fixed by next summer/fall, I will stick with Monterey and not upgrade to the next macOS version next fall. I think I will start upgrading to the next major macOS release one year behind the release of the .0 version. It seems to me that the new macOS gets pretty stable with most bugs squashed right before the scheduled release of the next major version (which is usually in early fall).
That's exactly my approach. I upgraded for Catalina to Big Sur in January 2022 after Monterey has been already been released. Sadly, it does appear for Apple to take year and stabilize a major OS release.
The issue with the Thunderbolt-based Ethernet adapters was not resolved in macOS 12.2.1. After three days of the DHCP working, I just had the issue today again. I had to go back to the static IP to get the network connectivity back.
This is pathetic, Apple! Network connectivity is one of those features that should be tested extensively before the release of every macOS update. Pathetic is the only word I have for Apple at this point for this screwup. I can’t even report this to Apple (I tired) because the Apple Care geniuses have no clue what a Thunderbolt-based Ethernet adapter is or what DHCP is. Simply hopeless.
I have hd no luck with DHCP w/ Manual Address or Static. It still stops working. However, if I bounce the interface it coems back online. I have an Apple Support case opened and a Feedback case open. They are diagnosing the TCPdump and sysdiagnose I sent them. This is clearly an issue with the IP Stack on macOS. I also checked and it affects IPv6 also.
I don't know if it is relevant to your problem, but I just noticed this new support document on the CalDigit website:
Ethernet port on the TS4 or TS3 Plus does not work properly
Might be worthwhile giving the settings they suggest a try.
Ethernet port on the TS4 or TS3 Plus does not work properly
Might be worthwhile giving the settings they suggest a try.
I think I finally found the fix for this issue. I needed to disable the AVB/EAV mode. This is a relatively new standard that reserves the Ethernet bandwidth for latency / jitter sensitive audio/video traffic to provide low-latency and low-jitter medium for that traffic. However, the Ethernet switch that the Ethernet adapter supporting this standard is connected to must also support this standard in order for this feature to work. Almost no consumer-grade Ethernet switches support this standard, and not even all Cisco enterprise-class switches support it. For example, Cisco 3560 Series switches (or lower-end / older switches) do not support this standard. This standard is supported in Cisco 3650, 3850, and 9000 Series switches.
So, when I disabled this standard under the Thunderbolt Ethernet adapter and re-enabled DHCP, the Thunderbolt Gigabit Ethernet adapter (built into the Apple 27" Thunderbolt Display) connected, obtained DHCP, and has been working for a week now without any issues. Please see the attached screen shot to see how you can disable AVB/EAV in macOS System Preferences -> Network.
So, when I disabled this standard under the Thunderbolt Ethernet adapter and re-enabled DHCP, the Thunderbolt Gigabit Ethernet adapter (built into the Apple 27" Thunderbolt Display) connected, obtained DHCP, and has been working for a week now without any issues. Please see the attached screen shot to see how you can disable AVB/EAV in macOS System Preferences -> Network.
Sirozha, a related question: Realtek 8153 based USB Ethernet adapters seem to have an issue with high cpu loads and/or low throughput, due to using the AppleUserECM driver. Does the orginal Apple Thunderbolt Gigabit Ethernet adapter (which internally uses a Broadcom PCIe NIC) combined with the TB3-TB2 adapter also have this issue, or does it offload properly, resulting in low CPU load and proper gigabit throughput?
Is anyone else still having an issue with DHCP not working on an M1 Pro/Max MBP with macOS 12.2.1?
It's happening with both of my CalDigit T/S3+ docks and an Anker USB-C Gigabit ethernet adapter. When I plug my 2019 16" i7 MBP into the same devices, I get an IP address via DHCP and everything works, but my M1 almost always uses a self-assigned IP address. It seems to get an IP via DHCP on rare occasion if I have WiFi turned off, but even then it's very inconsistent. Static IPs seem to be okay for now, but one of my adapters is used at multiple locations with different network subnets, so a static IP is less than ideal for a long-term solution.
It's happening with both of my CalDigit T/S3+ docks and an Anker USB-C Gigabit ethernet adapter. When I plug my 2019 16" i7 MBP into the same devices, I get an IP address via DHCP and everything works, but my M1 almost always uses a self-assigned IP address. It seems to get an IP via DHCP on rare occasion if I have WiFi turned off, but even then it's very inconsistent. Static IPs seem to be okay for now, but one of my adapters is used at multiple locations with different network subnets, so a static IP is less than ideal for a long-term solution.
I did, but unfortunately I'm not seeing any AVB/EAB mode checkbox on that screen for any of my docks/ethernet adapters. I also tried CalDigit's recommendation, but that didn't have any effect either. I verified Green Ethernet is disabled on the managed switch that it's plugged into as well just in case.