FAQ
TL;DR: 30 PCs on the LAN; one Win10 Pro can't open Samba shares: "Guest access in SMB2 is disabled by default." Fix by enabling secure authentication or the temporary insecure guest logons policy, then map drives with stored credentials. Printers may still require credentials and permissions. [Guest access in SMB2 is disabled by default]
Why it matters: This helps Windows 10 users fix \server access errors to Ubuntu/Samba shares and restore file and printer sharing reliably.
Quick Facts
- Windows 10 (1709+) blocks unauthenticated SMB guest sessions by default; use accounts or enable “Enable insecure guest logons” if required. [*Guest access in SMB2 is disabled by default*]
- SMB1/CIFS is deprecated and unsafe; prefer SMB2/SMB3 on both Windows and Samba servers. [*Stop using SMB1*]
- Adding a Windows Credential for \\192.168.14.100 restored drive mapping on the affected PC. [Elektroda, turek77, post #17476828]
- Matching workgroup names aren’t required when connecting via \\IP; browsing and access are separate. [Elektroda, turek77, post #17471272]
- Instead of disabling Defender Firewall, allow File and Printer Sharing on Private networks. [*File sharing over a network in Windows*]
Why do I get "You do not have access... unauthenticated guests" on Windows 10?
Windows 10 blocks guest SMB access by default for SMB2/SMB3. That message appears when the server expects guest access. Use real user credentials or temporarily enable the "Enable insecure guest logons" policy. Microsoft notes, "Guest access in SMB2 is disabled by default." [Guest access in SMB2 is disabled by default]
How do I enable insecure guest logons (temporary workaround)?
- Open gpedit.msc → Computer Configuration → Administrative Templates → Network → Lanman Workstation.
- Set "Enable insecure guest logons" to Enabled and apply.
- Reconnect to \server\share. Use this only while you transition to authenticated access. [Guest access in SMB2 is disabled by default]
How do I store Samba credentials in Windows so access works?
- Open Control Panel → Credential Manager → Windows Credentials.
- Add a Windows credential: Internet address = server IP or name, Username and Password = Samba user.
- Reconnect the share or map a drive. Windows will use this credential without prompting. [Credential Manager]
Ping works but \\192.168.x.x fails—what does that mean?
Ping only tests ICMP reachability. SMB access can still fail due to guest restrictions, credentials, or firewall rules. Test using the full UNC path to a share, like \192.168.14.100\share. Ensure File and Printer Sharing is allowed on the Private profile. [File sharing over a network in Windows]
Should I enable SMB1/CIFS to fix access?
No. SMB1 is obsolete and risky; leave it disabled. Instead, use SMB2/SMB3 and proper credentials. Microsoft states, "SMBv1 is not installed by default." Update Samba if needed to support modern protocols. [Stop using SMB1]
Which Windows services must be running to access network shares?
Ensure the Workstation service is running, as it handles SMB client connections. Open services.msc and verify Workstation is set to Automatic and Started. Forum experts also ask to check this when diagnosing share issues. [Elektroda, jprzedworski, post #17463710]
I can see computers in Network, but I get Access Denied—why?
Discovery and access are separate. You may see devices but still be blocked by guest restrictions or missing credentials. Connect directly using \IP\share and supply a valid account, or add a Windows Credential. Access can be denied even when the directory is visible. [Elektroda, turek77, post #17465499]
How do I map a network drive when browsing fails?
Use the UNC path directly.
- In File Explorer, right‑click This PC → Map network drive.
- Enter \192.168.14.100\share and check "Connect using different credentials."
- Enter the Samba username and password and finish. [Map a network drive in Windows]
Windows never asks for a username/password—how do I change that?
Windows uses cached credentials. Open Control Panel → Credential Manager → Windows Credentials. Remove or edit entries for the server name or IP. Reconnect the share and select "Use different credentials" when mapping to enter the correct account. [Credential Manager]
Why can’t I access a shared printer even though drives now work?
Printer shares may still require authentication and matching permissions. Add the printer via \host\printer using a valid account. Confirm your user is allowed on the printer share. In the case discussed, four PCs printed fine while one remained denied until credentials were addressed. [Elektroda, turek77, post #17476828]
What Samba settings help Windows 10 clients connect securely?
Create named users and require authentication. In smb.conf, use security = user, set server min protocol = SMB2, and avoid guest-only shares. If you must allow guests, do so intentionally and understand the risks. [Samba Guest Access]
Do workgroup names have to match to access Ubuntu Samba shares?
No. Accessing by \IP or DNS works regardless of workgroup. Matching names mainly affect browsing visibility. The server and the client just need compatible SMB and valid credentials when authentication is required. [Elektroda, turek77, post #17471272]
Is there a command-line way to test access with credentials?
Yes, use net use. Example:
net use \192.168.14.100\share /user:USERNAME PASSWORD /persistent:no
If it connects, your credentials and SMB path are correct. You can then map the drive in Explorer. [net use]
Edge case: Enabling SMB1 makes Network browsing appear—should I keep it?
No. SMB1 may restore legacy browsing, but it remains insecure and unsupported. Keep SMB1 disabled and fix authentication or DNS instead. Modern discovery and access work without SMB1, and the old Computer Browser relied on SMB1. [Stop using SMB1]
