CalDigit TS4 Ethernet Not Working? A Host-First Fix

Start with the failure that is actually visible

Before changing a setting, record four results: whether the laptop charges, whether one simple USB device works, whether a monitor works, and whether the operating system shows a wired-network interface. If several dock functions disappeared together, use the whole-dock troubleshooting path. If those functions survive and only wired networking is absent, keep the diagnosis on this Ethernet branch.

Next look at both ends of the network cable. A link light or a reported wired connection means the computer and switch have established part of the route; it does not prove that DHCP supplied an address or that internet access works. No link at all points first to the cable, selected switch or router port, dock controller availability, or host connection. A self-assigned address, connected-without-internet state, or intermittent link belongs to a later branch.

Save work before disconnecting the dock, and safely eject dock-connected storage. Change one variable at a time. Replacing the host cable, network cable, switch port, driver, and network service together may restore access, but it destroys the evidence needed to prevent the failure from returning.

Confirm that the host can expose the TS4 Ethernet controller

CalDigit specifies that the TS4's 2.5GbE controller requires a Thunderbolt host or a USB4 host that supports PCIe. A plain USB-C 3.x connection can still expose some USB functions and may support a display or charging, yet leave the TS4 Ethernet controller unavailable. That pattern is a capability limit, not proof that the network jack has failed. CalDigit's TS4 specifications state this host requirement explicitly.

Identify the exact laptop and the exact port used for the upstream cable. On Windows, confirm Thunderbolt support or ask the computer manufacturer whether that USB4 port exposes PCIe. If the port is ordinary USB-C without PCIe tunneling, stop trying unrelated Ethernet drivers: CalDigit recommends a separate USB Ethernet adapter for that host route. Replacing the TS4 with another unit would not add a missing host capability.

For a Thunderbolt Windows computer, confirm that the TS4 is approved in the system's Thunderbolt management path when approval is required. Use the TS4 host port and the supplied or explicitly supported Thunderbolt cable. A cable can carry charging or lower-rate USB data without establishing the complete controller path expected by the dock.

Build a known-good wired baseline

Connect the TS4 directly to a known working port on the router or switch with a known working network cable. If practical, confirm that same cable and switch port with another computer or adapter. Keep Wi-Fi enabled until the wired interface appears; then identify the wired connection by name rather than assuming an internet page loaded through Ethernet.

Check whether the operating system received a normal address from the network's DHCP service. A link with no valid address is different from no detected controller. If workplace policy permits, pause a VPN or security filter only for the controlled comparison and restore it immediately afterward. Do not reset every network setting merely because a speed test is low.

The TS4 supports 2.5GbE but can negotiate with traditional 1GbE equipment. A 1Gb switch port is therefore not a failure. Record the negotiated link rate, then separate local-network performance from the internet plan, remote server, storage speed, VPN, cable category, and traffic on the rest of the route.

On macOS, repair the TS4 network service before replacing the dock

CalDigit's current TS4/TS3 Plus support article addresses a dock that cannot obtain a DHCP address or carries no network traffic despite being connected correctly. Its macOS sequence removes old or unused Thunderbolt Ethernet Slot services associated with the dock, creates a new service for the active Thunderbolt Ethernet Slot, and waits for the connection state to update. Record any manual address, DNS, proxy, VLAN, or workplace configuration before deleting a service so it can be restored accurately. CalDigit's Ethernet troubleshooting sequence is the source for these model-specific steps.

If the recreated service remains disconnected, CalDigit next instructs users to disconnect both the Thunderbolt and network cables from the dock for 30–45 seconds, reconnect them, and test again. This is a scoped cable cycle for the stated Ethernet symptom, not a universal reset procedure and not a reason to erase unrelated Mac network services.

For a persistent Energy Efficient Ethernet compatibility problem, CalDigit documents manual hardware settings: choose the speed that matches the attached network equipment, use full duplex or full duplex with flow control, avoid the Energy Efficient Ethernet option, and leave MTU at 1500 unless the network administrator requires something else. Do not select 5GbE or 10GbE for the TS4; CalDigit lists its ceiling as 2.5GbE.

On Windows, separate host capability, controller detection, and drivers

First check whether Windows detects the TS4 Ethernet controller. If it does not, return to the host-port and Thunderbolt-approval check before installing software. CalDigit says USB-C 3.x hosts do not expose the TS4 controller, while a USB4 host needs PCIe support. A driver cannot create that missing hardware route.

When the host route is supported but Windows does not provide the controller correctly, use only CalDigit's TS4 Ethernet package for the applicable operating system. CalDigit also publishes a separate January 2025 announcement for ARM-based Windows support; that driver solves a defined ARM compatibility gap and should not be presented as a universal update for every Intel or AMD computer. CalDigit's ARM Windows notice points to its current downloads area.

If the adapter appears but the link is unstable, CalDigit's model-specific guidance includes disabling Energy Efficient Ethernet in the adapter's advanced properties. Record the original value before changing it. The same support article calls out Auto Smartport on some Cisco switches as a possible compatibility factor; change managed-switch settings only with the network administrator, not as a blind home-user step.

Treat slow or intermittent Ethernet as a different problem

A controller that never appears, a link that never comes up, a connection that lacks an address, and a link that slows or drops after sleep are four different symptoms. For intermittent failures, note whether only Ethernet disappears or the entire dock reconnects. Also record whether the failure follows sleep, cable movement, a VPN connection, a particular switch port, or a sustained local transfer.

Test a repeatable local task before relying on an internet speed test. A transfer to a known local server still includes both computers' storage and network adapters, but it removes the internet service and remote server from the path. Compare like with like: same files, endpoints, cable, switch port, and power state. The goal is to identify which segment limits the route rather than claim that a 2.5GbE label guarantees 2.5Gbps application throughput.

Avoid generic firmware or network resets as the first response. They can change several conditions at once and may remove managed settings. Use an update only when CalDigit or the laptop manufacturer identifies it for the exact TS4, host, operating system, and symptom.

Escalate with a record that CalDigit or IT can reproduce

Record the laptop model, operating-system build, host port, whether the route is Thunderbolt or USB4 with PCIe, TS4 serial number, upstream cable, network cable, router or switch model and port, controller name, negotiated link rate, assigned address, and whether displays, USB, and charging survive. Include the result of the known-good cable and switch-port test.

Replace hardware only when the evidence supports it. If the TS4 controller is absent on a plain USB-C host, use a supported USB Ethernet adapter or a different host route. If the controller appears and the same dock, cable, and network port fail across supported computers after CalDigit's model-specific steps, the dock becomes a more credible suspect. That distinction prevents a capability mismatch from being mistaken for a defective Ethernet jack.

Related questions