(They are there, I can see them in the fedora file browser locally) Here is my smb.conf file: I would run nmap locally, and then from a different host. Answer: Open terminal and run the following command to edit samba config file. On the Windows clients I can see the shares so samba appears to be working. [homes] comment = Home Directories browseable = no writable = yes Both User A & B can see this share, but only user A can access it. I also have an iMac that I upgraded to Catalina last night. Unable to access via Windows explorer via the name or the IP Address.

# Un-comment the following parameter to make sure that only "username" # can connect to \\server\username # This might need tweaking when using external authentication schemes; valid users = %S ; Turn on sharing so anyone with network access can read and write files in the public folders. pam password change = yes map to guest = bad user ; usershare max shares = 100 usershare allow guests = yes And here is the share section: Both user A & B can access this from windows. Open up File Explorer and then right-click on This PC (in the left pane). In the resulting screen (Figure B), click Choose a custom network location (the only option) and then click Next… When accessing a Samba share in windows, I can see the share but whenever I try and access it - entering the same username and password as the Samba user created with sudo smbpasswd -a benjamin (same as system user), I only get "Access is Denied".
... see how simple it can be with the help of Samba. The shared paths have file permissions 666. From the resulting context menu, select Add a network location (Figure A). On Windows 10 clients specifically on versions 1709 or beyond when you try to access the KACE SMA Samba Share will receive a Windows cannot find \\SMAHostname\client. I am also testing on a 7.2 server and having the same problems. Figure A A new wizard will open, one that will walk you through the process of creating a shortcut for a new network location within File Explorer. I configured Samba (Arch Linux 64 bit) to use usershares and I wanted to share some folders with my Windows 10 laptop. However, the authentication fails on the Windows boxes. I can see my Arch computer on Windows, access it, list folders but I can't access them (Windows shows popup that can't access my shared folder).

Allow windows to manage homegroup connection (recommended). No problems. Turn on file and printer sharing. level 2. The server is redhat 7.4.

I am trying to set up file shares that can be accessed from Windows PC's.

I've checked to make sure that File Sharing/discovery was on (it is). sudo gedit /etc/samba/smb.conf. Ensure Windows firewall allows outgoing access for the same ports. If you cannot open/map network shared folders on your NAS, Samba Linux server, computers with old Windows versions (Windows 7/XP/Server 2003) from Windows 10, most likely the problem is that legacy and insecure versions of the SMB protocol are disabled in the latest Windows 10 builds (SMB protocol is used in Windows to access shared network folders and files).