the other computers are win10 and win7
That's going to be a problem. Accessing a WIn10 machine from Linux and accessing a Win7 machine from Linux will be different.
For host discovery and access to a Win7 machine you would need in smb.conf the following lines in the [gloabl] section:
Code: Select all
client max protocol = NT1
name resolve order = bcast host lmhosts wins
There is one other paramater that you may need to fix and that is your host name. Run this command:
Count the number of characters. If it's more than 15 your machine is invisible to netbios so you will need to fix that by adding one more line to smb.conf under the ones above:
Code: Select all
netbios name = a-name-shorter-than-15-characters-long
Then reboot your Mint machine.
The clinet max protocol = NT1 line that works for Win7 will be a problem for Win10 since it disables SMBv1 ( i.e., NT1 ). You will be able to see the Win10 machine but you won't be able to access it.
And remember that to access the Mint machine from either Windows machine you can always do it explicitly on Explorer:
By ip address:
And for Windows 10 by it's mDNS qualified host name:
You do have one other side issue and that's this - you cannot see your own machine:
The computer does not even appear on the network
You should always be able to see your own machine on the network - outside the Windows Network folder - becase of avahi. The only thing that would stop it would be if it's not running:
Now I'm going to make this as clear as I can. Right now it doesn't matter if avahi isn't working since you don't have any other Linux or MacOS machines in your network. But should you start adding more Linux machines to your network and you cannot get avahi to work you need to stop using Mint.