Fix Nautilus not opening SMB shares after Ubuntu 22.04

Here's the exact scenario. You're running Ubuntu 22.04 (maybe upgraded from 20.04), and you try to open a network location in Nautilus. You click on a Samba share in the sidebar, or type smb://server/share in the address bar. The spinner spins for 30 seconds to a minute, then you get a popup: "Unable to access location – Failed to retrieve share list from server". Or maybe it just hangs forever until you kill Nautilus. This happens most often when connecting to older NAS devices, Windows 7/10 machines, or any SMB server using SMBv1 protocol. I've seen it on Synology NAS boxes with legacy shares, and on Buffalo LinkStation devices. The file manager worked fine before the upgrade — now it's busted.

Why it broke

The root cause is Ubuntu 22.04 ships with a newer version of gvfs and samba-libs that default to requiring SMBv2 or higher. Many older NAS devices and Windows machines still offer SMBv1 as a fallback. When Nautilus (via gvfs) tries to connect, it sends an SMBv2 request. The server doesn't understand that, so it responds with a protocol negotiation failure. The client then tries to fall back, but the timeout is long, and sometimes the fallback itself fails. The fix isn't to downgrade gvfs — that's messy. The real fix is to tell the Samba client to accept SMBv1 again by adjusting the client minimum protocol setting in your smb.conf file. SMBv1 is old and insecure, I know. But if you need to reach that specific NAS in a private network, this is the practical solution. The alternative is updating the NAS firmware, which isn't always possible.

The fix: add client min protocol to smb.conf

Open a terminal. You can press Ctrl+Alt+T to get one.
Back up the current smb.conf file before editing. Run:
```
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf.backup
```
This saves you if you mess up. The file is at /etc/samba/smb.conf on a standard Ubuntu install.
Edit the file with a text editor. I use nano because it's simple:
```
sudo nano /etc/samba/smb.conf
```
You'll see a section called [global] near the top. If it doesn't exist, don't worry — we'll add it.
Scroll to the [global] section. Add this line right after [global]:
```
client min protocol = SMB2
```
Wait — I hear you. You said SMBv1 was the problem. Here's the nuance: setting SMB2 tells the client to accept SMB2 and higher, but also allows SMBv1 negotiation as a fallback. If you want to allow only SMBv1 (less secure), you can use NT1 instead. For most older NAS drives, SMB2 is enough. If you still get errors, change it to NT1.
Important: If your smb.conf doesn't have a [global] section, just add these lines at the top of the file:
```
[global]
client min protocol = SMB2
```
Save the file. In nano, press Ctrl+O to write out, then Enter to confirm. Press Ctrl+X to exit.
Restart the SMB services. Run:
```
sudo systemctl restart smbd
sudo systemctl restart nmbd
```
After running those, you should see no errors in the terminal. If you get a "unit not found" message, don't panic — smbd and nmbd might not be installed as services. In that case, just reboot your machine instead. Reboot with:
```
sudo reboot
```
After reboot (or service restart), open Nautilus again. Click on the network location or type smb://server/share in the address bar. The share should open within a few seconds. If it worked, you'll see the folder contents.

Still failing? Check these things

If the share still doesn't open, here's a list of other common culprits.

Firewall — Ubuntu's firewall (ufw) might block Samba ports. Check with:
```
sudo ufw status
```
If it's active, allow Samba with:
```
sudo ufw allow samba
```
Port 445 (SMB) and 139 (NetBIOS) need to be open.
Check the server name — Use the IP address instead of the hostname. So instead of smb://nas, try smb://192.168.1.100. If that works, you have a DNS/mDNS issue.
Check authentication — Some NAS devices require a username and password. In Nautilus, when prompted, don't skip the username field. Use the format WORKGROUP\username if the NAS uses a workgroup name.
Check gvfs version — There's a known bug in gvfs 1.48.x where SMB shares with certain characters in the share name (like spaces) fail entirely. If your share name has spaces, rename it on the NAS to use underscores or hyphens. This sucks, but it's a real problem.
Check if the share is mounted via fstab — If you have a CIFS mount in /etc/fstab, that might interfere with Nautilus's own mount. Temporarily comment out the fstab entry by putting a # at the start of the line, then reboot and test.
The nuclear option: install cifs-utils — Sometimes gvfs-smb just won't cooperate. Install the classic CIFS tools:
```
sudo apt install cifs-utils
```
Then mount the share manually from the terminal to see the real error:
```
sudo mount -t cifs //192.168.1.100/shared /mnt -o username=youruser
```
The error message from mount is usually more specific than Nautilus's.

I've seen this exact problem at least a dozen times since 22.04 launched. Nine times out of ten, adding client min protocol = SMB2 to smb.conf fixes it instantly. The other times it's a firewall or DNS thing. If none of these work, your NAS might genuinely only speak SMBv1 and you're out of luck — in that case, consider replacing the NAS hardware or running a Windows VM as a bridge.