Set SMB dialect ranges separately for client and server roles

Source facts

Microsoft documents separate minimum and maximum SMB dialect settings for client and server roles, configured through Group Policy or PowerShell. The documented prerequisites include Windows Server 2025 or Windows 11 version 24H2 or later, with the appropriate administrative permissions. Microsoft also describes examining a network capture to see the dialects requested and negotiated by the endpoints. Microsoft documentation.

Applicability

Inventory the actual client and server releases and the devices that must connect. Review the peer capabilities and every required application path before proposing a narrower negotiation range.

DSE recommendation

Write the intended client range and server range separately. Ask the file-service owner to identify peers that might fall outside either range, including appliances and occasional maintenance clients. Preserve the current settings and define an explicit rejection test for an unsupported peer.

Verification

Reconnect representative clients under controlled conditions and record the negotiated dialect at both ends. Test the excluded case and confirm the result matches the approved policy. Keep failed connections visible as compatibility findings and resolve unexpected exclusions before applying the restriction to a wider server group.

Official references

Microsoft Learn: Manage SMB dialects in Windows and Windows Server 2025. Source reviewed September 8, 2026.