CentOS Stream 10 – Common Problem 246 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Older clients cannot connect to a Samba share with NT_STATUS_INVALID_NEGOTIATION errors.

Environment & Reproduction

Affects legacy scanners and embedded devices still using SMB1 after recent Samba updates.

Root Cause Analysis

Samba 4 in CentOS Stream 10 disables SMB1 by default for security, breaking legacy negotiation.

Quick Triage

Run smbclient -L //server -m NT1 to confirm SMB1 negotiation and inspect /var/log/samba.

Step-by-Step Diagnosis

Run: smbclient -L //server -m NT1 -U%; testparm -s | grep -i ‘server min protocol’.

Solution – Primary Fix

Replace clients with SMB2/3 firmware, or set server min protocol = SMB2_02 if compatibility is required.

Solution – Alternative Approaches

Place legacy clients on an isolated VLAN with an SMB1 gateway host instead of weakening the main server.

Verification & Acceptance Criteria

smbclient -m SMB3 succeeds from modern clients and legacy clients negotiate over SMB2_02 if enabled.

Rollback Plan

Revert smb.conf to server min protocol = SMB3_00 once legacy devices are decommissioned.

Prevention & Hardening

Inventory SMB clients quarterly and schedule firmware upgrades for legacy hardware.

Related Errors & Cross-Refs

Related to NTLMv1 deprecation and signing-required mismatch errors.

Related tutorial: View the step-by-step tutorial for centos-stream-10.

View all centos-stream-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Samba documentation and Red Hat Samba migration notes.