So, now what I have is perfectly fine access with "guest ok = yes" for each share in smb.conf.
After adding "read only = no", and allowing the 'other' users write access (chmod o=rwx <path to share>) I could write files too.
However, I don't think it's really that secure leaving things with full guest access. Sure the ufw firewall only allows my one PC IP address on the LAN, and my router has MAC filtering, but it'd be nice for the extra layer of security of a password login to protect the Linux machine.
Everything I do does not work. Windows takes a strangely long time to pop up the credentials username/password box, and then fails with a Network Error: "Windows cannot access the share" with a 0x80004005 error.
I have my OS user "mintuser" with pw "password"
I have created a samba user "mintuser" with pw "password" [sudo smbpasswd -a mintuser]
smb.conf // all else is default
Code: Select all
[global] workgroup = <same as Win10 PC> [share] comment = share path = /home/roshare valid users = mintuser read only = no
shows mintuser is present
What gives? Is this a Windows thing?
Typing this "\\192.168.56.101\share" should get me to the share folder
Entering "mintuser" and username and "password" for password should work too, right?
So far, I have found a lot of out of date info, suggesting "security = user" which is depreciated. I'm now stuck.
As I have Linux in a VirtualMachine, running with a host-only adaptor, I am open to try all sorts here.
Windows 'host' is seen by Linux 'guest' at 192.168.56.1 (firewall rules open upd 137/138, tcp 139/445)
Linux 'guest' is seen by Windows 'host' at 192.168.56.101
Linux Mint 18.3 xfce with kernel 4.10.0-38-generic (default) and samba 4.3.11
Windows 10 Pro 1703 Creators
Thanks for any help