ZimaCube Pro Thunderbolt Windows Direct Connect: 169.254 IP

Bottom Line: 169.254.x.x Is the Direct Thunderbolt Network—Use That IP, Not the LAN IP

On ZimaCube Pro, Thunderbolt direct connect behaves like a network link. The current official guide says the direct path receives a 169.254.x.x address, while the normal LAN keeps its own IP. To get Thunderbolt performance, open the dashboard or SMB share using the address assigned to the Thunderbolt path.

ZimaCube console showing multiple 169.254 addresses and a separate LAN address — The ZimaCube console showed two 169.254.x.x link-local addresses alongside the normal LAN address, confirming separate network paths.

macOS Connect to Server dialog using an SMB path to a 169.254 ZimaCube address — On macOS, the direct path was tested by connecting SMB to the 169.254.x.x address assigned to the Thunderbolt link.

Do Not Use “40 Gbps” as the Expected ZimaCube File-Transfer Number

The old thread spent a lot of time debating 20 vs 40 Gbps. Current Zima documentation is clearer: the PC Direct guide describes ZimaCube Pro Thunderbolt direct connection as up to 20G for this use case. A 40 Gbps Thunderbolt 4 link rating is not the same thing as guaranteed application throughput.

macOS Finder copying a large Windows ISO over a direct ZimaCube SMB connection — A Finder transfer was used to test practical throughput on the direct ZimaCube connection rather than relying only on the negotiated link label.

ZimaOS Files web interface uploading a Windows ISO during Thunderbolt testing — The web Files interface was also tested, helping separate application-transfer behavior from the raw network link.

ZimaOS dashboard showing traffic on eth2 during a file transfer — The dashboard showed transfer traffic on eth2, one clue that the active path was not necessarily the Thunderbolt interface the tester expected.

On Windows, First Prove the Peer-to-Peer Adapter Exists

Windows should expose a Thunderbolt/USB4 peer-to-peer network adapter. If the adapter exists but the browser cannot open the ZimaCube link-local IP, you have moved past “cable not detected” and into IP/routing/interface-priority troubleshooting.

Windows browser timing out when opening a ZimaCube 169.254 link-local address — Windows could see the Thunderbolt network interface but the browser timed out when opening one of the ZimaCube 169.254.x.x addresses.

Second Windows browser timeout against another ZimaCube 169.254 address — A second link-local address also timed out, showing that link negotiation alone did not prove the Windows IP path was usable.

Windows Network Connections showing a USB4 TM P2P Network Adapter for the ZimaCube direct link — Windows exposed the direct link as a USB4 peer-to-peer network adapter, confirming that the Thunderbolt/USB4 networking device existed.

Link-local IPv4 addresses are defined by RFC 3927. They are valid for the directly connected link and are not routed like normal LAN addresses.

When LAN and Thunderbolt Are Both Connected, Test the Exact Interface

Temporarily disable the ordinary LAN/Wi-Fi path on the client if necessary, then reconnect through the 169.254.x.x address. Once direct access works, re-enable other interfaces and make sure your SMB/dashboard shortcut still points to the Thunderbolt address. The current ZimaCube Thunderbolt direct-connect guide explicitly warns that LAN and Thunderbolt use different IPs.

ZimaOS Network Manager showing two Thunderbolt links negotiated at 20 Gbps — ZimaOS displayed both Thunderbolt links at 20 Gbps. Current ZimaCube direct-connect documentation also describes up to 20G for this use case.

Thunderbolt link ratings describe the interface, not guaranteed application throughput. Intel’s Thunderbolt 4 overview is useful for separating link capability from the ZimaCube-specific direct-connect implementation.

Measure Real Throughput, Not Only the Negotiated Link

Copy one large file and watch which interface carries the traffic. SMB, browser upload, storage speed and client-side implementation can all limit real transfer rates below the negotiated link speed.

For current hardware context, see the ZimaCube 2 product page and NAS file-sharing guide.