An Ethernet jack on a rugged-tablet dock is not, by itself, evidence that a managed network will recognize the tablet or that its business application will recover after docking. Specify which network adapter supplies the wired connection, which MAC address that adapter presents, how the site admits that identity, and what the application does when the link changes. A cable link light is only the first checkpoint.
This question is narrower than selecting a dock for ports and power. The rugged-tablet docking guide covers the physical bundle; the enterprise Wi-Fi identity guide concerns wireless admission. Here the procurement decision is whether the exact tablet, dock, NIC, firmware and network policy make wired identity and reconnection predictable.
Identify the adapter the network will actually see
A tablet may use an internal wired NIC, a dock’s Ethernet controller or a separate USB Ethernet adapter. These are not interchangeable procurement descriptions. Request the tablet and dock part numbers, dock connection type, installed NIC/driver identifiers, supported operating-system build and any BIOS or firmware settings that govern dock LAN. Determine whether a particular accessory merely exposes a port or provides its own adapter. The network team should identify the expected interface in the operating system and the address reported by the switch or admission service, not infer it from the shape of an RJ-45 socket.
Some platforms offer MAC address pass-through: the dock’s external NIC may present a selected address from the tablet instead of its own physical address. This is a model-and-configuration feature, not a universal Ethernet property. As a bounded third-party example, the Dell Latitude 7230 Rugged Extreme Tablet service manual lists a MAC Address Pass-Through setup option that replaces an external NIC’s address with the selected system address. The manual cautions that listed options can depend on installed devices; it does not establish support for an AIDC GO tablet or every dock. Verify the proposed dock, NIC driver, firmware and IT policy together.
Record separately the tablet’s system pass-through address, the dock’s physical adapter address and the MAC observed on the live wired interface. Do not edit or clone addresses as a general fix: such a change can disrupt networking and may violate the site’s identity rules. Dell’s separate pass-through address guidance for its laptops and docks describes checking the address with and without a dock and notes a static-IP configuration limitation. That guidance is not a compatibility statement for the 7230 tablet or the proposed dock. Use the applicable model documentation and the network team’s records for the quoted device.
Separate a live link from network and application acceptance
After the adapter appears, check link speed and stability, the assigned IP configuration, DNS resolution, the required VLAN or admission result, and reachability to the actual application endpoint. If the site uses wired 802.1X or a MAC-based admission rule, obtain that site’s exact policy and the adapter’s supported driver behavior; a remembered MAC address is not proof of authentication or device trust. If network identity changes when a tablet moves between docks, an allowlist, DHCP reservation or asset inventory may refer to the wrong identifier.
A successful ping is still not a completed field transaction. The application may retain a stale session, continue using another interface, lose an in-progress upload or retry a write whose server-side result is already committed. Define what the user must see before leaving the dock: a current server response, the intended asset or task record, and a visible result for pending work. The offline-capture guide uses a barcode workflow to explain uncertain receipts; the wired adapter’s identity is a separate check.
Walk one tablet through two docks
Editorial example, not a customer deployment or measured test: Tablet T-17 performs an inspection offline, then returns to desk dock D-A to submit record R-17. It later moves to vehicle dock D-B. The IT plan expects the same managed tablet identity at both locations. Before acceptance, the team records the physical NIC and presented MAC at D-A and D-B, the network admission decision, and the application’s response when R-17 is submitted. These labels are teaching identifiers, not evidence of a supported AIDC GO configuration.
At D-A, a lit port and an assigned IP address do not close the test: confirm that R-17 exists once in the backend and that the tablet shows an acknowledged result. At D-B, repeat the identity and admission checks. If the dock presents a different MAC, determine whether that is an intended dock-identity design or a missing pass-through capability; do not silently treat it as the same managed endpoint. If a submit times out while undocking, query R-17 in the system of record before retrying. If it is already committed, another submit could create a duplicate.
Repeat with the screen locked, after a dock reconnect and after a controlled network outage. A device that resumes the Ethernet link but leaves the application showing an old success banner needs an application recovery rule. Conversely, a working application over Wi-Fi does not prove the wired dock path works; log the actual interface used at each checkpoint.
Write the acceptance evidence into the quotation
Ask the supplier and integrator for the exact tablet SKU, dock SKU and revision, NIC and driver identifiers, supported firmware/OS combinations, whether MAC pass-through is supported on this pair, and any limits on dock LAN or simultaneous wireless service. Ask the customer’s network owner for the admission method, expected identity, addressing and application endpoint. If pass-through is not required, document the alternative: a dock-specific managed identity may be perfectly suitable when the site provisions each dock deliberately.
The witness test should capture: physical connection; detected NIC; presented MAC at two docks; switch or admission result; IP/DNS and application connectivity; one known pending record submitted exactly once; undock/re-dock; and recovery from an interrupted submission. The pass criterion is not a universal MAC value. It is the agreed, repeatable identity and a correctly acknowledged business record for the proposed configuration.
AIDC GO’s rugged-tablet category can begin a form-factor shortlist, but it does not claim MAC pass-through, a particular dock NIC or wired admission behavior for every model. Share the proposed tablet/dock combination and network policy with Integration Support, or contact AIDC GO with the exact acceptance record required before ordering.