| Home | |||||||||||||||||||||||||
| ** | 2/21/26 | Networking | |||||||||||||||||||||||
| Home | |||||||||||||||||||||||||
| Home | Gemini: Samba Share Connection Troubleshooting | ||||||||||||||||||||||||
| h_hh_ll | |||||||||||||||||||||||||
| Linux | network routing and Windows security. | ||||||||||||||||||||||||
| Windows | 1 | ping the Tailscale IP instead | If that works, map the drive using the Tailscale IP. | This is often much more reliable than local networking. | |||||||||||||||||||||
| Notes | |||||||||||||||||||||||||
| Template | |||||||||||||||||||||||||
| 2 | Windows | "Public" vs "Private" Profile | This is the most common reason a Windows machine can't ping a local Linux box. | ||||||||||||||||||||||
| Settings > Network & Internet > Ethernet | If Windows thinks your home Wi-Fi is a "Public" network, it silently drops outgoing discovery requests and incoming echo replies. | ||||||||||||||||||||||||
| Settings > Network & Internet > Wi-Fi | Ensure it is set to "Private". | ||||||||||||||||||||||||
| 3 | Subnet Mismatch | The "Hidden" Issue | |||||||||||||||||||||||
| 4 | Tailscale | Exit nodes > Allow local Network Access | If this is unchecked, Tailscale can sometimes "tunnel" all your traffic, making your local printer and local Samba shares invisible. | ||||||||||||||||||||||
| Preferences > Use Tailscale subnets | |||||||||||||||||||||||||
| Since Tailscale creates a virtual network interface (usually named tailscale0), we need to tell Samba it's allowed to listen there. | |||||||||||||||||||||||||
| 1 | Update Samba to Listen on Tailscale | By default, Samba sometimes only listens on the physical ethernet/Wi-Fi interface. | |||||||||||||||||||||||
| sudo nano /etc/samba/smb.conf | |||||||||||||||||||||||||
| [global] | |||||||||||||||||||||||||
| interfaces = lo enp2s0 tailscale0 | |||||||||||||||||||||||||
| bind interfaces only = yes | |||||||||||||||||||||||||
| sudo systemctl restart smbd nmbd | Restart Samba | ||||||||||||||||||||||||
| 2 | Verify the Samba User | Windows 11 requires a password-protected account for SMB by default. It will often reject "Guest" or "Anonymous" logins without a fight. | |||||||||||||||||||||||
| sudo smbpasswd -a your_debian_username | Make sure you've explicitly added your user to the Samba database: | ||||||||||||||||||||||||
| 3 | Clear Windows Credential "Ghosting" | Windows 11 is notorious for "remembering" a failed login attempt and refusing to ask for a password again, resulting in that "Check the spelling" error. | |||||||||||||||||||||||
| Open the Start Menu and type "Credential Manager" | |||||||||||||||||||||||||
| Go to Windows Credentials | |||||||||||||||||||||||||
| Look for any entries related to your Debian IP or Tailscale IP. Remove them. | |||||||||||||||||||||||||
| Try to map the drive again using the Tailscale IP: \\100.x.y.z\YourShareName. | |||||||||||||||||||||||||
| 4 | Check the "Path" Permissions | If the folder you are sharing is inside your /home directory, Linux permissions can be very protective. | |||||||||||||||||||||||
| sudo chmod 755 /path/to/your/shared/folder | |||||||||||||||||||||||||
| 5 | Final Diagnostic Command | If it still fails, run this on the Debian machine while trying to connect from Windows: | |||||||||||||||||||||||
| sudo tail -f /var/log/samba/log.smbd | Watch the output. If you see "Permission denied" or "Connection refused from [IP]", it will tell us exactly which side is slamming the door. | ||||||||||||||||||||||||
| ? | Which error does Windows show now? Is it still "Check the spelling," or has it changed to "Enter Network Credentials" or "Access Denied"? | ||||||||||||||||||||||||