SMB shares become unreachable after enabling jumbo frames on mixed‑vendor switch

Environment

Home lab: Debian 11 file server (Samba 4.13) with a 1GbE NIC, mixed-vendor managed switches (vendor A and vendor B) between server and Windows 10 clients, jumbo frames (MTU 9000) configured on server and vendor A switch only.

Symptoms

Windows clients intermittently fail to open SMB shares from the Debian server; file copy sessions hang at 0% or stall after a few MB transferred. Some clients can list directories while others get 'Network path not found.'

Observations

Server reports no NIC errors; dmesg shows no driver faults. tcpdump on server shows packets with MTU-sized fragments arriving but some clients' retransmissions appear after long delays. Vendor B switch interface counters show high rates of oversized/fragmented frames and intermittent CRC errors on the trunk between vendor A and vendor B switches.

Already attempted

Rolled back MTU to 1500 on one Windows client and it restored SMB access immediately. Rebooted vendor B switch and problem persisted. Temporarily set Samba socket options (SO_RCVBUF/SO_SNDBUF) to default, no effect. Enabled SMB2/3 only on server.

Question

What diagnostics and reversible configuration changes can confirm whether mismatched MTU/jumbo frame handling across mixed‑vendor switches is causing SMB failures, and what safe remediation steps restore SMB connectivity without data loss?

Post timeline

COMMUNITY RESPONSES

Verified community troubleshooting

0 replies

No answers yet..

Showing 0 of 0 community responses

AI DIAGNOSTICS

Incident analysis

Updated 2d ago• Trouble ID

Most likely causes

Partial jumbo frame support: one or more switches in the path do not support MTU 9000 or have inconsistent configuration causing frame drops. 95%

Misconfigured trunk/aggregation: an 802.1Q trunk or LACP link between vendor switches may have MTU or fragmentation offload mismatches. 80%

NIC offload mismatch: server NIC using large segment offload (TSO/GSO) producing jumbo packets that an intermediate switch mishandles. 65%

Summary

Symptoms point to path MTU/fragmentation issues crossing a segment that does not consistently support jumbo frames (vendor B switch). SMB (particularly older clients or NetBIOS components) is sensitive to dropped or malformed large frames. The fact that reducing MTU on one client immediately restored connectivity indicates the problem is frame-size related, and switch counters showing CRC/oversized frames implicate the intermediate vendor B device or an Ethernet trunk misconfiguration.

Suggested Fixes

Diagnostic step 1

Set MTU to 1500 on server and both switches (vendor A and vendor B) and verify SMB reliability to confirm MTU is the factor (reversible).

Diagnostic step 2

Collect packet captures on server and on an affected Windows client while reproducing the hang; look for retransmissions, ICMP fragmentation-needed, and mismatched frame sizes.

Diagnostic step 3

Check and align NIC offload settings: temporarily disable TSO/GSO on the server (ethtool -K <iface> tso off gso off) and retest SMB to see if large segments cause the issue.