trinidad wrote:https://serverfault.com/questions/87916 ... with-samba
On a private LAN I don't bother with this stuff. I also use a Windows administrator account and password to login from the Linux side. Use gpe-msc and also check/set your Windows firewall. Also just because the share folder shows up in Windows doesn't mean that Samba is working. Some users have found that v1 works better than v2 for large files. My advice - if you're on Windows 10 - install SSH. More straightforward.
TC
I am able to connect to my shares on my HTPC which is running Linux Mint from my Windows machine. Though it was set up through the GUI and there is no mention of the shares at all in the smb.conf file on the HTPC. The fit-PC has no GUI, hence Samba. Also, I do have SSH installed on the Windows machine, as I was SSH'd into the fit-PC from the Windows PowerShell to set up the auto-mount and configure Samba. How do I use that to transfer files? I will look into the rest of what you suggested when I get some more time later.
EDIT: That's odd. I can't reach my HTPC shares from my Windows machine anymore. I was able to just last night.
EDIT #2: I've added these lines to the /etc/samba/smb.conf file:
Code: Select all
lanman auth = no
ntlm auth = yes
client lanman auth = no
and it didn't change anything.
I've also gone into gpedit in Windows and it is already set to allow insecure connections. I've also tried pretty much every available NTLM setting in Windows with the only result being I've completely lost the ability to see anything at all on my LAN. I can no longer access my HTPC from my Windows rig or access my Windows rig from my HTPC. My whole LAN is borked over this now. I was able to get it so I could see the HTPC and the fit-PC on my LAN (though I was still unable to access them) briefly, but I can't do that anymore. I don't even know what changed. This is annoying.
EDIT #3: I was able to fix most of my LAN. I am now able to access my HTPC from my Windows machine and vice versa again, but I am still unable to access the fit-PC from the Windows machine. Now it won't even ask for credentials, though. It just says it's not accessible.