Failed to mount Windows share: Connection timed out

Question

I was able to connect a few months ago by my Ubuntu 16.04 to Windows shared server driver of my institute using the "connect to server" option on a desktop panel using smb:// and the server IP address.

Now when I try to connect again it give me this error message:

Unhandled error message: Failed to mount Windows share: Connection timed out

What could be happened/changed to give this error?

Does that have to do with updating software? The samba is already at the newest version!

Solution 1

The suggestions here work i.e. add in the [Global] section of the smb.conf file

client min protocol = SMB2
client max protocol = SMB2

Most of the computers on my network run Ubuntu 16.04 and the problem was getting the error message.

Unable to access location. Failed to mount Windows share: Connection Timed Out.

when connecting to a newer machine running Ubuntu 20.04. The new machine could see the network and connect to any machine on it, but not the other way around, i.e. the older machines running Ubuntu 16.04 could not access the Ubuntu 20.04 machine and responded with

Unable to access location. Failed to mount Windows share: Connection Timed Out.  

Solution 2

Edit and add the below entries to /etc/samba/smb.conf, under [global] It should look like

[global]
client min protocol = SMB3
client max protocol = SMB3

Comments

[CijcoSistems]

Where are you trying to connect from? Publicly exposing services is not very secure. In my campus we must connect via VPN prior to accessing their services. Maybe they put in place recently a new security policy which forbids remote (off-site) connections.

[Emad]

I am trying to do it from my institute office, from the same place where I used to do it! I was trying to figure out what kind of reason it could be and I found that maybe updating the smbclient to version 4 leads to refusing mounting it!

[Emad]

The question is now how to downgrade my smbclient?

[CijcoSistems]

You can install a specific version with: apt-get install package_name=version. Check serverfault.com/questions/108080/… to find available versions of a package. Also keep in mind that smbclient AFAIK is a CLI tool, maybe you mean the one used by the desktop tool (probably gvfs-backends?).

[Leon Straathof]

On my system setting both to SMB2 is what did the trick. I think @Emad complained about the newer version messing things up, as well.

[user1768761]

For me too... SMB2 works for connecting to another Ubuntu samba share. Has this samba implementation ever worked for anyone out of the box without constant and painful tweaking with it, restarting machines etc?...