I have been getting errors connecting to samba/cifs shares from like 3 weeks ago, I have 4 machines, one with Windows, 2 with Fedora 24 and one with Fedora 22. I have shares on the two fedora 24 machines and if I try to connect, for example, from one f24 machine to the other via thunar I get a No route to host. error. I also had configured a one-liner script on my fedora 22 box that connects to the f24 machine using the following command:# mount -t cifs -o username=****,password=**** '\\192.168.1.1\share' remote/and it worked like a charm for a very long time, but recently it fails with this error:[  91.981816] CIFS VFS: Error connecting to socket. Aborting operation.[  91.981960] CIFS VFS: cifs_mount failed w/return code = -113Unable to find suitable address.I also tried to connect from one of my f24 machines to the other, and I get (on both machines, trying to connect to each other):Unable to find suitable address.But, if I try to connect using the same command from within the same target machine, it works without any issues, and it gets mounted correctly.The windows machine simply fails to connect. Why does this happen? How can I fix this? This is new to me since everything was working correctly until 2-3 weeks ago. Also I can ssh into any of them without any problem, the issue is completely on samba/cifs.
SAMBA/CIFS connection error
samba;cifs
I think that the problem is the construction of the mount command. Try with this:mount -t cifs //192.168.1.1/share mount_point/ -o username=****,password=****This should work if the shares configuration in 192.168.1.1 are well configured. If this don't work, you can use smbclient in the client machine to debug the problems without use mount, with something like this (executed in one of the client machines):smbclient //192.168.1.1/share -U usernameIt will prompt you for the password of username, and it will give you a more detailed error if it goes wrong.